xintongsong opened a new pull request #10330: [FLINK-14189][runtime] Extend TaskExecutor to support dynamic slot allocation URL: https://github.com/apache/flink/pull/10330 ## What is the purpose of the change This PR is part fo FLIP-56. It extends `TaskExecutor` to support dynamic slot allocation. With this PR, the `TaskExecutor` now supports both previous static slot allocation and the new dynamic allocation. - For dynamic slot allocation, a special `SlotID` (with negative slot index) needs to be provided, as well as a `ResourceProfile` to describe the requested slot resources. - For static slot allocation, a normal `SlotID` (with slot index in the range of `[0, slotNumber)`) needs to be provided. In such cases, the provided `ResourceProfile` will be ignored, and the default slot resource profile derived from configuration will be used. This PR is based on #10146. ## Brief change log - a23d4e5bb9e6d8de936224e62225ca17ae5c8957..927a11838172fe792636923e9378677f92a48b73: Commits of previous PRs. - ef3dd3dceccca803a204813b6777ff8d22ffa170..00c2c39433aeaee6380e2df35fab64e4688d24d9: Hot-fixes and code clean-ups. - ccb13bf72c7109e5b4fa5debf5f66e0b8c01776d: Dynamically create a slot on allocation and destroy a slot on free. - ad0944250413e92e31da943d64d8ac6e1d03c2a0: Support allocate slots without pre-defined slot id. - 38ccce57501562d1bc0e182e246c7a126a589fbe: Introduce `ResourceProfileBookkeeper` for managing resource reserving and releasing of slots. - 74a47e3970a450c64911e458179912dbc2be16db: Use `ResourceProfileBookkeeper` to bookkeep allocated / available resources on the TM side. - 4af0ae0c53dd7752d3c0acbd0928176c151403b1: Generate slot report with TM available resources. - 837f4a9a70f1950f45e7ce766ffd77f286bbc3c8: Task executor supports allocating slots with dynamic resources. ## Verifying this change Added unit test cases in `TaskSlotTableTest` and `TaskExecutorTest`. ## 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: (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)
---------------------------------------------------------------- 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
