zhijiangW opened a new pull request #8509: [FLINK-12458][network] Introduce 
PartitionConnectionException for unreachable producer
URL: https://github.com/apache/flink/pull/8509
 
 
   ## What is the purpose of the change
   
   * If the consumer can not establish a connection to remote task executor 
while requesting remote subpartition, which might indicate the remote task 
executor is not reachable. We could wrap this connection exception into new 
proposed `PartitionConnectionException` which also extends 
`PartitionException`, then the job master would decide whether to restart the 
upstream region to re-producer partition data.*
   
   ## Brief change log
   
     - *Introduce new `PartitionConnectionException` extends 
`PartitionException.*
     - *Wrap any exceptions into `PartitionConnectionException` while creating 
partition request client during `RemoteInputChannel#requestSubpartition`*
   
   ## Verifying this change
   
     - *Added new tests in `RemoteInputChannelTest` for verifying the 
`PartitionConnectionException` while requesting sub partition.*
   
   ## 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