mchades commented on issue #10601:
URL: https://github.com/apache/gravitino/issues/10601#issuecomment-6656914278

   This is a known limitation documented in MetalakeManager. No real-world 
incident is reported here. Guaranteeing atomic updates requires broader storage 
changes, and the proposed rollback cannot guarantee atomicity either. Closing 
as not planned for now; please reopen with a concrete operational case.
   
   After resolving the underlying storage failure, manual recovery can be 
attempted through `PATCH /api/metalakes/{name}` with `{"inUse": true/false}`:
   
   - If enabling failed: disable successfully, then enable.
   - If disabling failed: enable successfully, then disable.
   
   Both steps must complete successfully. This toggles the entire metalake and 
affects the availability of all its catalogs. Repeating the original request 
alone will not reapply the catalog flags because the metalake is already in the 
requested state.
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to