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 startup behaviour #1136

Closed
henrikjohansen opened this Issue May 3, 2015 · 4 comments

Comments

Projects
None yet
6 participants
@henrikjohansen

henrikjohansen commented May 3, 2015

Currently when a server node starts and finds issues with the Elasticsearch cluster it refuses to complete the startup process - with the introduction of the journaling subsystem in 1.0 I find this behaviour a bit problematic since it could mean loosing messages.

I would like to suggest that server nodes always start regardless of the ES cluster status (and thus can buffer messages in it's journal) - the web interface could then inform the user that ES has a problem that needs investigating to avoid confusion.

@runningman84

This comment has been minimized.

runningman84 commented May 4, 2015

+1

2 similar comments
@pkoraca

This comment has been minimized.

pkoraca commented May 7, 2015

+1

@gstimac

This comment has been minimized.

gstimac commented May 7, 2015

+1

@packs

This comment has been minimized.

packs commented Jun 8, 2015

++$votes;

@zexxon zexxon added the feature label Jun 18, 2015

joschi added a commit that referenced this issue Jul 6, 2015

Allow startup without working Elasticsearch cluster
The previous implementation of IndexerSetupService (and related classes) would should down Graylog if
Elasticsearch wasn't available or the cluster health state was RED on startup. This made sense as long
as Graylog didn't have a proper on-disk journal in which messages could be persistently buffered.

The new implementation simply acknowledges the unavailability of Elasticsearch and generates an
appropriate system notification (and log entries) but does not shutdown Graylog.

Fixes #1136

@kroepke kroepke closed this in #1289 Jul 7, 2015

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