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

Elasticsearch operations timeout #1220

Closed
joschi opened this Issue Jun 5, 2015 · 1 comment

Comments

Projects
None yet
3 participants
@joschi
Contributor

joschi commented Jun 5, 2015

Graylog currently runs most Elasticsearch operations without a timeout which will make the whole thing unstable if the Elasticsearch backend is slow or network partitions occur.

To prevent that, all Elasticsearch operations should be run with a configurable timeout.

@joschi joschi added the elasticsearch label Jun 5, 2015

joschi added a commit that referenced this issue Jun 9, 2015

joschi added a commit that referenced this issue Jun 9, 2015

@joschi joschi added this to the 1.2.0 milestone Jun 9, 2015

@joschi joschi self-assigned this Jun 9, 2015

@runningman84

This comment has been minimized.

runningman84 commented Jun 16, 2015

+1

sivasamyk pushed a commit to sivasamyk/graylog2-server that referenced this issue Jul 13, 2015

Unlimited file descriptors are good enough for ES
IndexerClusterCheckerThread checked for the maximum number of open files on Elasticsearch nodes
but didn't handle "unlimited" (-1) correctly.

Fixes Graylog2#1220
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment