[I] [Tiering] Trigger job failover when coordinator epoch changes [fluss]

["Shawn-Hx (via GitHub)" <gi...@apache.org>]

Shawn-Hx opened a new issue, #3921:
URL: https://github.com/apache/fluss/issues/3921

   ### Search before asking
   
   - [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar.
   
   
   ### Fluss version
   
   0.9.0 (latest release)
   
   ### Please describe the bug 🐞
   
   TieringSourceEnumerator records the coordinator epoch only at startup. After a coordinator failover or upgrade, it continues tiering with the stale epoch. The coordinator rejects subsequent heartbeats, causing tiering tasks to time out and the failuresTotal metric to keep increasing.
   
   ### Solution
   
   Validate the coordinator epoch in every heartbeat response. If it differs from the startup epoch, throw an exception to trigger a Flink job failover. The restarted enumerator will register again with the latest coordinator epoch.
   
   ### Are you willing to submit a PR?
   
   - [x] I'm willing to submit a PR!


-- 
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-unsubscribe@fluss.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org