You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fluss.apache.org by "luoyuxia (via GitHub)" <gi...@apache.org> on 2026/01/13 08:10:13 UTC

[I] Handle individual table failures without failing the entire job [fluss]

luoyuxia opened a new issue, #2360:
URL: https://github.com/apache/fluss/issues/2360

   ### Search before asking
   
   - [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar.
   
   
   ### Description
   
   **Description**
   Currently, the Tiering Service processes multiple tables for data tiering. However, if a task for a specific table fails due to non-recoverable reasons (e.g., AccessDeniedException for remote storage, missing Paimon Catalog permissions, or metadata corruption), the entire Tiering Service job might crash or enter a restart loop.
   
   Consistent with our implementation in the Committer node, we should improve the fault tolerance of the Tiering Service.
   
   **Proposed Changes**
   The Tiering Service should be decoupled from individual table task failures:
   
   Isolation of Failures: If a tiering task for Table A fails due to an exception (especially permission-related or configuration-related), the service should catch the exception and prevent it from propagating to the main thread.
   
   Table Status Marking: Mark the specific table as "Failed" or "Error" in memory (and potentially log the state).
   
   Continue with Next Table: The service should continue processing the next available tables (Table B, Table C, etc.) in the queue instead of stopping the entire job.
   
   The `TieringReader` should send to `TieringEnumerator` and the `TieringEnumerator` should notify this to all `TieringReader`  and `Committer` so that they can clear their status for this failed table. 
   
   ### Willingness to contribute
   
   - [ ] 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

Re: [I] Handle individual table failures without failing the entire job [fluss]

Posted by "linguoxuan (via GitHub)" <gi...@apache.org>.
linguoxuan commented on issue #2360:
URL: https://github.com/apache/fluss/issues/2360#issuecomment-3752618116

   Hi, @luoyuxia . Has this not started yet? I'm interested in this and would like to contribute.


-- 
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

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

Re: [I] Handle individual table failures without failing the entire job [fluss]

Posted by "linguoxuan (via GitHub)" <gi...@apache.org>.
linguoxuan commented on issue #2360:
URL: https://github.com/apache/fluss/issues/2360#issuecomment-3749514584

   Hi, @luoyuxia. Has this not started yet? I'm interested in this and would like to contribute.


-- 
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

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