zhuzhurk opened a new pull request #10038: [FLINK-14375][runtime] Refactor task 
state updating to only notify scheduler about state changes that really happened
URL: https://github.com/apache/flink/pull/10038
 
 
   
   ## What is the purpose of the change
   
   This PR is to avoid fake state update. More details see LFINK-14375.
   Besides that, it also has a few other benefits:
   1. we can get rid of the hack code in Execution#processFail
   2. all states are possible to be notified to SchedulingStrategy, i.e. it 
solves FLINK-14233
   
   
   ## Brief change log
   
     - *Change DefaultScheduler to not handle the state update in 
SchedulerBase#updateTaskExecutionState*
     - *Change ExecutionGraph to notify all execution state changes to 
scheduler*
   
   
   ## Verifying this change
   
   This change is already covered by existing tests in DefaultSchedulerTest and 
IT cases.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (yes / **no**)
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: (yes / **no**)
     - The serializers: (yes / **no** / don't know)
     - The runtime per-record code paths (performance sensitive): (yes / **no** 
/ don't know)
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Yarn/Mesos, ZooKeeper: (**yes** / no / don't know)
     - The S3 file system connector: (yes / **no** / don't know)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (yes / **no**)
     - If yes, how is the feature documented? (**not applicable** / docs / 
JavaDocs / not documented)
   

----------------------------------------------------------------
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

Reply via email to