This is an automated email from the ASF dual-hosted git repository.
dbarnes pushed a commit to branch support/1.13
in repository https://gitbox.apache.org/repos/asf/geode.git
The following commit(s) were added to refs/heads/support/1.13 by this push:
new 54a3b8f GEODE-9561: typo repair
54a3b8f is described below
commit 54a3b8fbcb9acb489fc96ff9654cde3aefdc3cc4
Author: Dave Barnes <[email protected]>
AuthorDate: Wed Sep 8 13:22:20 2021 -0700
GEODE-9561: typo repair
---
geode-docs/managing/management/jmx_manager_operations.html.md.erb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/geode-docs/managing/management/jmx_manager_operations.html.md.erb
b/geode-docs/managing/management/jmx_manager_operations.html.md.erb
index 657fa0c..da8ca6a 100644
--- a/geode-docs/managing/management/jmx_manager_operations.html.md.erb
+++ b/geode-docs/managing/management/jmx_manager_operations.html.md.erb
@@ -42,7 +42,7 @@ gfsh>start server --name=<server-name>
--J=-Dgemfire.jmx-manager=true \
By default, any locator can become a JMX Manager when started. When you start
up a locator, if no other JMX Manager is detected in the cluster, the locator
starts one automatically. If you start a second locator, it will detect the
current JMX Manager and will not start up another JMX Manager unless the second
locator's `gemfire.jmx-manager-start` property is set to true.
-For most deployments, you only need to have one JMX Manager per cluster.
However, you can run more than JMX Manager if necessary. If you want to provide
high-availability and redundancy for the Pulse monitoring tool, or if you are
running additional JMX clients other than gfsh, then use the
`jmx-manager-start=true` property to force individual nodes (either locators or
servers) to become JMX Managers at startup. Since there is some performance
overhead to being a JMX Manager, we recommen [...]
+For most deployments, you only need to have one JMX Manager per cluster.
However, you can run more than one JMX Manager if necessary. If you want to
provide high-availability and redundancy for the Pulse monitoring tool, or if
you are running additional JMX clients other than gfsh, then use the
`jmx-manager-start=true` property to force individual nodes (either locators or
servers) to become JMX Managers at startup. Since there is some performance
overhead to being a JMX Manager, we reco [...]
After the node becomes a JMX Manager, all other `jmx-manager-*` configuration
properties listed in [Configuring a JMX
Manager](jmx_manager_operations.html#topic_263072624B8D4CDBAD18B82E07AA44B6)
are applied.
