zhijiangW opened a new pull request #10539: [FLINK-14952][network] Solve the issue of exceeding memory limits when using mmap blocking partition URL: https://github.com/apache/flink/pull/10539 ## What is the purpose of the change *As reported by users in mail list, the container would be killed by yarn because of exceeding physical memory limits. It is mainly because the memory usage of mmap in `BoundedBlockingSubpartition` is not capped and not accounted by configured memory limits, but yarn would track this memory usage and kill the container once exceeding some threshold.* *To solve this issue, we adjust the default option of `taskmanager.network.bounded-blocking-subpartition-type` from `auto` to `file` for safety usage. And users can still enable mmap way via configuration if they make a proper adjustment in yarn configuration to avoid container killing.* ## Brief change log - *Generates the respective html files for previous changed configurations* - *Adjusts the default option of blocking subpartition type from `auto` to `file`* ## Verifying this change This change is a trivial rework / code cleanup without any test coverage. ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): (yes / **no**) - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (**yes** / no) - The serializers: (yes / **no** / don't know) - The runtime per-record code paths (performance sensitive): (yes / **no** / don't know) - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / **no** / don't know) - The S3 file system connector: (yes / **no** / don't know) ## Documentation - Does this pull request introduce a new feature? (yes / **no**) - If yes, how is the feature documented? (**not applicable** / docs / JavaDocs / not documented)
---------------------------------------------------------------- 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: [email protected] With regards, Apache Git Services
