[FLINK-4373] [cluster management] Introduce AllocationID, ResourceProfile, and AllocatedSlot#2630
Closed
StephanEwen wants to merge 1 commit into
Closed
[FLINK-4373] [cluster management] Introduce AllocationID, ResourceProfile, and AllocatedSlot#2630StephanEwen wants to merge 1 commit into
StephanEwen wants to merge 1 commit into
Conversation
…file, and AllocatedSlot These classes are introduced as part of the cluster management rework.
liuyuzhong
pushed a commit
to liuyuzhong/flink
that referenced
this pull request
Dec 5, 2016
…file, and AllocatedSlot These classes are introduced as part of the cluster management rework. This closes apache#2630
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
These classes are introduced as part of the cluster management rework (FLIP-6)
The
AllocatedSlotrepresents a slot on the TaskManager, reserved by a JobManager. Prior to FLIP-6, all slots are always implicitly reserved by the JobManager at which the TaskManagers register. With FLIP-6, slots are dynamically allocated - hence the AllocatedSlot.A
Slotis then anAllocatedSlotused by the Scheduler/ExecutionGraph for a task deployment, possibly sub-dividing the slot for slot sharing. It references the executed tasks, subslots, and has fields determining whether the slot is in use or freed.After this pull request,
Slot,SimpleSlot, andSharedSlothave a dual functionality to support FLIP-6 and the current style.