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

Remove exits from filebeat #645

Merged
merged 1 commit into from
Jan 6, 2016
Merged

Conversation

ruflin
Copy link
Contributor

@ruflin ruflin commented Jan 6, 2016

Remove panic recovery as should not be handled inside the beat. Same for exists. Beats should always properly be shut down whenever possible.

Add changelog for missing changelog in #644

Remove panic recovery as should not be handled inside the beat.
@ruflin ruflin force-pushed the remove-filebeat-exit branch from db0a7dc to 5deb914 Compare January 6, 2016 14:35
@ruflin ruflin added the review label Jan 6, 2016
@ruflin ruflin changed the title Remove exists from filebeat Remove exits from filebeat Jan 6, 2016
@monicasarbu
Copy link
Contributor

LGTM

@andrewkroh
Copy link
Member

To clarify, is this change being made so that the Beat will use the godaemon process to restart it on failure?

@ruflin
Copy link
Contributor Author

ruflin commented Jan 6, 2016

@andrewkroh This is mainly a cleanup of filebeat. I don't think the beats itself should exit but return errors. Some of this code was still coming from lsf. Returning errors will also make the shutdown smoother.

@andrewkroh
Copy link
Member

That all makes sense. I misread the recover code and thought it was actually doing recovery to keep the beat running in case of a panic.

andrewkroh added a commit that referenced this pull request Jan 6, 2016
@andrewkroh andrewkroh merged commit 9e573c9 into elastic:master Jan 6, 2016
@ruflin ruflin deleted the remove-filebeat-exit branch January 6, 2016 15:38
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.

3 participants