isunjin opened a new pull request #6817: [FLINK-10298] [JobManager] Batch Job 
Failover Strategy
URL: https://github.com/apache/flink/pull/6817
 
 
   ## What is the purpose of the change
   
   The new failover strategy needs to consider handling failures according to 
different failure types. It orchestrates the batch job failover logic in 
onTaskFailure method of the FailoverStrategy interface, with the logic inline:
   
   public void onTaskFailure(Execution taskExecution, Throwable cause) {
   
           //1. Get the throwable type
   
           //2. If the type is NonRecoverableError fail the job
   
           //3. If the type is PatritionDataMissingError, do revocation
   
           //4. If the type is EnvironmentError, do check blacklist
   
           //5. Other failure types are recoverable, but we need to remember 
the count
            of the failure
   
           //6. if it exceeds the threshold, fail the job
   }
   
   ## Brief change log
     - *Add a configuration MAX_ATTEMPTS_EXECUTION_FAILURE_COUNT, the default 
value is 6 *
     - *Add a failure counter in the failed region*
     - **
   
   
   ## Verifying this change
   
   This change added tests and can be verified as follows:
   
     - *Added Tests to validate job fail immediately and not restart if meet a 
NoRecoverableError*
     - *Added a test to validate job fail after 
MAX_ATTEMPTS_EXECUTION_FAILURE_COUNT times if meet a RecoverableError"
     - *Added BatchJobFailoverStrategy that inherited from 
RestartPipelinedRegionStrategy*
   
   ## 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? (yes )
     - If yes, how is the feature documented? 
([document](https://docs.google.com/document/d/1FdZdcA63tPUEewcCimTFy9Iz2jlVlMRANZkO4RngIuk/edit#heading=h.to0clnrw60r))
   

----------------------------------------------------------------
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:
[email protected]


With regards,
Apache Git Services

Reply via email to