[INLONG-7072][Manager][Sort] Resource adaptive adjustment for Hudi #7077
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dockerzhang
reviewed
Dec 29, 2022
| /inlong-sort/connectors | ||
| /plugins | ||
| /inlong-sort/sort-dist.jar | ||
| /inlong-manager/plugins |
There was a problem hiding this comment.
please remove these lines
healchow
requested changes
Dec 30, 2022
| @@ -209,6 +209,10 @@ | |||
| "meta.Sinks.Hudi.PartitionFieldListHelp": "If the field type is timestamp, you must set the format of the field value, support MICROSECONDS, MILLISECONDS, SECONDS, SQL, ISO_8601, and custom, such as: yyyy-MM-dd HH:mm:ss, etc.", | |||
| "meta.Sinks.Hudi.FieldFormat": "FieldFormat", | |||
| "meta.Sinks.Hudi.ExtListHelper": "The DDL attribute of the hudi table needs to be prefixed with 'ddl.'", | |||
| "meta.Sinks.Hudi.RecordPreDayUnit": "row", | |||
| "meta.Sinks.Hudi.RecordPreDay": "RecordPreDay", | |||
|
|
||
| --> | ||
|
|
||
| ## Apache InLong dev toolkit |
There was a problem hiding this comment.
Please do not commit unrelated codes with this issue.
|
This PR is stale because it has been open for 60 days with no activity. |
github-actions
bot
added
the
stage/stale
github-actions
bot
removed
the
stage/stale
|
This PR is stale because it has been open for 60 days with no activity. |
github-actions
bot
added
the
stage/stale
github-actions
bot
removed
the
stage/stale
|
This PR is stale because it has been open for 60 days with no activity. |
github-actions
bot
added
the
stage/stale
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prepare a Pull Request
[INLONG-7072][Manager][Sort] Resource adaptive adjustment for Hudi
Motivation
Hudi flink jobs often have unreasonable resource allocation. Too much allocation will lead to waste of resources, and too little will lead to back pressure or OOM.
When allocating resources, you first need to determine the concurrency of the source side to ensure that there is no data backlog in the upstream when reading. Here is a general configuration situation, such as partitioning by day, with about 15 billion data per day, and about 50 concurrent configurations. Other data volumes can be converted appropriately.
After determining the concurrency on the source side, you can configure the concurrency of write according to the ratio of 1:1.5 or 1:2.
If OOM occurs in the write operator during operation, you can appropriately add write concurrency and TM memory.
If the following back pressure occurs, the concurrency can be adjusted according to the consumption difference between source and write. As follows, there is a difference of about 50W, that is, there is 50W of data that cannot keep up with the write, and then it can be based on the amount of successfully written data and the running (used) Time to calculate how much write concurrency is needed to calculate the difference of 50W.
Modifications
Verifying this change
(Please pick either of the following options)
This change is a trivial rework/code cleanup without any test coverage.
This change is already covered by existing tests, such as:
(please describe tests)
This change added tests and can be verified as follows:
(example:)
Documentation