The GitHub Actions job "Flink CI (beta)" on flink.git/release-2.2 has succeeded. Run started by GitHub user pnowojski (triggered by pnowojski).
Head commit for run: 342fb95492144f810239bd3f0b8d46389f466df9 / Efrat Levitan <[email protected]> [FLINK-40093][Runtime] Resume idle splits by alignment check if previously paused Usually pauseOrResumeSplits pauses idleness timer for the split so it isn't marked idle while paused. However with low idleness timeout (observed with 1s) + low allowed WM drift, a race condition could cause paused splits to never resume though they have records: 1. A split becomes paused due to too advanced records. 2. pauseOrResumeSplits pauses the split. 3. pauseOrResumeSplits reaches to pause the split idleness clock but is {idlenessTimeout} too late, and the split becomes idle. 4. The watermark advances but the split is excluded from the watermark alignment check due to its idleness. 5. More records arrive but the split is paused at the connector level so they aren't processed, nor seen by watermarkGenerator so it still considers the split idle The PR aims to fix it by preserving the part where idle splits are excluded from alignment pause (to not override their idle status) while allowing alignment check to resume splits even if they are currently idle. They are considered idle until they emit the next record. Report URL: https://github.com/apache/flink/actions/runs/29568054316 With regards, GitHub Actions via GitBox
