Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FLINK-8748] [flip6] Cancel slot allocations for alternatively completed slot requests #5561

Merged
merged 7 commits into from
Feb 24, 2018

Conversation

tillrohrmann
Copy link
Contributor

What is the purpose of the change

If a slot request is fulfilled with a different AllocatedSlot in the SlotPool,
then we cancel the slot request sent to the ResourceManager.

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): (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)

@tillrohrmann tillrohrmann force-pushed the slotPoolCancelSlotRequests branch 5 times, most recently from 2aa2e86 to efc5440 Compare February 24, 2018 13:14
tillrohrmann added a commit to tillrohrmann/flink that referenced this pull request Feb 24, 2018
…ted slot requests

If a slot request is fulfilled with a different AllocatedSlot in the SlotPool,
then we cancel the slot request sent to the ResourceManager.

This closes apache#5561.
This commit enables the rescaling of Flink jobs which are currently not fully
deployed. In such a case, Flink will use the last internal rescaling savepoint.
If there is no such savepoint, then it will use the provided savepoint when the
job was submitted. In case that there is no savepoint at all, then it will restart
the job with vanilla state.

This closes apache#5560.
The problem was a race condition between the triggerCheckpoint and the wait
loop which had as termination condition the number of received trigger checkpoint
messages.
…ted slot requests

If a slot request is fulfilled with a different AllocatedSlot in the SlotPool,
then we cancel the slot request sent to the ResourceManager.

This closes apache#5561.
@asfgit asfgit merged commit 529b512 into apache:master Feb 24, 2018
@tillrohrmann tillrohrmann deleted the slotPoolCancelSlotRequests branch May 29, 2018 10:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants