xintongsong opened a new pull request #8740: [FLINK-12763][runtime] Fail job immediately if tasks’ resource needs can not be satisfied. URL: https://github.com/apache/flink/pull/8740 ## What is the purpose of the change This pull request is based on #8704. It checks whether slot requests can be satisfied by configured resource per slot, and fails those can't be satisfied early instead of waiting for the timeout. ## Brief change log - Convert ResourceSpecs into ResourceProfiles when requesting slots. - Resource manager set allowed slot resource profiles for slot manager. - Yarn/Mesos resource manager set on started. - Standalone resource manager set after an initialization time, based on registered slots during that time. - Slot manager check slot requests against allowed resource profiles, and fail requests early if they can not be satisfied. ## Verifying this change This change added tests and can be verified as follows: - Added SlotManagerTest#testCheckSlotRequestResourceProfile that validates slot manager checks slot request against allowed resource profiles correctly. - Added StandaloneResourceManagerTest#testSetAllowedSlotResourceProfiles that validates that standalone resource manager set allowed resource profiles and fail unsatisfiable slot requests properly, based on slots registered within a cluster initialization time. ## 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
