-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Add changes that support settings files #5332
Conversation
If you find that events are backing up, or that the CPU is not saturated, consider increasing | ||
this number to better utilize machine processing power. | ||
|
||
*`--pipeline.output.workers COUNT`*:: |
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.
@suyograo or @jsvd I'm not convinced this is a valid CLI flag.
pipeline.output.workers DOES NOT exist here:
https://github.com/elastic/logstash/blob/master/logstash-core/lib/logstash/runner.rb
But it does exist here:
https://github.com/elastic/logstash/blob/master/config/logstash.yml#L34
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.
@jsvd did you mean workers
in output
plugins?
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.
good catch @dedemorton
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.
@andrewvc should we expose pipeline.output.workers
to the command line and make it known?
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.
IMHO, we should not. Its just inconsistent to have 1 config option being exposed this way. We should not set this precedent.
@dedemorton Can we also add a separate section "Using the Settings File" or something similar to call out the existence of Since this is new its good to push its visibility. |
-w, --pipeline.workers COUNT | ||
Sets the number of pipeline workers (threads) to run for filter processing (default: number of cores). | ||
*`-w, --pipeline.workers COUNT`*:: | ||
Sets the number of pipeline workers (threads) to run for filter processing (default: half the number of cores). |
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.
I mislead you here, @dedemorton, it's actually the number of cores, not half (set in here)
[edit] please fix also in config/logstash.yml
@suyograo Sure, I can add the info to a separate topic. I decided to err on the side of minimalism here, but I can see how having a separate topic might raise visibility that the file exists. |
aa22440
to
519eee5
Compare
519eee5
to
02342c2
Compare
LGTM |
1 similar comment
LGTM |
Adds doc about settings file to resolve an item listed in #5148
Summary of changes: