Details
-
Bug
-
Status: Closed
-
Blocker
-
Resolution: Fixed
-
1.16.0, 1.17.0, 1.16.1
Description
In batch stream mode with adaptive batch schedule mode, If we set the max parallelism large as 32768 (pipeline.max-parallelism), the job could hang at the shuffle phase:
It would hang for a long time and show "No bytes sent":
After some time to debug, we can see the downstream operator did not receive the end-of-partition event.
Attachments
Attachments
Issue Links
- is caused by
-
FLINK-28519 Fix the bug that SortMergeResultPartitionReadScheduler may not read data sequentially
- Resolved
- links to