This is an automated email from the ASF dual-hosted git repository.

abhishek pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/druid.git


The following commit(s) were added to refs/heads/master by this push:
     new d98cbd90f0 Update basic-cluster-tuning.md (#12412)
d98cbd90f0 is described below

commit d98cbd90f06576b0c89eb3d82a92abbfe09f53a8
Author: mark-imply <[email protected]>
AuthorDate: Fri Apr 8 03:59:55 2022 -0600

    Update basic-cluster-tuning.md (#12412)
    
    Changed "Other useful JVM flags" to "Other generally useful JVM flags" in 
order to align with the introduction to the doc.
---
 docs/operations/basic-cluster-tuning.md | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/docs/operations/basic-cluster-tuning.md 
b/docs/operations/basic-cluster-tuning.md
index 800a001b74..473bf722b7 100644
--- a/docs/operations/basic-cluster-tuning.md
+++ b/docs/operations/basic-cluster-tuning.md
@@ -398,7 +398,7 @@ Enabling process termination on out-of-memory errors is 
useful as well, since th
 
 `-XX:+ExitOnOutOfMemoryError`
 
-#### Other useful JVM flags
+#### Other generally useful JVM flags
 
 ```
 -Duser.timezone=UTC
@@ -423,7 +423,7 @@ Enabling process termination on out-of-memory errors is 
useful as well, since th
 -XX:HeapDumpPath=/var/logs/druid/historical.hprof
 -XX:MaxDirectMemorySize=1g
 ```
-> Please note that the flag settings above represent sample, general 
guidelines only. Be careful to use values appropriate 
+> Please note that the flag settings above represent sample, general 
guidelines only. Be careful to use values appropriate
 for your specific scenario and be sure to test any changes in staging 
environments.
 
 `ExitOnOutOfMemoryError` flag is only supported starting JDK 8u92 . For older 
versions, `-XX:OnOutOfMemoryError='kill -9 %p'` can be used.
@@ -467,4 +467,3 @@ The limit on the number of open files can be set 
permanently by editing `/etc/se
 ##### max_map_count
 
 Historical processes and to a lesser extent, MiddleManager and Indexer 
processes memory map segment files, so depending on the number of segments per 
server, `/proc/sys/vm/max_map_count` might also need to be adjusted. Depending 
on the variant of Linux, this might be done via `sysctl` by placing a file in 
`/etc/sysctl.d/` that sets `vm.max_map_count`.
-


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to