azagrebin opened a new pull request #11445: [FLINK-16615] Introduce data structures and utilities to calculate Job Manager memory components URL: https://github.com/apache/flink/pull/11445 ## What is the purpose of the change This PR introduces new memory model and its configuration options for JM. There is no behavioural change at the moment, only data structures for memory components are prepared and options are parsed to fill them. See more details in [FLIP-116: Unified Memory Configuration for Job Managers](https://cwiki.apache.org/confluence/display/FLINK/FLIP+116%3A+Unified+Memory+Configuration+for+Job+Managers). ## Brief change log - Introduce new memory JM options in `JobManagerOptions` - Introduce `JobManagerProcessSpec` container for JM memory components - Factor out common parts from `TaskExecutorProcessUtils` into `MemoryProcessUtils` which can be reused for JM (JVM components and arguments, some other common methods) - Factor out common tests from `TaskExecutorProcessUtilsTest` into the base test suite `MemoryProcessUtilsTestBase` - Introduce `JobManagerProcessUtils` which parses new memory specific `JobManagerOptions` and calculates JM memory components as `JobManagerProcessSpec` - Introduce `JobManagerProcessUtilsTest` suite for `JobManagerProcessUtils` ## Verifying this change Unit tests. ## 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, Kubernetes/Yarn/Mesos, ZooKeeper: (no) - 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 now)
---------------------------------------------------------------- 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
