This is an automated email from the ASF dual-hosted git repository.
dbarnes pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/geode-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 5ac455f GEODE-10510: User guide updates - alter runtime command and
change loglevel command docs bug & improvements
5ac455f is described below
commit 5ac455fd0e713c4bbd5c8113d5dd410d9c4d08ce
Author: Dave Barnes <[email protected]>
AuthorDate: Wed Mar 23 12:22:33 2022 -0700
GEODE-10510: User guide updates - alter runtime command and change loglevel
command docs bug & improvements
---
.../socket_communication_have_enough_sockets.html | 2 +-
docs/guide/112/tools_modules/gfsh/command-pages/alter.html | 12 ++++++++----
docs/guide/112/tools_modules/gfsh/command-pages/change.html | 10 ++++++----
.../socket_communication_have_enough_sockets.html | 2 +-
docs/guide/113/tools_modules/gfsh/command-pages/alter.html | 12 ++++++++----
docs/guide/113/tools_modules/gfsh/command-pages/change.html | 10 ++++++----
docs/guide/114/tools_modules/gfsh/command-pages/alter.html | 12 ++++++++----
docs/guide/114/tools_modules/gfsh/command-pages/change.html | 10 ++++++----
.../socket_communication_have_enough_sockets.html | 2 +-
.../guide/latest/tools_modules/gfsh/command-pages/alter.html | 12 ++++++++----
.../latest/tools_modules/gfsh/command-pages/change.html | 10 ++++++----
11 files changed, 59 insertions(+), 35 deletions(-)
diff --git
a/docs/guide/112/managing/monitor_tune/socket_communication_have_enough_sockets.html
b/docs/guide/112/managing/monitor_tune/socket_communication_have_enough_sockets.html
index 1815e67..dc3819a 100644
---
a/docs/guide/112/managing/monitor_tune/socket_communication_have_enough_sockets.html
+++
b/docs/guide/112/managing/monitor_tune/socket_communication_have_enough_sockets.html
@@ -2649,7 +2649,7 @@ recommend that you set <code>conserve-sockets</code> to
<code>false</code>.</p>
<p>You can force the release of an idle socket connection for peer-to-peer and
client-to-server connections:</p>
<ul>
-<li> <strong>Peer-to-peer</strong>. For peer-to-peer threads that do not
share sockets, you can use the <code>socket-lease-time</code> to make sure that
no socket sits idle for too long. When a socket that belongs to an individual
thread remains unused for this time period, the system automatically returns it
to the pool. The next time the thread needs a socket, it creates a new
socket.</li>
+<li> <strong>Peer-to-peer</strong>. For peer-to-peer threads that do not
share sockets, you can use the <code>socket-lease-time</code> to make sure that
no socket sits idle for too long. When a socket that belongs to an individual
thread remains unused for this time period, the system automatically closes
that socket. The next time the thread needs a socket, it creates a new
socket.</li>
<li> <strong>Client</strong>. For client connections, you can affect the same
lease-time behavior by setting the pool <code>idle-timeout</code>.</li>
</ul>
diff --git a/docs/guide/112/tools_modules/gfsh/command-pages/alter.html
b/docs/guide/112/tools_modules/gfsh/command-pages/alter.html
index d27876e..3ce1ed8 100644
--- a/docs/guide/112/tools_modules/gfsh/command-pages/alter.html
+++ b/docs/guide/112/tools_modules/gfsh/command-pages/alter.html
@@ -3089,7 +3089,11 @@ server1 | Region "/customer" altered on "server1"
<h2 id="alter-runtime"><a id="topic_7E6B7E1B972D4F418CB45354D1089C2B"
class="no-quick-link"></a>alter runtime</h2>
-<p>Alters configuration properties for all members or a subset of members
while the member or members are running.</p>
+<p>Alters configuration properties for all servers or a subset of servers
while the member or members are running.
+Alter runtime is a cluster configuration command that affects the
configuration for newly joining servers.
+In order for running members to adopt the alteration, they must be stopped and
restarted.</p>
+
+<p>The alter runtime command does not apply to locators.</p>
<p>For more information on these configuration properties, see <a
href="/docs/guide/112/reference/topics/chapter_overview_cache_xml.html#cache_xml">cache.xml</a>
and configuration parameter reference.</p>
@@ -3151,7 +3155,7 @@ server1 | Region "/customer" altered on "server1"
<td>0</td>
</tr>
<tr>
-<td><span class="keyword parmname">–loglevel </span></td>
+<td><span class="keyword parmname">–log-level </span></td>
<td>The new log level. This option is required and you must specify a value.
Valid values are: <code>ALL</code>, <code>TRACE</code>, <code>DEBUG</code>,
<code>INFO</code>, <code>WARN</code>, <code>ERROR</code>, <code>FATAL</code>,
<code>OFF</code>.
<td>INFO</td>
@@ -3200,11 +3204,11 @@ Valid values are: <code>ALL</code>, <code>TRACE</code>,
<code>DEBUG</code>, <cod
</table></p>
<p><strong>Example Commands:</strong></p>
-<pre class="highlight plaintext"><code>alter runtime --members=server1
--loglevel=WARN --enable-statistics=true
+<pre class="highlight plaintext"><code>alter runtime --members=server1
--log-level=WARN --enable-statistics=true
</code></pre>
<p><strong>Sample Output:</strong></p>
-<pre class="highlight plaintext"><code>gfsh>alter runtime --members=server1
--loglevel=WARN --enable-statistics=true
+<pre class="highlight plaintext"><code>gfsh>alter runtime --members=server1
--log-level=WARN --enable-statistics=true
Runtime configuration altered successfully for the following member(s)
192.0.2.0(server1:240)<v1>:64871
</code></pre>
diff --git a/docs/guide/112/tools_modules/gfsh/command-pages/change.html
b/docs/guide/112/tools_modules/gfsh/command-pages/change.html
index 9d71ede..9767847 100644
--- a/docs/guide/112/tools_modules/gfsh/command-pages/change.html
+++ b/docs/guide/112/tools_modules/gfsh/command-pages/change.html
@@ -2631,10 +2631,12 @@ limitations under the License.
<p>Changes the logging level on specified members.</p>
+<p>The <code>change loglevel</code> command applies only to the members
specified, whether they are servers or locators. The change does not apply to
unspecified or subsequently-added members.</p>
+
<p><strong>Availability:</strong> Online. You must be connected in
<code>gfsh</code> to a JMX Manager member to use this command.</p>
<p><strong>Syntax:</strong></p>
-<pre class="highlight plaintext"><code>change loglevel --loglevel=value
[--members=value(,value)*] [--groups=value(,value)*]
+<pre class="highlight plaintext"><code>change loglevel --log-level=value
[--members=value(,value)*] [--groups=value(,value)*]
</code></pre>
<p><a
id="topic_E74ED23CB60342538B2175C326E7D758__table_2277A2CE8F6E4731B45FEFA2B1366DB6"></a></p>
@@ -2665,7 +2667,7 @@ limitations under the License.
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">--loglevel</span></td>
+<td><span class="keyword parmname">--log-level</span></td>
<td><em>Required.</em> Log level to change. Valid options are:
<code>ALL</code>, <code>TRACE</code>, <code>DEBUG</code>, <code>INFO</code>,
<code>WARN</code>, <code>ERROR</code>, <code>FATAL</code>, <code>OFF</code>.
</td>
@@ -2677,11 +2679,11 @@ limitations under the License.
<p><span class="tablecap">Table 1. Change Loglevel Parameters</span></p>
<p><strong>Example Commands:</strong></p>
-<pre class="highlight plaintext"><code>gfsh>change loglevel
--loglevel=DEBUG --members=server1
+<pre class="highlight plaintext"><code>gfsh>change loglevel
--log-level=DEBUG --members=server1
</code></pre>
<p><strong>Sample Output:</strong></p>
-<pre class="highlight plaintext"><code>gfsh>change loglevel
--loglevel=DEBUG --members=server1
+<pre class="highlight plaintext"><code>gfsh>change loglevel
--log-level=DEBUG --members=server1
Summary
diff --git
a/docs/guide/113/managing/monitor_tune/socket_communication_have_enough_sockets.html
b/docs/guide/113/managing/monitor_tune/socket_communication_have_enough_sockets.html
index 503166b..70971bd 100644
---
a/docs/guide/113/managing/monitor_tune/socket_communication_have_enough_sockets.html
+++
b/docs/guide/113/managing/monitor_tune/socket_communication_have_enough_sockets.html
@@ -2647,7 +2647,7 @@ recommend that you set <code>conserve-sockets</code> to
<code>false</code>.</p>
<p>You can force the release of an idle socket connection for peer-to-peer and
client-to-server connections:</p>
<ul>
-<li> <strong>Peer-to-peer</strong>. For peer-to-peer threads that do not
share sockets, you can use the <code>socket-lease-time</code> to make sure that
no socket sits idle for too long. When a socket that belongs to an individual
thread remains unused for this time period, the system automatically returns it
to the pool. The next time the thread needs a socket, it creates a new
socket.</li>
+<li> <strong>Peer-to-peer</strong>. For peer-to-peer threads that do not
share sockets, you can use the <code>socket-lease-time</code> to make sure that
no socket sits idle for too long. When a socket that belongs to an individual
thread remains unused for this time period, the system automatically closes
that socket. The next time the thread needs a socket, it creates a new
socket.</li>
<li> <strong>Client</strong>. For client connections, you can affect the same
lease-time behavior by setting the pool <code>idle-timeout</code>.</li>
</ul>
diff --git a/docs/guide/113/tools_modules/gfsh/command-pages/alter.html
b/docs/guide/113/tools_modules/gfsh/command-pages/alter.html
index 83933c4..405331a 100644
--- a/docs/guide/113/tools_modules/gfsh/command-pages/alter.html
+++ b/docs/guide/113/tools_modules/gfsh/command-pages/alter.html
@@ -3087,7 +3087,11 @@ server1 | Region "/customer" altered on "server1"
<h2 id="alter-runtime"><a id="topic_7E6B7E1B972D4F418CB45354D1089C2B"
class="no-quick-link"></a>alter runtime</h2>
-<p>Alters configuration properties for all members or a subset of members
while the member or members are running.</p>
+<p>Alters configuration properties for all servers or a subset of servers
while the member or members are running.
+Alter runtime is a cluster configuration command that affects the
configuration for newly joining servers.
+In order for running members to adopt the alteration, they must be stopped and
restarted.</p>
+
+<p>The alter runtime command does not apply to locators.</p>
<p>For more information on these configuration properties, see <a
href="/docs/guide/113/reference/topics/chapter_overview_cache_xml.html#cache_xml">cache.xml</a>
and configuration parameter reference.</p>
@@ -3149,7 +3153,7 @@ server1 | Region "/customer" altered on "server1"
<td>0</td>
</tr>
<tr>
-<td><span class="keyword parmname">–loglevel </span></td>
+<td><span class="keyword parmname">–log-level </span></td>
<td>The new log level. This option is required and you must specify a value.
Valid values are: <code>ALL</code>, <code>TRACE</code>, <code>DEBUG</code>,
<code>INFO</code>, <code>WARN</code>, <code>ERROR</code>, <code>FATAL</code>,
<code>OFF</code>.
<td>INFO</td>
@@ -3198,11 +3202,11 @@ Valid values are: <code>ALL</code>, <code>TRACE</code>,
<code>DEBUG</code>, <cod
</table></p>
<p><strong>Example Commands:</strong></p>
-<pre class="highlight plaintext"><code>alter runtime --members=server1
--loglevel=WARN --enable-statistics=true
+<pre class="highlight plaintext"><code>alter runtime --members=server1
--log-level=WARN --enable-statistics=true
</code></pre>
<p><strong>Sample Output:</strong></p>
-<pre class="highlight plaintext"><code>gfsh>alter runtime --members=server1
--loglevel=WARN --enable-statistics=true
+<pre class="highlight plaintext"><code>gfsh>alter runtime --members=server1
--log-level=WARN --enable-statistics=true
Runtime configuration altered successfully for the following member(s)
192.0.2.0(server1:240)<v1>:64871
</code></pre>
diff --git a/docs/guide/113/tools_modules/gfsh/command-pages/change.html
b/docs/guide/113/tools_modules/gfsh/command-pages/change.html
index e772a3e..d87197b 100644
--- a/docs/guide/113/tools_modules/gfsh/command-pages/change.html
+++ b/docs/guide/113/tools_modules/gfsh/command-pages/change.html
@@ -2631,10 +2631,12 @@ limitations under the License.
<p>When using a custom <code>Log4J</code> configuration, this command takes
effect only if the member whose logging level you want to change was started
using the <code>--J=-Dgeode.LOG_LEVEL_UPDATE_OCCURS=ALWAYS</code> system
property.</p>
+<p>The <code>change loglevel</code> command applies only to the members
specified, whether they are servers or locators. The change does not apply to
unspecified or subsequently-added members.</p>
+
<p><strong>Availability:</strong> Online. You must be connected in
<code>gfsh</code> to a JMX Manager member to use this command.</p>
<p><strong>Syntax:</strong></p>
-<pre class="highlight plaintext"><code>change loglevel --loglevel=value
[--members=value(,value)*] [--groups=value(,value)*]
+<pre class="highlight plaintext"><code>change loglevel --log-level=value
[--members=value(,value)*] [--groups=value(,value)*]
</code></pre>
<p><a
id="topic_E74ED23CB60342538B2175C326E7D758__table_2277A2CE8F6E4731B45FEFA2B1366DB6"></a></p>
@@ -2665,7 +2667,7 @@ limitations under the License.
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">--loglevel</span></td>
+<td><span class="keyword parmname">--log-level</span></td>
<td><em>Required.</em> Log level to change. Valid options are:
<code>ALL</code>, <code>TRACE</code>, <code>DEBUG</code>, <code>INFO</code>,
<code>WARN</code>, <code>ERROR</code>, <code>FATAL</code>, <code>OFF</code>.
</td>
@@ -2677,11 +2679,11 @@ limitations under the License.
<p><span class="tablecap">Table 1. Change Loglevel Parameters</span></p>
<p><strong>Example Commands:</strong></p>
-<pre class="highlight plaintext"><code>gfsh>change loglevel
--loglevel=DEBUG --members=server1
+<pre class="highlight plaintext"><code>gfsh>change loglevel
--log-level=DEBUG --members=server1
</code></pre>
<p><strong>Sample Output:</strong></p>
-<pre class="highlight plaintext"><code>gfsh>change loglevel
--loglevel=DEBUG --members=server1
+<pre class="highlight plaintext"><code>gfsh>change loglevel
--log-level=DEBUG --members=server1
Summary
diff --git a/docs/guide/114/tools_modules/gfsh/command-pages/alter.html
b/docs/guide/114/tools_modules/gfsh/command-pages/alter.html
index 78e364d..363d26f 100644
--- a/docs/guide/114/tools_modules/gfsh/command-pages/alter.html
+++ b/docs/guide/114/tools_modules/gfsh/command-pages/alter.html
@@ -3131,7 +3131,11 @@ server1 | Region "/customer" altered on "server1"
<h2 id="alter-runtime"><a id="topic_7E6B7E1B972D4F418CB45354D1089C2B"
class="no-quick-link"></a>alter runtime</h2>
-<p>Alters configuration properties for all members or a subset of members
while the member or members are running.</p>
+<p>Alters configuration properties for all servers or a subset of servers
while the member or members are running.
+Alter runtime is a cluster configuration command that affects the
configuration for newly joining servers.
+In order for running members to adopt the alteration, they must be stopped and
restarted.</p>
+
+<p>The alter runtime command does not apply to locators.</p>
<p>For more information on these configuration properties, see <a
href="/docs/guide/114/reference/topics/chapter_overview_cache_xml.html#cache_xml">cache.xml</a>
and configuration parameter reference.</p>
@@ -3193,7 +3197,7 @@ server1 | Region "/customer" altered on "server1"
<td>0</td>
</tr>
<tr>
-<td><span class="keyword parmname">–loglevel </span></td>
+<td><span class="keyword parmname">–log-level </span></td>
<td>The new log level. This option is required and you must specify a value.
Valid values are: <code>ALL</code>, <code>TRACE</code>, <code>DEBUG</code>,
<code>INFO</code>, <code>WARN</code>, <code>ERROR</code>, <code>FATAL</code>,
<code>OFF</code>.
<td>INFO</td>
@@ -3242,11 +3246,11 @@ Valid values are: <code>ALL</code>, <code>TRACE</code>,
<code>DEBUG</code>, <cod
</table></p>
<p><strong>Example Commands:</strong></p>
-<pre class="highlight plaintext"><code>alter runtime --members=server1
--loglevel=WARN --enable-statistics=true
+<pre class="highlight plaintext"><code>alter runtime --members=server1
--log-level=WARN --enable-statistics=true
</code></pre>
<p><strong>Sample Output:</strong></p>
-<pre class="highlight plaintext"><code>gfsh>alter runtime --members=server1
--loglevel=WARN --enable-statistics=true
+<pre class="highlight plaintext"><code>gfsh>alter runtime --members=server1
--log-level=WARN --enable-statistics=true
Runtime configuration altered successfully for the following member(s)
192.0.2.0(server1:240)<v1>:64871
</code></pre>
diff --git a/docs/guide/114/tools_modules/gfsh/command-pages/change.html
b/docs/guide/114/tools_modules/gfsh/command-pages/change.html
index 8a467f1..46dd0d0 100644
--- a/docs/guide/114/tools_modules/gfsh/command-pages/change.html
+++ b/docs/guide/114/tools_modules/gfsh/command-pages/change.html
@@ -2675,10 +2675,12 @@ limitations under the License.
<p>When using a custom <code>Log4J</code> configuration, this command takes
effect only if the member whose logging level you want to change was started
using the <code>--J=-Dgeode.LOG_LEVEL_UPDATE_OCCURS=ALWAYS</code> system
property.</p>
+<p>The <code>change loglevel</code> command applies only to the members
specified, whether they are servers or locators. The change does not apply to
unspecified or subsequently-added members.</p>
+
<p><strong>Availability:</strong> Online. You must be connected in
<code>gfsh</code> to a JMX Manager member to use this command.</p>
<p><strong>Syntax:</strong></p>
-<pre class="highlight plaintext"><code>change loglevel --loglevel=value
[--members=value(,value)*] [--groups=value(,value)*]
+<pre class="highlight plaintext"><code>change loglevel --log-level=value
[--members=value(,value)*] [--groups=value(,value)*]
</code></pre>
<p><a
id="topic_E74ED23CB60342538B2175C326E7D758__table_2277A2CE8F6E4731B45FEFA2B1366DB6"></a></p>
@@ -2709,7 +2711,7 @@ limitations under the License.
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">--loglevel</span></td>
+<td><span class="keyword parmname">--log-level</span></td>
<td><em>Required.</em> Log level to change. Valid options are:
<code>ALL</code>, <code>TRACE</code>, <code>DEBUG</code>, <code>INFO</code>,
<code>WARN</code>, <code>ERROR</code>, <code>FATAL</code>, <code>OFF</code>.
</td>
@@ -2721,11 +2723,11 @@ limitations under the License.
<p><span class="tablecap">Table 1. Change Loglevel Parameters</span></p>
<p><strong>Example Commands:</strong></p>
-<pre class="highlight plaintext"><code>gfsh>change loglevel
--loglevel=DEBUG --members=server1
+<pre class="highlight plaintext"><code>gfsh>change loglevel
--log-level=DEBUG --members=server1
</code></pre>
<p><strong>Sample Output:</strong></p>
-<pre class="highlight plaintext"><code>gfsh>change loglevel
--loglevel=DEBUG --members=server1
+<pre class="highlight plaintext"><code>gfsh>change loglevel
--log-level=DEBUG --members=server1
Summary
diff --git
a/docs/guide/latest/managing/monitor_tune/socket_communication_have_enough_sockets.html
b/docs/guide/latest/managing/monitor_tune/socket_communication_have_enough_sockets.html
index ed793dd..6b93a24 100644
---
a/docs/guide/latest/managing/monitor_tune/socket_communication_have_enough_sockets.html
+++
b/docs/guide/latest/managing/monitor_tune/socket_communication_have_enough_sockets.html
@@ -2691,7 +2691,7 @@ recommend that you use the default value of
<code>false</code>.</p>
<p>You can force the release of an idle socket connection for peer-to-peer and
client-to-server connections:</p>
<ul>
-<li> <strong>Peer-to-peer</strong>. For peer-to-peer threads that do not
share sockets, you can use the <code>socket-lease-time</code> to make sure that
no socket sits idle for too long. When a socket that belongs to an individual
thread remains unused for this time period, the system automatically returns it
to the pool. The next time the thread needs a socket, it creates a new
socket.</li>
+<li> <strong>Peer-to-peer</strong>. For peer-to-peer threads that do not
share sockets, you can use the <code>socket-lease-time</code> to make sure that
no socket sits idle for too long. When a socket that belongs to an individual
thread remains unused for this time period, the system automatically closes
that socket. The next time the thread needs a socket, it creates a new
socket.</li>
<li> <strong>Client</strong>. For client connections, you can affect the same
lease-time behavior by setting the pool <code>idle-timeout</code>.</li>
</ul>
diff --git a/docs/guide/latest/tools_modules/gfsh/command-pages/alter.html
b/docs/guide/latest/tools_modules/gfsh/command-pages/alter.html
index 78e364d..363d26f 100644
--- a/docs/guide/latest/tools_modules/gfsh/command-pages/alter.html
+++ b/docs/guide/latest/tools_modules/gfsh/command-pages/alter.html
@@ -3131,7 +3131,11 @@ server1 | Region "/customer" altered on "server1"
<h2 id="alter-runtime"><a id="topic_7E6B7E1B972D4F418CB45354D1089C2B"
class="no-quick-link"></a>alter runtime</h2>
-<p>Alters configuration properties for all members or a subset of members
while the member or members are running.</p>
+<p>Alters configuration properties for all servers or a subset of servers
while the member or members are running.
+Alter runtime is a cluster configuration command that affects the
configuration for newly joining servers.
+In order for running members to adopt the alteration, they must be stopped and
restarted.</p>
+
+<p>The alter runtime command does not apply to locators.</p>
<p>For more information on these configuration properties, see <a
href="/docs/guide/114/reference/topics/chapter_overview_cache_xml.html#cache_xml">cache.xml</a>
and configuration parameter reference.</p>
@@ -3193,7 +3197,7 @@ server1 | Region "/customer" altered on "server1"
<td>0</td>
</tr>
<tr>
-<td><span class="keyword parmname">–loglevel </span></td>
+<td><span class="keyword parmname">–log-level </span></td>
<td>The new log level. This option is required and you must specify a value.
Valid values are: <code>ALL</code>, <code>TRACE</code>, <code>DEBUG</code>,
<code>INFO</code>, <code>WARN</code>, <code>ERROR</code>, <code>FATAL</code>,
<code>OFF</code>.
<td>INFO</td>
@@ -3242,11 +3246,11 @@ Valid values are: <code>ALL</code>, <code>TRACE</code>,
<code>DEBUG</code>, <cod
</table></p>
<p><strong>Example Commands:</strong></p>
-<pre class="highlight plaintext"><code>alter runtime --members=server1
--loglevel=WARN --enable-statistics=true
+<pre class="highlight plaintext"><code>alter runtime --members=server1
--log-level=WARN --enable-statistics=true
</code></pre>
<p><strong>Sample Output:</strong></p>
-<pre class="highlight plaintext"><code>gfsh>alter runtime --members=server1
--loglevel=WARN --enable-statistics=true
+<pre class="highlight plaintext"><code>gfsh>alter runtime --members=server1
--log-level=WARN --enable-statistics=true
Runtime configuration altered successfully for the following member(s)
192.0.2.0(server1:240)<v1>:64871
</code></pre>
diff --git a/docs/guide/latest/tools_modules/gfsh/command-pages/change.html
b/docs/guide/latest/tools_modules/gfsh/command-pages/change.html
index 8a467f1..46dd0d0 100644
--- a/docs/guide/latest/tools_modules/gfsh/command-pages/change.html
+++ b/docs/guide/latest/tools_modules/gfsh/command-pages/change.html
@@ -2675,10 +2675,12 @@ limitations under the License.
<p>When using a custom <code>Log4J</code> configuration, this command takes
effect only if the member whose logging level you want to change was started
using the <code>--J=-Dgeode.LOG_LEVEL_UPDATE_OCCURS=ALWAYS</code> system
property.</p>
+<p>The <code>change loglevel</code> command applies only to the members
specified, whether they are servers or locators. The change does not apply to
unspecified or subsequently-added members.</p>
+
<p><strong>Availability:</strong> Online. You must be connected in
<code>gfsh</code> to a JMX Manager member to use this command.</p>
<p><strong>Syntax:</strong></p>
-<pre class="highlight plaintext"><code>change loglevel --loglevel=value
[--members=value(,value)*] [--groups=value(,value)*]
+<pre class="highlight plaintext"><code>change loglevel --log-level=value
[--members=value(,value)*] [--groups=value(,value)*]
</code></pre>
<p><a
id="topic_E74ED23CB60342538B2175C326E7D758__table_2277A2CE8F6E4731B45FEFA2B1366DB6"></a></p>
@@ -2709,7 +2711,7 @@ limitations under the License.
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">--loglevel</span></td>
+<td><span class="keyword parmname">--log-level</span></td>
<td><em>Required.</em> Log level to change. Valid options are:
<code>ALL</code>, <code>TRACE</code>, <code>DEBUG</code>, <code>INFO</code>,
<code>WARN</code>, <code>ERROR</code>, <code>FATAL</code>, <code>OFF</code>.
</td>
@@ -2721,11 +2723,11 @@ limitations under the License.
<p><span class="tablecap">Table 1. Change Loglevel Parameters</span></p>
<p><strong>Example Commands:</strong></p>
-<pre class="highlight plaintext"><code>gfsh>change loglevel
--loglevel=DEBUG --members=server1
+<pre class="highlight plaintext"><code>gfsh>change loglevel
--log-level=DEBUG --members=server1
</code></pre>
<p><strong>Sample Output:</strong></p>
-<pre class="highlight plaintext"><code>gfsh>change loglevel
--loglevel=DEBUG --members=server1
+<pre class="highlight plaintext"><code>gfsh>change loglevel
--log-level=DEBUG --members=server1
Summary
