xintongsong opened a new pull request #9105: [FLINK-13241][Yarn/Mesos] Fix Yarn/MesosResourceManager setting managed memory size into wrong configuration instance. URL: https://github.com/apache/flink/pull/9105 ## What is the purpose of the change This PR fix the bug that Yarn/MesosResourceManager set managed memory size into wrong configuration instance. As a result, such setting does not overwrite the config on TM side, causing RM/TM slot resource profile inconsistency. As a result, pending task manager slots on RM side cannot be completed once created, prevent RM from starting new TMs for subsequence slot requests. ## Brief change log - Yarn/MesosResourceManager set managed memory into the proper configuration instance. ## Verifying this change - Manually verified the change by running a streaming job with two vertices using lazy from source strategy on Yarn. The job requests slots in 2 rounds and we verified that RM does start new TM for the second round slot requests, which it doesn't without this change. ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): (no) - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (no) - The serializers: (no) - The runtime per-record code paths (performance sensitive): (no) - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes) - The S3 file system connector: (no) ## Documentation - Does this pull request introduce a new feature? (no) - If yes, how is the feature documented? (not applicable)
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
