You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2019/02/19 16:27:05 UTC

[GitHub] tillrohrmann opened a new pull request #7756: [FLINK-11357] Make ExecutionGraph#suspend terminate ExecutionGraph atomically

tillrohrmann opened a new pull request #7756: [FLINK-11357] Make ExecutionGraph#suspend terminate ExecutionGraph atomically
URL: https://github.com/apache/flink/pull/7756
 
 
   ## What is the purpose of the change
   
   This commit makes the suspend call transition the ExecutionGraph atomically into the
   SUSPENDED state without requiring a round-trip to cancel all task properly. Instead it
   simply notifies the TaskExecutors about the suspension and then transitions the Executions
   into a terminal state. Moreover, this commit removes JobStatus#SUSPENDING.
   
   This PR is based on #7755.
   
   ## Brief change log
   
   - Introduce `Execution#suspend` which transition all non terminal states except for `RECONCILING` directly into `CANCELED`
   - Add `ExecutionVertex#suspend` and `ExecutionJobVertex#suspend` to forward suspend calls to `Execution`
   - Update `ExecutionGraph#suspend` to make sure that suspend happens atomically
   
   ## Verifying this change
   
   - Updated the `ExecutionGraphSuspendTest`
   
   ## 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: (yes)
     - 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 GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services