Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Health indicator for broken repositories #103784

Closed
DaveCTurner opened this issue Jan 2, 2024 · 1 comment · Fixed by #104614
Closed

Health indicator for broken repositories #103784

DaveCTurner opened this issue Jan 2, 2024 · 1 comment · Fixed by #104614
Assignees
Labels

Comments

@DaveCTurner
Copy link
Contributor

Sometimes nodes cannot create a working snapshot Repository instance as specified by the current cluster metadata. This might be due to a missing plugin (yielding an UnknownTypeRepository instance) or some other bad config (yielding an InvalidRepository instance). This causes log messages and failures when actually trying to use the repository but may otherwise go unnoticed. I think we should have a health indicator to surface this kind of misconfiguration directly to the user.

Relates #103752.

@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-data-management (Team:Data Management)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants