[tiering] fail tiering job when readers exceed max duration - #3810
Open
zuston wants to merge 2 commits into
Open
[tiering] fail tiering job when readers exceed max duration#3810zuston wants to merge 2 commits into
zuston wants to merge 2 commits into
Conversation
Member
Author
|
cc @luoyuxia |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
When a table reaches its max tiering duration (datalake.freshness), the tiering enumerator already force-completes in-flight work by notifying source readers via TieringReachMaxDurationEvent. In some cases, however, readers remain stuck and never acknowledge completion (FinishedTieringEvent), leaving the tiering job hanging indefinitely.
This change adds a fast-fail safeguard in TieringSourceEnumerator: after max duration is reached, if the table is still active after another maxTieringDurationMs window, the coordinator fails the Flink tiering job with a FlinkRuntimeException. This allows Flink to restart/recover the stuck source readers instead of leaving the job running forever.
Brief change log
Tests
API and Format
Documentation