bjlovegithub opened a new pull request, #26518: URL: https://github.com/apache/flink/pull/26518
## What is the purpose of the change Fix the issue that GlobalCommitterOperator stuck when upstream operator - writer/committer is scaled up. ## Brief change log Use the old subtask count from restored state instead of new subtask count. When writer/committer operator is restored after scaling up, new tasks without restored state won't send CommittableSummary to downstream GlobalCommitterOperator. So if writer/committer sends subtasks of new run, GlobalCommitterOperator will stuck forever as it is looking for CommittableSummary for new tasks. More details are describe here: https://issues.apache.org/jira/projects/FLINK/issues/FLINK-37747 ## Verifying this change Update existed UT case to cover the code change. ## 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: yes ## Documentation - Does this pull request introduce a new feature? no - If yes, how is the feature documented? not applicable -- 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: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
