-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Properly shut down crawler in case one prospector is misconfigured #4037
Conversation
This needs backport to 5.3 and 5.4 |
@@ -32,6 +32,10 @@ func NewLog(p *Prospector) (*Log, error) { | |||
config: p.config, | |||
} | |||
|
|||
if len(p.config.Paths) == 0 { | |||
return nil, fmt.Errorf("Each prospector must have at least one path defined.") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[golint] reported by reviewdog 🐶
error strings should not be capitalized or end with punctuation or a newline
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
LGTM, can you address reviewdog comment and add a changelog? |
If one prospector started to already send data and a second one was misconfigured, the beat paniced during shutdown. This is no prevented by properly shutting down the crawler also on error. Closes elastic#3917
@exekias Updated |
…lastic#4037) If one prospector started to already send data and a second one was misconfigured, the beat paniced during shutdown. This is no prevented by properly shutting down the crawler also on error. Closes elastic#3917 (cherry picked from commit 95195cc)
…lastic#4037) If one prospector started to already send data and a second one was misconfigured, the beat paniced during shutdown. This is no prevented by properly shutting down the crawler also on error. Closes elastic#3917 (cherry picked from commit 95195cc)
…lastic#4037) If one prospector started to already send data and a second one was misconfigured, the beat paniced during shutdown. This is no prevented by properly shutting down the crawler also on error. Closes elastic#3917 (cherry picked from commit 95195cc)
If one prospector started to already send data and a second one was misconfigured, the beat paniced during shutdown. This is no prevented by properly shutting down the crawler also on error.
Closes #3917