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

Fix Data Stream Lifecycle health indicator to return UNKNOWN #108812

Closed

Conversation

nielsbauman
Copy link
Contributor

When there is no health info available from the health node, the status should be UNKNOWN instead of GREEN.

When there is no health info available from the health node, the
status should be UNKNOWN instead of GREEN.
@elasticsearchmachine
Copy link
Collaborator

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

@elasticsearchmachine
Copy link
Collaborator

Hi @nielsbauman, I've created a changelog YAML for you.

@Before
public void updatePollInterval() throws IOException {
// We need Data Stream Lifecycle to run at least once to have a "green" status.
updateClusterSettings(client(), Settings.builder().put("data_streams.lifecycle.poll_interval", "5s").build());
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After I added this fix, I realized that this PR will cause the health API to return unknown after cluster startup until Data Stream Lifecycle has run at least once. The default interval is 5m, which is quite a while for the health API to report unknown IMO. It probably makes sense to discuss this briefly before we proceed.

@nielsbauman
Copy link
Contributor Author

During an internal discussion, it became clear that this GREEN status is intentional -- as "missing" data can in this case be interpreted as no errors. I'll close this and open up another PR that rewords the comment in DataStreamLifecycleHealthIndicatorService.

@nielsbauman nielsbauman deleted the fix-data-stream-health-status branch May 24, 2024 18:41
nielsbauman added a commit to nielsbauman/elasticsearch that referenced this pull request May 24, 2024
nielsbauman added a commit to nielsbauman/elasticsearch that referenced this pull request May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants