github-mirrors/logstash
1
0
Fork 0
mirror of https://github.com/elastic/logstash.git synced 2025-04-24 06:37:19 -04:00
Code Issues Projects Releases Packages Wiki Activity

More pre-release tweaks to content

Browse source 
Fixes #9943
This commit is contained in:
Karen Metts 2019-01-09 12:27:53 -05:00 • committed by karen.metts
parent 7ffa86e915
commit fdb880e059
2 changed files with 10 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

14
docs/static/best-practice.asciidoc vendored
View file

@ -1,8 +1,8 @@
[[tips]]
== Tips and Best Practices
We will be adding more tips and best practices, so please check back soon.
If you have something you would like to see added, please:
We are adding more tips and best practices, so please check back soon.
If you have something to add, please:
* create an issue at
https://github.com/elastic/logstash/issues, or
@ -21,8 +21,8 @@ forum].
[[tip-windows-cli]]
==== Shell commands on Windows OS
Command line often show single quotes.
On Windows systems, replace a single quote `'' with a double quote `"`.
Command line examples often show single quotes.
On Windows systems, replace a single quote `'` with a double quote `"`.
*Example*
@ -69,9 +69,9 @@ pipeline management is enabled.
"How many partitions should I use per topic?"
At least: Number of {ls} nodes multiplied by consumer threads per node.
At least the number of {ls} nodes multiplied by consumer threads per node.
Better yet: Use a multiple of the above number. Increasing the number of
Better yet, use a multiple of the above number. Increasing the number of
partitions for an existing topic is extremely complicated. Partitions have a
very low overhead. Using 5 to 10 times the number of partitions suggested by the
first point is generally fine, so long as the overall partition count does not
@ -88,7 +88,7 @@ partitions overall. Try not to exceed 1000 partitions.
Lower values tend to be more efficient and have less memory overhead. Try a
value of `1` then iterate your way up. The value should in general be lower than
the number of pipeline workers. Values larger than 4 rarely result in a
the number of pipeline workers. Values larger than 4 rarely result in
performance improvement.
[float]

6
docs/static/troubleshooting.asciidoc vendored
View file

@ -1,8 +1,8 @@
[[troubleshooting]]
== Troubleshooting Common Problems
We will be adding more troubleshooting tips, so please check back soon. If you
have something you would like to see added, please:
We are adding more troubleshooting tips, so please check back soon. If you
have something to add, please:
* create an issue at
https://github.com/elastic/logstash/issues, or
@ -237,7 +237,7 @@ https://github.com/logstash-plugins/logstash-input-kafka/issues/210
*Solution*
* Upgrade Kafka Input plugin to v. 6.3.4 or later.
* If (and only if) upgrading is impossible, set `consumer_threads` to `1`.
* If (and only if) upgrading is not possible, set `consumer_threads` to `1`.
[float]