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

Stop filebeat on error starting registrar #2868

Merged
merged 1 commit into from
Oct 27, 2016

Conversation

ruflin
Copy link
Member

@ruflin ruflin commented Oct 27, 2016

Currently when there is an error during loading the state, filebeat 5.0 doesn't stop and just continues. The registrar loading in filebeat 5.x was already improved an additional validation was added. This PR only changes that if there is an error in loading states, filebeat is not started and a proper error is returned.

This PR does not need forward porting as in the master branch already a more enhanced error management is in place.

Currently when there is an error during loading the state, filebeat 5.0 doesn't stop and just continues. The registrar loading in filebeat 5.x was already improved an additional validation was added. This PR only changes that if there is an error in loading states, filebeat is not started and a proper error is returned.
@tsg
Copy link
Contributor

tsg commented Oct 27, 2016

LGTM.

@tsg tsg merged commit 731c795 into elastic:5.0 Oct 27, 2016
@ruflin ruflin deleted the error-loading-state branch October 27, 2016 11:40
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
Currently when there is an error during loading the state, filebeat 5.0 doesn't stop and just continues. The registrar loading in filebeat 5.x was already improved an additional validation was added. This PR only changes that if there is an error in loading states, filebeat is not started and a proper error is returned.
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 this pull request may close these issues.

2 participants