NicoK opened a new pull request #7033: [FLINK-10419][checkpoint] fix 
ClassNotFoundException while deserializing user exceptions
URL: https://github.com/apache/flink/pull/7033
 
 
   ## What is the purpose of the change
   
   `DeclineCheckpoint` tries to make sure that it does wrap any exception which 
can be and/or contain user code into a `SerializedThrowable`. It also contains 
special handling of a few exceptions that are not wrapped into 
`SerializedThrowable` (`CheckpointDeclineException` sub-classes are claimed to 
not contain user-code) but if these carry user-code exceptions as *suppressed* 
exceptions, the deserialization at the JobManager will fail and the RPC call 
will not be processed at all - we thus rely on another method to actually get 
rid of the checkpoint, e.g. a timeout.
   
   ## Brief change log
   
   - remove the special handling of `CheckpointDeclineException` sub-classes
   
   ## Verifying this change
   
   This change is already covered by existing tests, such as checkpoint tests 
and IT cases.
   
   I also manually verified that no code is relying on checks such as 
`instanceof CheckpointDeclineException` or the explicitly mentioned 
sub-classes, so that it is ok to replace these with `SerializedThrowable` in 
the RPC.
   
   ## 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? **JavaDocs**
   

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