-
Notifications
You must be signed in to change notification settings - Fork 13k
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-1925] Fixes blocking method submitTask on the TM #622
Conversation
…e into two phases: TDD reception with eager acknowledgement and TDD instantiation with a subsequent state update message.
…ase timeouts for travis
.description())); | ||
} | ||
} else { | ||
if (!(success instanceof Messages.Acknowledge$)) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this line is not parsable in Eclipse (the $ mess with the Java parser).
A workaround is to expose the case object class and object via a utility method and check against that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will do.
Looks god modulo some comments. The most critical being the concurrent Map one. |
…n.concurrent.ConcurrentHashMap, refactors submitTask method into extra initializeTask method, makes message type test eclipse compatible.
Thanks for reviewing the code @StephanEwen. I addressed your comments and updated the PR. |
Looks good. Will merge this in my next batch, since I am building code on top anyways... |
…e into two phases: 1. TDD reception with eager acknowledgement and 2. TDD instantiation with a subsequent state update message. This closes apache#622
…e into two phases: 1. TDD reception with eager acknowledgement and 2. TDD instantiation with a subsequent state update message. This closes apache#622
…e into two phases: 1. TDD reception with eager acknowledgement and 2. TDD instantiation with a subsequent state update message. This closes apache#622
The
submitTask
method which processes theSubmitTask
message blocks while downloading the task jars from theJobManager
. Depending on the number of TMs and jars, this can take a long time.In order to get rid of the blocking call the
submitTask
method is split up into two phases: TDD reception with eager acknowledgement and TDD instantiation with a subsequent state update message. The TDD instantiation is executed concurrently in a future. Upon finishing the instantiation, anUpdateTaskExecutionState
message withExecutionState.RUNNING
is sent to the JM. This implies that the state of theExecution
is not directly set toRUNNING
by theSubmitTask
future handler which is created inExecution.deployToSlot
.