1996fanrui opened a new pull request, #26931:
URL: https://github.com/apache/flink/pull/26931

   ## What is the purpose of the change
   
   Job cannot be recovered from UC(unaligned checkpoint) after rescaling, and 
the exception is:
   
   ```
   java.lang.UnsupportedOperationException: Cannot rescale the given pointwise 
partitioner. 
   Did you change the partitioner to forward or rescale? 
   It may also help to add an explicit shuffle().
   ```
   
   When one upstream task has multiple output exchanges, which including UC 
SUPPORTED exchanges(likes hash or rebalance) and at least one UC UNSUPPORTED 
exchanges(likes Forward or rescale).
   
   Or when one downstream task has multiple input exchanges, which including UC 
SUPPORTED exchanges(likes hash or rebalance) and at least one UC UNSUPPORTED 
exchanges(likes Forward or rescale).
   
   See more from FLINK-38267
   
   
   ## Brief change log
   
   - [FLINK-38267] Only call channel state rescaling logic for exchange with 
channel state to avoid UnsupportedOperationException
   - [FLINK-38267][checkpoint] Refactor hasInputState and hasOutputState 
related logic in TaskStateAssignment
   
   
   ## Verifying this change
   
   Doing
   
   ## 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, Kubernetes/Yarn, ZooKeeper: no
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? no
   


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

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to