j1wonpark opened a new issue, #4190: URL: https://github.com/apache/amoro/issues/4190
### Search before asking - [X] I have searched in the [issues](https://github.com/apache/amoro/issues?q=is%3Aissue) and found no similar issues. ### What would you like to be improved? When an external catalog (e.g., REST catalog) fails to initialize during AMS startup — due to an unreachable endpoint, authentication error, or network issue — the exception propagates from `DefaultCatalogManager`'s constructor, crashing the entire AMS process. This means a single misconfigured or temporarily unavailable catalog prevents all other catalogs and the dashboard from being accessible. Furthermore, once AMS restarts, the failed catalog cannot be updated via the dashboard because `updateCatalog()` calls `getServerCatalog()`, which attempts to rebuild the catalog using `computeIfAbsent` with the old (broken) metadata, triggering the same failure. ### How should we improve? 1. **Initialization resilience**: Wrap individual catalog loading in try-catch during `DefaultCatalogManager` initialization so that a single catalog failure is logged and skipped rather than crashing AMS. 2. **Update recovery path**: When a catalog is not present in `serverCatalogMap` (failed to initialize), `updateCatalog()` should fall back to updating the DB directly and attempt to rebuild with the new metadata, allowing operators to fix catalog configuration from the dashboard without restarting AMS. ### Are you willing to submit PR? - [X] Yes I am willing to submit a PR! ### Subtasks _No response_ ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
