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 4762e6e Update user guides, 1.12 & 1.13
4762e6e is described below
commit 4762e6e125d62bd61adb44b2e081f6848d826168
Author: Dave Barnes <[email protected]>
AuthorDate: Thu Apr 29 14:43:31 2021 -0700
Update user guides, 1.12 & 1.13
---
docs/guide/112/managing/logging/setting_up_logging.html | 2 +-
.../112/managing/monitor_tune/socket_tcp_keepalive.html | 2 +-
docs/guide/113/about_geode.html | 2 +-
.../cluster_config/persisting_configurations.html | 16 ++++++++--------
.../113/configuring/running/running_the_cacheserver.html | 2 +-
.../113/getting_started/15_minute_quickstart_gfsh.html | 8 ++++----
docs/guide/113/managing/logging/setting_up_logging.html | 2 +-
.../113/managing/management/jmx_manager_operations.html | 2 +-
.../113/managing/monitor_tune/socket_tcp_keepalive.html | 2 +-
docs/guide/113/tools_modules/gfsh/tour_of_gfsh.html | 6 +++---
.../http_session_mgmt/tomcat_setting_up_the_module.html | 4 ++--
11 files changed, 24 insertions(+), 24 deletions(-)
diff --git a/docs/guide/112/managing/logging/setting_up_logging.html
b/docs/guide/112/managing/logging/setting_up_logging.html
index 8f77c56..0fdc7d1 100644
--- a/docs/guide/112/managing/logging/setting_up_logging.html
+++ b/docs/guide/112/managing/logging/setting_up_logging.html
@@ -2667,7 +2667,7 @@ Make sure each member logs to its own files. This makes
the logs easier to decip
<li><p>Set the maximum size of a single log file in
<code>log-file-size-limit</code>. If not set, the single, main log file is
used. If set, the metadata file, the main log, and rolled child logs are
used.</p></li>
<li><p>Set the maximum size of all log files in
<code>log-disk-space-limit</code>. If non-zero, this limits the combined size
of all inactive log files, deleting oldest files first to stay under the limit.
A zero setting indicates no limit.</p></li>
</ol></li>
-<li><p>If you are using the <code>gfsh</code> command-line interface,
<code>gfsh</code> can creates its own log file in the directory where you run
the <code>gfsh</code> or <code>gfsh.bat</code> script. By default, gfsh does
not generate log files for itself. To enable gfsh logs, set the following
system property to the desired log level before starting gfsh:</p>
+<li><p>If you are using the <code>gfsh</code> command-line interface,
<code>gfsh</code> can create its own log file in the directory where you run
the <code>gfsh</code> or <code>gfsh.bat</code> script. By default, gfsh does
not generate log files for itself. To enable gfsh logs, set the following
system property to the desired log level before starting gfsh:</p>
<pre class="highlight plaintext"><code>export
JAVA_ARGS=-Dgfsh.log-level=[severe|warning|info|config|fine|finer|finest]
</code></pre>
diff --git a/docs/guide/112/managing/monitor_tune/socket_tcp_keepalive.html
b/docs/guide/112/managing/monitor_tune/socket_tcp_keepalive.html
index eaea23d..7ddd552 100644
--- a/docs/guide/112/managing/monitor_tune/socket_tcp_keepalive.html
+++ b/docs/guide/112/managing/monitor_tune/socket_tcp_keepalive.html
@@ -2626,7 +2626,7 @@ limitations under the License.
<p>Geode supports TCP KeepAlive to prevent socket connections from being timed
out.</p>
-<p>The <code>gemfire.enableTcpKeepAlive</code> system property prevents
connections that appear idle from being timed out (for example, by a firewall.)
When configured to true, Geode enables the SO_KEEPALIVE option for individual
sockets. This operating system-level setting allows the socket to send
verification checks (ACK requests) to remote systems in order to determine
whether or not to keep the socket connection alive.</p>
+<p>The <code>gemfire.setTcpKeepAlive</code> system property prevents
connections that appear idle from being timed out (for example, by a firewall.)
When configured to true, Geode enables the SO_KEEPALIVE option for individual
sockets. This operating system-level setting allows the socket to send
verification checks (ACK requests) to remote systems in order to determine
whether or not to keep the socket connection alive.</p>
<p><strong>Note:</strong>
The time intervals for sending the first ACK KeepAlive request, the subsequent
ACK requests and the number of requests to send before closing the socket is
configured on the operating system level.</p>
diff --git a/docs/guide/113/about_geode.html b/docs/guide/113/about_geode.html
index f635ef2..ae3696c 100644
--- a/docs/guide/113/about_geode.html
+++ b/docs/guide/113/about_geode.html
@@ -2622,7 +2622,7 @@ See the License for the specific language governing
permissions and
limitations under the License.
-->
-<p>This documentation describes product concepts and provides complete setup
instructions for Apache Geode 1.13.2.
+<p>This documentation describes product concepts and provides complete setup
instructions for Apache Geode 1.13.
Source files are available from the <a
href="https://github.com/apache/geode/tree/develop/geode-docs";>Apache Geode
Github repository</a>
and instructions on how to build this documentation are available in the <a
href="https://github.com/apache/geode/blob/develop/geode-book/README.md";>Geode
project README file</a>.</p>
diff --git
a/docs/guide/113/configuring/cluster_config/persisting_configurations.html
b/docs/guide/113/configuring/cluster_config/persisting_configurations.html
index 21e04aa..c738110 100644
--- a/docs/guide/113/configuring/cluster_config/persisting_configurations.html
+++ b/docs/guide/113/configuring/cluster_config/persisting_configurations.html
@@ -2639,7 +2639,7 @@ limitations under the License.
/ _____/ ______/ ______/ /____/ /
/ / __/ /___ /_____ / _____ /
/ /__/ / ____/ _____/ / / / /
-/______/_/ /______/_/ /_/ 1.13.2
+/______/_/ /______/_/ /_/ 1.13
Monitor and Manage Apache Geode
gfsh>
@@ -2653,7 +2653,7 @@ Locator in /Users/username/my_geode/locator1 on
192.0.2.0[10334] as locator1
is currently online.
Process ID: 5203
Uptime: 15 seconds
-Geode Version: 1.13.2
+Geode Version: 1.13
Java Version: 1.8.0_121
Log File: /Users/username/my_geode/locator1/locator1.log
JVM Arguments: -Dgemfire.enable-cluster-configuration=true
@@ -2676,7 +2676,7 @@ Server in /Users/username/my_geode/server1 on
192.0.2.0[40404] as server1
is currently online.
Process ID: 5627
Uptime: 2 seconds
-Geode Version: 1.13.2
+Geode Version: 1.13
Java Version: 1.8.0_121
Log File: /Users/username/my_geode/server1/server1.log
JVM Arguments: -Dgemfire.default.locators=192.0.2.0[10334]
-Dgemfire.groups=group1
@@ -2692,7 +2692,7 @@ Server in /Users/username/my_geode/server2 on
192.0.2.0[40405] as server2
is currently online.
Process ID: 5634
Uptime: 2 seconds
-Geode Version: 1.13.2
+Geode Version: 1.13
Java Version: 1.8.0_121
Log File: /Users/username/my_geode/server2/server2.log
JVM Arguments: -Dgemfire.default.locators=192.0.2.0[10334]
-Dgemfire.groups=group1
@@ -2708,7 +2708,7 @@ Server in /Users/username/my_geode/server3 on
192.0.2.0[40406] as server3
is currently online.
Process ID: 5637
Uptime: 2 seconds
-Geode Version: 1.13.2
+Geode Version: 1.13
Java Version: 1.8.0_121
Log File: /Users/username/my_geode/server3/server3.log
JVM Arguments: -Dgemfire.default.locators=192.0.2.0[10334]
@@ -2789,7 +2789,7 @@ Locator in /Users/username/new_geode/locator2 on
192.0.2.0[10335] as locator2
is currently online.
Process ID: 5749
Uptime: 15 seconds
-Geode Version: 1.13.2
+Geode Version: 1.13
Java Version: 1.8.0_121
Log File: /Users/username/new_geode/locator2/locator2.log
JVM Arguments: -Dgemfire.enable-cluster-configuration=true
@@ -2816,7 +2816,7 @@ Server in /Users/username/new_geode/server4 on
192.0.2.0[40414] as server4
is currently online.
Process ID: 5813
Uptime: 4 seconds
-Geode Version: 1.13.2
+Geode Version: 1.13
Java Version: 1.8.0_121
Log File: /Users/username/new_geode/server4/server4.log
JVM Arguments: -Dgemfire.default.locators=192.0.2.0[10335]
@@ -2833,7 +2833,7 @@ Server in /Users/username/new_geode/server2 on
192.0.2.0[40415] as server5
is currently online.
Process ID: 5954
Uptime: 2 seconds
-Geode Version: 1.13.2
+Geode Version: 1.13
Java Version: 1.8.0_121
Log File: /Users/username/new_geode/server5/server5.log
JVM Arguments: -Dgemfire.default.locators=192.0.2.0[10335]
-Dgemfire.groups=group1
diff --git a/docs/guide/113/configuring/running/running_the_cacheserver.html
b/docs/guide/113/configuring/running/running_the_cacheserver.html
index 50c8797..486d00c 100644
--- a/docs/guide/113/configuring/running/running_the_cacheserver.html
+++ b/docs/guide/113/configuring/running/running_the_cacheserver.html
@@ -2735,7 +2735,7 @@ check the status of a running cache server by providing
the server name:</p>
Server in /home/username/server4 on 192.0.2.0[40404] as server4 is currently
online.
Process ID: 49008
Uptime: 2 minutes 4 seconds
-Geode Version: 1.13.2
+Geode Version: 1.13
Java Version: 1.8.0_121
Log File: /home/username/server4/server4.log
JVM Arguments:
diff --git a/docs/guide/113/getting_started/15_minute_quickstart_gfsh.html
b/docs/guide/113/getting_started/15_minute_quickstart_gfsh.html
index 154fafc..84746e9 100644
--- a/docs/guide/113/getting_started/15_minute_quickstart_gfsh.html
+++ b/docs/guide/113/getting_started/15_minute_quickstart_gfsh.html
@@ -2643,7 +2643,7 @@ limitations under the License.
/ _____/ ______/ ______/ /____/ /
/ / __/ /___ /_____ / _____ /
/ /__/ / ____/ _____/ / / / /
-/______/_/ /______/_/ /_/ 1.13.2
+/______/_/ /______/_/ /_/ 1.13
Monitor and Manage Geode
gfsh>
@@ -2655,7 +2655,7 @@ Starting a Geode Locator in
/home/username/my_geode/locator1...
Locator in /home/username/my_geode/locator1 on ubuntu.local[10334] as locator1
is currently online.
Process ID: 3529
Uptime: 18 seconds
-Geode Version: 1.13.2
+Geode Version: 1.13
Java Version: 1.8.0_121
Log File: /home/username/my_geode/locator1/locator1.log
JVM Arguments: -Dgemfire.enable-cluster-configuration=true
-Dgemfire.load-cluster-configuration-from-dir=false
@@ -2936,7 +2936,7 @@ are being waited on by other members.
/ _____/ ______/ ______/ /____/ /
/ / __/ /___ /_____ / _____ /
/ /__/ / ____/ _____/ / / / /
-/______/_/ /______/_/ /_/ 1.13.2
+/______/_/ /______/_/ /_/ 1.13
Monitor and Manage Geode
</code></pre></li>
@@ -2954,7 +2954,7 @@ Successfully connected to: [host=ubuntu.local, port=1099]
<pre class="highlight plaintext"><code>Server in
/home/username/my_geode/server1 on ubuntu.local[40411] as server1 is currently
online.
Process ID: 3402
Uptime: 1 minute 46 seconds
-Geode Version: 1.13.2
+Geode Version: 1.13
Java Version: 1.8.0_121
Log File: /home/username/my_geode/server1/server1.log
JVM Arguments: -Dgemfire.default.locators=192.0.2.0[10334]
-Dgemfire.use-cluster-configuration=true
diff --git a/docs/guide/113/managing/logging/setting_up_logging.html
b/docs/guide/113/managing/logging/setting_up_logging.html
index 9e8616c..ed85e3e 100644
--- a/docs/guide/113/managing/logging/setting_up_logging.html
+++ b/docs/guide/113/managing/logging/setting_up_logging.html
@@ -2665,7 +2665,7 @@ Make sure each member logs to its own files. This makes
the logs easier to decip
<li><p>Set the maximum size of a single log file in
<code>log-file-size-limit</code>. If not set, the single, main log file is
used. If set, the metadata file, the main log, and rolled child logs are
used.</p></li>
<li><p>Set the maximum size of all log files in
<code>log-disk-space-limit</code>. If non-zero, this limits the combined size
of all inactive log files, deleting oldest files first to stay under the limit.
A zero setting indicates no limit.</p></li>
</ol></li>
-<li><p>If you are using the <code>gfsh</code> command-line interface,
<code>gfsh</code> can creates its own log file in the directory where you run
the <code>gfsh</code> or <code>gfsh.bat</code> script. By default, gfsh does
not generate log files for itself. To enable gfsh logs, set the following
system property to the desired log level before starting gfsh:</p>
+<li><p>If you are using the <code>gfsh</code> command-line interface,
<code>gfsh</code> can create its own log file in the directory where you run
the <code>gfsh</code> or <code>gfsh.bat</code> script. By default, gfsh does
not generate log files for itself. To enable gfsh logs, set the following
system property to the desired log level before starting gfsh:</p>
<pre class="highlight plaintext"><code>export
JAVA_ARGS=-Dgfsh.log-level=[severe|warning|info|config|fine|finer|finest]
</code></pre>
diff --git a/docs/guide/113/managing/management/jmx_manager_operations.html
b/docs/guide/113/managing/management/jmx_manager_operations.html
index 4bdfbcb..2e76f73 100644
--- a/docs/guide/113/managing/management/jmx_manager_operations.html
+++ b/docs/guide/113/managing/management/jmx_manager_operations.html
@@ -2654,7 +2654,7 @@ Locator in /Users/username/apache-geode/locator1 on
192.0.2.0[10334] as locator1
is currently online.
Process ID: 27144
Uptime: 5 seconds
-Geode Version: 1.13.2
+Geode Version: 1.13
Java Version: 1.8.0_121
Log File: /Users/username/apache-geode/locator1/locator1.log
JVM Arguments: -Dgemfire.enable-cluster-configuration=true
diff --git a/docs/guide/113/managing/monitor_tune/socket_tcp_keepalive.html
b/docs/guide/113/managing/monitor_tune/socket_tcp_keepalive.html
index 719487d..5ed4923 100644
--- a/docs/guide/113/managing/monitor_tune/socket_tcp_keepalive.html
+++ b/docs/guide/113/managing/monitor_tune/socket_tcp_keepalive.html
@@ -2624,7 +2624,7 @@ limitations under the License.
<p>Geode supports TCP KeepAlive to prevent socket connections from being timed
out.</p>
-<p>The <code>gemfire.enableTcpKeepAlive</code> system property prevents
connections that appear idle from being timed out (for example, by a firewall.)
When configured to true, Geode enables the SO_KEEPALIVE option for individual
sockets. This operating system-level setting allows the socket to send
verification checks (ACK requests) to remote systems in order to determine
whether or not to keep the socket connection alive.</p>
+<p>The <code>gemfire.setTcpKeepAlive</code> system property prevents
connections that appear idle from being timed out (for example, by a firewall.)
When configured to true, Geode enables the SO_KEEPALIVE option for individual
sockets. This operating system-level setting allows the socket to send
verification checks (ACK requests) to remote systems in order to determine
whether or not to keep the socket connection alive.</p>
<p><strong>Note:</strong>
The time intervals for sending the first ACK KeepAlive request, the subsequent
ACK requests and the number of requests to send before closing the socket is
configured on the operating system level.</p>
diff --git a/docs/guide/113/tools_modules/gfsh/tour_of_gfsh.html
b/docs/guide/113/tools_modules/gfsh/tour_of_gfsh.html
index db51ba1..1321c37 100644
--- a/docs/guide/113/tools_modules/gfsh/tour_of_gfsh.html
+++ b/docs/guide/113/tools_modules/gfsh/tour_of_gfsh.html
@@ -2655,7 +2655,7 @@ Locator in /home/username/gfsh_tutorial/locator1 on
192.0.2.0[10334]
as locator1 is currently online.
Process ID: 67666
Uptime: 6 seconds
-Geode Version: 1.13.2
+Geode Version: 1.13
Java Version: 1.8.0_121
Log File: /home/username/gfsh_tutorial/locator1.log
JVM Arguments: -Dgemfire.enable-cluster-configuration=true
@@ -2755,7 +2755,7 @@ Server in /home/username/gfsh_tutorial/server1 on
192.0.2.0[40404] as server1
is currently online.
Process ID: 68375
Uptime: 4 seconds
-Geode Version: 1.13.2
+Geode Version: 1.13
Java Version: 1.8.0_121
Log File: /home/username//gfsh_tutorial/server1/server1.log
JVM Arguments: -Dgemfire.locators=localhost[10334]
@@ -2859,7 +2859,7 @@ Server in /home/username/gfsh_tutorial/server2 on
192.0.2.0[40405] as
server2 is currently online.
Process ID: 68423
Uptime: 4 seconds
-Geode Version: 1.13.2
+Geode Version: 1.13
Java Version: 1.8.0_121
Log File: /home/username/gfsh_tutorial/server2/server2.log
JVM Arguments: -Dgemfire.default.locators=192.0.2.0[10334]
diff --git
a/docs/guide/113/tools_modules/http_session_mgmt/tomcat_setting_up_the_module.html
b/docs/guide/113/tools_modules/http_session_mgmt/tomcat_setting_up_the_module.html
index 747bc93..56036b2 100644
---
a/docs/guide/113/tools_modules/http_session_mgmt/tomcat_setting_up_the_module.html
+++
b/docs/guide/113/tools_modules/http_session_mgmt/tomcat_setting_up_the_module.html
@@ -2689,8 +2689,8 @@ To run Geode in a peer-to-peer configuration, add the
following line to Tomcat&r
</code></pre>
<p>The application server operates as a Geode client in this configuration.
With a similar environment to this example that is for a client/server set
up,</p>
-<pre class="highlight
plaintext"><code>CLASSPATH=$PWD/lib/geode-modules-1.13.2.0.jar:\
-$PWD/lib/geode-modules-tomcat8-1.13.2.0.jar:\
+<pre class="highlight
plaintext"><code>CLASSPATH=$PWD/lib/geode-modules-1.13.0.jar:\
+$PWD/lib/geode-modules-tomcat8-1.13.0.jar:\
$PWD/lib/servlet-api.jar:\
$PWD/lib/catalina.jar:\
$PWD/lib/tomcat-util.jar:\
