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

Graylog discards messages when it detects that there's no Elasticsearch master elected #10440

Closed
asachs01 opened this issue Apr 14, 2021 · 0 comments · Fixed by #11317
Closed
Assignees

Comments

@asachs01
Copy link

asachs01 commented Apr 14, 2021

What?

This is from HS-373864503

if the cluster is in cluster block for no master Graylog discards all messages with should be indexed.

Following gets logged to Indexer Failures Page:
{"type":"cluster_block_exception","reason":"blocked by: [SERVICE_UNAVAILABLE/2/no master];"}

In my opinion this is a retryable state, which should be retried, same as a Cluster Block for Full Filesystem (which gets retried).


Edit

Please note that the customer indicated that they'd also like us to consider this message as a retryable state;

' {"type":"unavailable_shards_exception","reason":"[log_30d_4656][0] primary shard is not active Timeout: [1m], request: [BulkShardRequest [[log_30d_4656][0]] containing [458] requests]"} '
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants