You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@geode.apache.org by db...@apache.org on 2022/04/16 00:51:04 UTC
[geode] branch support/1.14 updated: GEODE-9759: replaces double-hyphens with ‑‑ (#7597)
This is an automated email from the ASF dual-hosted git repository.
dbarnes pushed a commit to branch support/1.14
in repository https://gitbox.apache.org/repos/asf/geode.git
The following commit(s) were added to refs/heads/support/1.14 by this push:
new e7be6be0e0 GEODE-9759: replaces double-hyphens with ‑‑ (#7597)
e7be6be0e0 is described below
commit e7be6be0e0f47f47e2deadb4a6a3c97c9c12a9eb
Author: Max Hufnagel <mh...@vmware.com>
AuthorDate: Fri Apr 15 17:50:58 2022 -0700
GEODE-9759: replaces double-hyphens with ‑‑ (#7597)
---
.../use_pdx_high_level_steps.html.md.erb | 2 +-
.../configuring_bucket_for_pr.html.md.erb | 2 +-
.../query_grammar_and_reserved_words.html.md.erb | 2 +-
.../15_minute_quickstart_gfsh.html.md.erb | 2 +-
.../management_system_overview.html.md.erb | 4 +-
.../failure_detection.html.md.erb | 8 +-
.../implementing_authorization.html.md.erb | 2 +-
.../memory_requirements_for_cache_data.html.md.erb | 2 +-
.../gfsh/command-pages/alter.html.md.erb | 104 +++----
.../gfsh/command-pages/backup.html.md.erb | 6 +-
.../gfsh/command-pages/change.html.md.erb | 6 +-
.../gfsh/command-pages/close.html.md.erb | 14 +-
.../gfsh/command-pages/compact.html.md.erb | 14 +-
.../gfsh/command-pages/configure.html.md.erb | 10 +-
.../gfsh/command-pages/connect.html.md.erb | 34 +--
.../gfsh/command-pages/create.html.md.erb | 306 ++++++++++-----------
.../gfsh/command-pages/define.html.md.erb | 6 +-
.../gfsh/command-pages/deploy.html.md.erb | 4 +-
.../gfsh/command-pages/describe.html.md.erb | 24 +-
.../gfsh/command-pages/destroy.html.md.erb | 24 +-
.../gfsh/command-pages/echo.html.md.erb | 2 +-
.../gfsh/command-pages/execute.html.md.erb | 14 +-
.../gfsh/command-pages/export.html.md.erb | 46 ++--
.../gfsh/command-pages/gc.html.md.erb | 4 +-
.../gfsh/command-pages/get.html.md.erb | 8 +-
.../gfsh/command-pages/history.html.md.erb | 4 +-
.../gfsh/command-pages/import.html.md.erb | 8 +-
.../gfsh/command-pages/list.html.md.erb | 26 +-
.../gfsh/command-pages/load-balance.html.md.erb | 2 +-
.../gfsh/command-pages/locate.html.md.erb | 8 +-
.../gfsh/command-pages/netstat.html.md.erb | 6 +-
.../gfsh/command-pages/pause.html.md.erb | 6 +-
.../gfsh/command-pages/pdx.html.md.erb | 6 +-
.../gfsh/command-pages/put.html.md.erb | 10 +-
.../gfsh/command-pages/rebalance.html.md.erb | 8 +-
.../gfsh/command-pages/remove.html.md.erb | 6 +-
.../gfsh/command-pages/resume.html.md.erb | 12 +-
.../gfsh/command-pages/revoke.html.md.erb | 2 +-
.../gfsh/command-pages/run.html.md.erb | 9 +-
.../gfsh/command-pages/search.html.md.erb | 8 +-
.../gfsh/command-pages/sh.html.md.erb | 4 +-
.../gfsh/command-pages/show.html.md.erb | 24 +-
.../gfsh/command-pages/shutdown.html.md.erb | 4 +-
.../gfsh/command-pages/sleep.html.md.erb | 2 +-
.../gfsh/command-pages/start.html.md.erb | 164 +++++------
.../gfsh/command-pages/status.html.md.erb | 18 +-
.../gfsh/command-pages/stop.html.md.erb | 12 +-
.../gfsh/command-pages/undeploy.html.md.erb | 4 +-
.../gfsh/command-pages/validate.html.md.erb | 4 +-
.../gfsh/command-pages/version.html.md.erb | 2 +-
.../using_bind_addresses.html.md.erb | 4 +-
51 files changed, 505 insertions(+), 508 deletions(-)
diff --git a/geode-docs/developing/data_serialization/use_pdx_high_level_steps.html.md.erb b/geode-docs/developing/data_serialization/use_pdx_high_level_steps.html.md.erb
index 520833b772..abbc6f76ae 100644
--- a/geode-docs/developing/data_serialization/use_pdx_high_level_steps.html.md.erb
+++ b/geode-docs/developing/data_serialization/use_pdx_high_level_steps.html.md.erb
@@ -44,6 +44,6 @@ Optionally, program your application code to deserialize individual fields out o
## PDX and Multi-Site (WAN) Deployments
-For multisite (WAN) installations only-- if you will use PDX serialization in any of your WAN-enabled regions, for each cluster, you must choose a unique integer between 0 (zero) and 255 and set the `distributed-system-id` in every member's `gemfire.properties` file. See [Configuring a Multi-site (WAN) System](../../topologies_and_comm/multi_site_configuration/setting_up_a_multisite_system.html).
+For multisite (WAN) installations only: If you will use PDX serialization in any of your WAN-enabled regions, for each cluster, you must choose a unique integer between 0 (zero) and 255 and set the `distributed-system-id` in every member's `gemfire.properties` file. See [Configuring a Multi-site (WAN) System](../../topologies_and_comm/multi_site_configuration/setting_up_a_multisite_system.html).
diff --git a/geode-docs/developing/partitioned_regions/configuring_bucket_for_pr.html.md.erb b/geode-docs/developing/partitioned_regions/configuring_bucket_for_pr.html.md.erb
index f8dc9714a7..79b8357785 100644
--- a/geode-docs/developing/partitioned_regions/configuring_bucket_for_pr.html.md.erb
+++ b/geode-docs/developing/partitioned_regions/configuring_bucket_for_pr.html.md.erb
@@ -47,7 +47,7 @@ The partition attribute `total-num-buckets` sets the number for the entire parti
- gfsh:
- Use the <span class="keyword parmname">--total-num-buckets</span> parameter of the `create region` command. For example:
+ Use the <span class="keyword parmname">‑‑total-num-buckets</span> parameter of the `create region` command. For example:
``` pre
gfsh>create region --name="PR1" --type=PARTITION --total-num-buckets=7
diff --git a/geode-docs/developing/querying_basics/query_grammar_and_reserved_words.html.md.erb b/geode-docs/developing/querying_basics/query_grammar_and_reserved_words.html.md.erb
index 03a10890ea..f226267f56 100644
--- a/geode-docs/developing/querying_basics/query_grammar_and_reserved_words.html.md.erb
+++ b/geode-docs/developing/querying_basics/query_grammar_and_reserved_words.html.md.erb
@@ -149,7 +149,7 @@ plus ::= +
## <a id="query_grammar_and_reserved_words__section_B074373F2ED44DC7B98652E70ABC5D5D" class="no-quick-link"></a>Language Notes
- Query language keywords such as SELECT, NULL, and DATE are case-insensitive. Identifiers such as attribute names, method names, and path expressions are case-sensitive.
-- Comment lines begin with -- (double dash).
+- Comment lines begin with ‑‑ (double dash).
- Comment blocks begin with /\* and end with \*/.
- String literals are delimited by single-quotes. Embedded single-quotes are doubled.
diff --git a/geode-docs/getting_started/15_minute_quickstart_gfsh.html.md.erb b/geode-docs/getting_started/15_minute_quickstart_gfsh.html.md.erb
index f15da5b1c5..9a7c659424 100644
--- a/geode-docs/getting_started/15_minute_quickstart_gfsh.html.md.erb
+++ b/geode-docs/getting_started/15_minute_quickstart_gfsh.html.md.erb
@@ -213,7 +213,7 @@ In this step you create a region with the `gfsh` command line utility. Regions a
gfsh>start server --name=server1 --server-port=40411
```
-5. Run the following command to retrieve data from the region again -- notice that the data is still available:
+5. Run the following command to retrieve data from the region again. Notice that the data is still available:
``` pre
gfsh>query --query="select * from /regionA"
diff --git a/geode-docs/managing/management/management_system_overview.html.md.erb b/geode-docs/managing/management/management_system_overview.html.md.erb
index 61b7494d02..7f59394c77 100644
--- a/geode-docs/managing/management/management_system_overview.html.md.erb
+++ b/geode-docs/managing/management/management_system_overview.html.md.erb
@@ -38,11 +38,11 @@ Each member of a cluster is a managed node. Any node that is not currently also
## <a id="concept_1BAE2CE1146B4347ABD61F50B9F9781F__section_8604838507194C8B86F1420FBA46894C" class="no-quick-link"></a>JMX Manager Node
-A JMX Manager node is a member that can manage other <%=vars.product_name%> members --that is, other managed nodes -- as well as itself. A JMX Manager node can manage all other members in the cluster.
+A JMX Manager node is a member that can manage other <%=vars.product_name%> members---that is, other managed nodes---as well as itself. A JMX Manager node can manage all other members in the cluster.
To convert a managed node to a JMX Manager node, you configure the <%=vars.product_name%> property `jmx-manager=true`, in the `gemfire.properties` file, and start the member as a JMX Manager node.
-You start the member as a JMX Manager node when you provide` --J=-Dgemfire.jmx-manager=true` as an argument to either the` start server` or `start locator` command. See [Starting a JMX Manager](jmx_manager_operations.html#topic_686158E9AFBD47518BE1B4BEB232C190) for more information.
+You start the member as a JMX Manager node when you provide `--J=-Dgemfire.jmx-manager=true` as an argument to either the `start server` or `start locator` command. See [Starting a JMX Manager](jmx_manager_operations.html#topic_686158E9AFBD47518BE1B4BEB232C190) for more information.
The JMX Manager node has the following extra resources allocated so that it can answer JMX queries:
diff --git a/geode-docs/managing/network_partitioning/failure_detection.html.md.erb b/geode-docs/managing/network_partitioning/failure_detection.html.md.erb
index 2f773e4834..dabeb0b8f9 100644
--- a/geode-docs/managing/network_partitioning/failure_detection.html.md.erb
+++ b/geode-docs/managing/network_partitioning/failure_detection.html.md.erb
@@ -51,10 +51,10 @@ ent(8788)<v7>:24136/53525]
The components of the membership view are as follows:
- The first part of the view (`[ent(5767)<v0>:8700|16]` in the example above) corresponds to the view ID. It identifies:
- - the address and processId of the membership coordinator-- `ent(5767)` in example above.
- - the view-number (`<vXX>`) of the membership view that the member first appeared in-- `<v0>` in example above.
- - membership-port of the membership coordinator-- `8700` in the example above.
- - view-number-- `16` in the example above
+ - the address and processId of the membership coordinator: `ent(5767)` in example above.
+ - the view-number (`<vXX>`) of the membership view that the member first appeared in: `<v0>` in example above.
+ - membership-port of the membership coordinator: `8700` in the example above.
+ - view-number: `16` in the example above
- The second part of the view lists all of the member processes in the current view. `[ent(5767)<v0>:8700/44876, ent(5829)<v1>:48034/55334, ent(5875)<v2>:4738/54595, ent(5822)<v5>:49380/39564, ent(8788)<v7>:24136/53525]` in the example above.
- The overall format of each listed member is:`Address(processId)<vXX>:membership-port/distribution port`. The membership coordinator is almost always the first member in the view and the rest are ordered by age.
- The membership-port is the JGroups TCP UDP port that it uses to send datagrams. The distribution-port is the TCP/IP port that is used for cache messaging.
diff --git a/geode-docs/managing/security/implementing_authorization.html.md.erb b/geode-docs/managing/security/implementing_authorization.html.md.erb
index b712b10986..a2dd539ffb 100644
--- a/geode-docs/managing/security/implementing_authorization.html.md.erb
+++ b/geode-docs/managing/security/implementing_authorization.html.md.erb
@@ -177,7 +177,7 @@ This table classifies the permissions assigned for `gfsh` operations.
| locate entry | DATA:READ:RegionName:Key |
| netstat | CLUSTER:READ |
| pause gateway-sender | CLUSTER:MANAGE:GATEWAY |
-| put --key=key1 --region=region1 | DATA:WRITE:RegionName:Key |
+| put ‑‑key=key1 ‑‑region=region1 | DATA:WRITE:RegionName:Key |
| query | DATA:READ:RegionName |
| rebalance | DATA:MANAGE |
| remove | DATA:WRITE:RegionName or DATA:WRITE:RegionName:Key |
diff --git a/geode-docs/reference/topics/memory_requirements_for_cache_data.html.md.erb b/geode-docs/reference/topics/memory_requirements_for_cache_data.html.md.erb
index bf6dfd276d..1276beacb0 100644
--- a/geode-docs/reference/topics/memory_requirements_for_cache_data.html.md.erb
+++ b/geode-docs/reference/topics/memory_requirements_for_cache_data.html.md.erb
@@ -218,7 +218,7 @@ If you do want to estimate memory usage for PDX serialized data, the following t
| String | String.length + 3 bytes |
| Domain Object | 9 bytes (for PDX header) + object serialization length (total all member fields) + 1 to 4 extra bytes (depends on the total size of Domain object) |
-A note of caution-- if the domain object contains many domain objects as member fields, then the memory overhead of PDX serialization can be considerably more than other types of serialization.
+A note of caution: If the domain object contains many domain objects as member fields, then the memory overhead of PDX serialization can be considerably more than other types of serialization.
## <a id="topic_d3g_c5z_j4" class="no-quick-link"></a>Calculating Socket Memory Requirements
diff --git a/geode-docs/tools_modules/gfsh/command-pages/alter.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/alter.html.md.erb
index da9d64ff11..8b122bb291 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/alter.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/alter.html.md.erb
@@ -111,39 +111,39 @@ The three required options, `--name`, `--region`, and `--disk-dirs`, identify th
</thead>
<tbody>
<tr>
-<td><span class="keyword parmname">\-\-name</span></td>
+<td><span class="keyword parmname">‑‑name</span></td>
<td><em>Required</em>. Name of the disk-store whose contents will be altered.</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-region</span></td>
+<td><span class="keyword parmname">‑‑region</span></td>
<td><em>Required</em>. Name (including path) of the region using the disk store.</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-disk-dirs</span></td>
+<td><span class="keyword parmname">‑‑disk-dirs</span></td>
<td><em>Required</em>. Directories where the data for the disk store was previously written.</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-compressor</span></td>
+<td><span class="keyword parmname">‑‑compressor</span></td>
<td>The fully-qualified class name of the compressor to use when compressing region entry values. A value of <code class="ph codeph">none</code> removes the compressor.</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-concurrency-level</span></td>
-<td>An estimate of the maximum number of application threads that will concurrently access a region entry. Together with <span class="keyword parmname">\-\-initial-capacity</span> and <span class="keyword parmname">\-\-load-factor</span>, sets the parameters on the underlying <code class="ph codeph">java.util.ConcurrentHashMap</code> used for storing region entries. This attribute does not apply to partitioned regions.</td>
+<td><span class="keyword parmname">‑‑concurrency-level</span></td>
+<td>An estimate of the maximum number of application threads that will concurrently access a region entry. Together with <span class="keyword parmname">‑‑initial-capacity</span> and <span class="keyword parmname">‑‑load-factor</span>, sets the parameters on the underlying <code class="ph codeph">java.util.ConcurrentHashMap</code> used for storing region entries. This attribute does not apply to partitioned regions.</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-enable-statistics</span></td>
+<td><span class="keyword parmname">‑‑enable-statistics</span></td>
<td>Enables statistics for the region specified by the <code>--region</code> option. Valid values are true or false. If the parameter is specified without a value, the value of true is used.</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-initial-capacity</span></td>
-<td>Together with <span class="keyword parmname">\-\-concurrency-level</span> and <span class="keyword parmname">\-\-load-factor</span>, sets the parameters on the underlying <code class="ph codeph">java.util.ConcurrentHashMap</code> used for storing region entries.</td>
+<td><span class="keyword parmname">‑‑initial-capacity</span></td>
+<td>Together with <span class="keyword parmname">‑‑concurrency-level</span> and <span class="keyword parmname">‑‑load-factor</span>, sets the parameters on the underlying <code class="ph codeph">java.util.ConcurrentHashMap</code> used for storing region entries.</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-load-factor</span></td>
-<td>Together with <span class="keyword parmname">\-\-concurrency-level</span> and <span class="keyword parmname">\-\-initial-capacity</span>, sets the parameters on the underlying <code class="ph codeph">java.util.ConcurrentHashMap</code> used for storing region entries. This must be a floating point number between 0 and 1, inclusive.</td>
+<td><span class="keyword parmname">‑‑load-factor</span></td>
+<td>Together with <span class="keyword parmname">‑‑concurrency-level</span> and <span class="keyword parmname">‑‑initial-capacity</span>, sets the parameters on the underlying <code class="ph codeph">java.util.ConcurrentHashMap</code> used for storing region entries. This must be a floating point number between 0 and 1, inclusive.</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-lru-action</span></td>
+<td><span class="keyword parmname">‑‑lru-action</span></td>
<td>Action to take when evicting entries from the region. Valid values are:
<ul>
<li><code class="ph codeph">none</code></li>
@@ -152,7 +152,7 @@ The three required options, `--name`, `--region`, and `--disk-dirs`, identify th
</ul></td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-lru-algorithm</span></td>
+<td><span class="keyword parmname">‑‑lru-algorithm</span></td>
<td>Least recently used eviction algorithm. Valid types are:
<ul>
<li><code class="ph codeph">none</code></li>
@@ -162,16 +162,16 @@ The three required options, `--name`, `--region`, and `--disk-dirs`, identify th
</ul></td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-lru-limit</span></td>
+<td><span class="keyword parmname">‑‑lru-limit</span></td>
<td>Number of entries allowed in the region before eviction occurs.</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-off-heap</span></td>
+<td><span class="keyword parmname">‑‑off-heap</span></td>
<td>Specifies whether the region values are in heap memory or off-heap memory. When true, region values are in off-heap memory. If the parameter is specified without a value, the value of true is used.</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-remove</span></td>
-<td>Specifies whether to remove the region from the disk-store. If the parameter is specified without a value, the value of true is used. Note: <span class="keyword parmname">\-\-remove</span> deletes all persistent data for the region. Consider copying the disk store files to a backup before using this option if you might want to retrieve the data at a later date.</td>
+<td><span class="keyword parmname">‑‑remove</span></td>
+<td>Specifies whether to remove the region from the disk-store. If the parameter is specified without a value, the value of true is used. Note: <span class="keyword parmname">‑‑remove</span> deletes all persistent data for the region. Consider copying the disk store files to a backup before using this option if you might want to retrieve the data at a later date.</td>
</tr>
</tbody>
</table>
@@ -257,37 +257,37 @@ alter region --name=value [--groups=value(,value)*]
</thead>
<tbody>
<tr>
-<td><span class="keyword parmname">\-\-async-event-queue-id</span></td>
+<td><span class="keyword parmname">‑‑async-event-queue-id</span></td>
<td>IDs of the Async Event Queues that will be used for write-behind operations.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-cache-listener</span></td>
+<td><span class="keyword parmname">‑‑cache-listener</span></td>
<td>Fully qualified class name of a plug-in to be instantiated for receiving after-event notification of changes to the region and its entries. Any number of cache listeners can be configured. A fully qualified class name may be appended with a JSON specification that will be parsed to become the fields of the parameter to the <code>init()</code> method for a class that implements the <code>Declarable</code> interface.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-cache-loader</span></td>
+<td><span class="keyword parmname">‑‑cache-loader</span></td>
<td>Fully qualified class name of a plug-in to be instantiated for receiving notification of cache misses in the region. At most, one cache loader can be defined in each member for the region. For distributed regions, a cache loader may be invoked remotely from other members that have the region defined. A fully qualified class name may be appended with a JSON specification that will be parsed to become the fields of the parameter to the <code>initialize()</code> method for a class that [...]
<td></td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-cache-writer</span></td>
+<td><span class="keyword parmname">‑‑cache-writer</span></td>
<td>Fully qualified class name of a plug-in to be instantiated for receiving before-event notification of changes to the region and its entries. The plug-in may cancel the event. At most, one cache writer can be defined in each member for the region. A fully qualified class name may be appended with a JSON specification that will be parsed to become the fields of the parameter to the <code>init()</code> method for a class that implements the <code>Declarable</code> interface.</td>
<td></td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-enable-cloning</span></td>
+<td><span class="keyword parmname">‑‑enable-cloning</span></td>
<td><p>Determines how <code class="ph codeph">fromDelta</code> applies deltas to the local cache for delta propagation. When true, the updates are applied to a clone of the value and then the clone is saved to the cache. When false, the value is modified in place in the cache.</p></td>
<td><code class="ph codeph">false</code></td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-entry-idle-time-expiration</span></td>
+<td><span class="keyword parmname">‑‑entry-idle-time-expiration</span></td>
<td>Number of seconds before a region or an entry expires. Specify <code class="ph codeph">-1</code> to indicate that there is no expiration of this type</td>
<td>-1</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-entry-idle-time-expiration-action</span></td>
+<td><span class="keyword parmname">‑‑entry-idle-time-expiration-action</span></td>
<td>Action that should take place when a region or an entry expires.
<div class="p">
Select one of the following expiration actions:
@@ -315,12 +315,12 @@ Select one of the following expiration actions:
<td><code class="ph codeph">invalidate</code></td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-entry-time-to-live-expiration</span></td>
+<td><span class="keyword parmname">‑‑entry-time-to-live-expiration</span></td>
<td>Number of seconds before a region or an entry expires. Specify <code class="ph codeph">-1</code> to indicate that there is no expiration of this type.</td>
<td>-1</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-entry-time-to-live-expiration-action</span></td>
+<td><span class="keyword parmname">‑‑entry-time-to-live-expiration-action</span></td>
<td>Action that should take place when a region or an entry expires.
<div class="p">
Select one of the following expiration actions:
@@ -348,42 +348,42 @@ Select one of the following expiration actions:
<td><code class="ph codeph">invalidate</code></td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-entry-idle-time-custom-expiry</span></td>
+<td><span class="keyword parmname">‑‑entry-idle-time-custom-expiry</span></td>
<td>The name of a class implementing CustomExpiry for entry idle time. Append a JSON string for initialization properties.</td>
<td></td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-entry-time-to-live-custom-expiry</span></td>
+<td><span class="keyword parmname">‑‑entry-time-to-live-custom-expiry</span></td>
<td>The name of a class implementing CustomExpiry for entry time to live. Append a JSON string for initialization properties.</td>
<td></td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-eviction-max</span></td>
+<td><span class="keyword parmname">‑‑eviction-max</span></td>
<td>Maximum value for the Eviction Attributes that the eviction algorithm uses to determine when to perform its eviction action. The unit of the maximum value is determined by the Eviction Algorithm.</td>
<td>0</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-gateway-sender-id</span></td>
+<td><span class="keyword parmname">‑‑gateway-sender-id</span></td>
<td>IDs of the Gateway Senders where data is routed.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-groups</span></td>
+<td><span class="keyword parmname">‑‑groups</span></td>
<td>Group(s) of members where the region will be altered.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-name</span></td>
+<td><span class="keyword parmname">‑‑name</span></td>
<td>Required. Name (including path) of the region.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-region-idle-time-expiration</span></td>
+<td><span class="keyword parmname">‑‑region-idle-time-expiration</span></td>
<td>Number of seconds before a region or an entry expires. If timeout is not specified, it defaults to zero (which means no expiration).</td>
<td>-1</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-region-idle-time-expiration-action</span></td>
+<td><span class="keyword parmname">‑‑region-idle-time-expiration-action</span></td>
<td>Action that should take place when a region or an entry expires.
<div class="p">
Select one of the following expiration actions:
@@ -411,12 +411,12 @@ Select one of the following expiration actions:
<td><code class="ph codeph">invalidate</code></td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-region-time-to-live-expiration </span></td>
+<td><span class="keyword parmname">‑‑region-time-to-live-expiration </span></td>
<td>Number of seconds before a region or an entry expires. If timeout is not specified, it defaults to zero (which means no expiration).</td>
<td>-1</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-region-time-to-live-expiration-action</span></td>
+<td><span class="keyword parmname">‑‑region-time-to-live-expiration-action</span></td>
<td>Action that should take place when a region or an entry expires.
<div class="p">
Select one of the following expiration actions:
@@ -501,78 +501,78 @@ alter runtime [--members=value(,value)*] [--groups=value(,value)*]
</thead>
<tbody>
<tr>
-<td><span class="keyword parmname">\-\-members</span></td>
+<td><span class="keyword parmname">‑‑members</span></td>
<td>Name or ID of the member(s) whose configuration is to be altered at runtime. If you do not specify this parameter, the configuration properties are modified for all cluster members using the cluster configuration service.</td>
<td>If not specified, all members using the cluster configuration service</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-groups</span></td>
+<td><span class="keyword parmname">‑‑groups</span></td>
<td>Name of the group(s) whose members's runtime configuration is to be altered. If you do not specify this parameter, the configuration properties are modified for all cluster members using the cluster configuration service.</td>
<td>If not specified, all members using the cluster configuration service</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-archive-disk-space-limit</span></td>
+<td><span class="keyword parmname">‑‑archive-disk-space-limit</span></td>
<td>Archive disk space limit. Maximum size (in megabytes) of all inactive statistic archive files combined. If this limit is exceeded, inactive archive files are deleted, oldest first, until the total size is within the limit. If set to zero, disk space use is unlimited. Valid values are (in megabytes): 0 - 1000000.</td>
<td>0</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-archive-file-size-limit</span></td>
+<td><span class="keyword parmname">‑‑archive-file-size-limit</span></td>
<td>Archive file size limit. The maximum size (in megabytes) of a single statistic archive file. Once this limit is exceeded, a new statistic archive file is created, and the current archive file becomes inactive. If set to zero, file size is unlimited. Valid values are (in megabytes): 0 - 1000000.</td>
<td>0</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-log-disk-space-limit </span></td>
+<td><span class="keyword parmname">‑‑log-disk-space-limit </span></td>
<td>Log disk space limit. Maximum size in megabytes of all inactive log files combined. If this limit is exceeded, inactive log files are deleted, oldest first, until the total size is within the limit. If set to zero, disk space use is unlimited. Valid values are (in megabytes): 0 - 1000000.</td>
<td>0</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-log-file-size-limit</span></td>
+<td><span class="keyword parmname">‑‑log-file-size-limit</span></td>
<td>Log file size limit. Maximum size in megabytes of a log file before it is closed and logging rolls on to a new (child) log file. If set to zero, log rolling is disabled. Valid values are (in megabytes): 0 - 1000000.</td>
<td>0</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-log-level </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: `ALL`, `TRACE`, `DEBUG`, `INFO`, `WARN`, `ERROR`, `FATAL`, `OFF`.
+Valid values are: `ALL`, `TRACE`, `DEBUG`, `INFO`, `WARN`, `ERROR`, `FATAL`, `OFF`.
<td>INFO</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-statistic-archive-file </span></td>
+<td><span class="keyword parmname">‑‑statistic-archive-file </span></td>
<td>The file to which the running system member writes statistic samples. For example: "StatisticsArchiveFile.gfs". Must be defined to store the archiving to a file. Adding the <code>.gz</code> suffix to the file name causes it to be compressed. See <a href="../../../managing/statistics/chapter_overview.html">Statistics</a>.</td>
<td><em>not set</em></td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-statistic-sample-rate </span></td>
+<td><span class="keyword parmname">‑‑statistic-sample-rate </span></td>
<td>Statistic sampling rate. Valid values are (in milliseconds): 100 - 60000. See <a href="../../../managing/statistics/chapter_overview.html">Statistics</a>.</td>
<td>1000</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-enable-statistics</span></td>
+<td><span class="keyword parmname">‑‑enable-statistics</span></td>
<td>Whether statistic sampling should be enabled. Specify <code>--statistic-archive-file</code> to store the statistics to a file. Valid values are: <code class="ph codeph">true</code> and <code class="ph codeph">false</code>. See <a href="../../../managing/statistics/chapter_overview.html">Statistics</a>.</td>
<td>false</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-copy-on-read</span></td>
+<td><span class="keyword parmname">‑‑copy-on-read</span></td>
<td>True or false. Sets the copy on read region attribute for cache read operations. See <a href="../../../basic_config/data_entries_custom_classes/copy_on_read.html">Copy on Read Behavior</a>.</td>
<td>false</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-lock-lease</span></td>
+<td><span class="keyword parmname">‑‑lock-lease</span></td>
<td>Sets the length, in seconds, of distributed lock leases obtained by this cache. See <a href="../../../managing/monitor_tune/performance_controls_setting_cache_timeouts.html#perf">Setting Cache Timeouts</a>.</td>
<td>120</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-lock-timeout</span></td>
+<td><span class="keyword parmname">‑‑lock-timeout</span></td>
<td>Sets the number of seconds a cache operation may wait to obtain a distributed lock lease before timing out. See <a href="../../../managing/monitor_tune/performance_controls_setting_cache_timeouts.html#perf">Setting Cache Timeouts</a>.</td>
<td>60</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-message-sync-interval</span></td>
+<td><span class="keyword parmname">‑‑message-sync-interval</span></td>
<td>Sets the frequency (in seconds) at which a message will be sent by the primary cache-server node to all the secondary cache-server nodes to remove the events which have already been dispatched from the queue. See <a href="../../../developing/events/ha_event_messaging_whats_next.html#ha_event_messaging_whats_next__section_741052B413F24F47A14F5B7D7955F0AA">Change Server Queue Synchronization Frequency</a>.</td>
<td>1</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-search-timeout</span></td>
+<td><span class="keyword parmname">‑‑search-timeout</span></td>
<td>Sets the number of seconds a cache get operation can spend searching for a value. See <a href="../../../managing/monitor_tune/performance_controls_setting_cache_timeouts.html#perf">Setting Cache Timeouts</a>.</td>
<td>300</td>
</tr>
diff --git a/geode-docs/tools_modules/gfsh/command-pages/backup.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/backup.html.md.erb
index 337fd137ba..d3832a842d 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/backup.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/backup.html.md.erb
@@ -51,13 +51,13 @@ backup disk-store --dir=value [--baseline-dir=value]
</thead>
<tbody>
<tr>
-<td><span class="keyword parmname">\-\-dir</span></td>
+<td><span class="keyword parmname">‑‑dir</span></td>
<td><em>Required.</em> Directory to which backup files are written.</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-baseline-dir</span></td>
+<td><span class="keyword parmname">‑‑baseline-dir</span></td>
<td>Directory that contains the baseline backup used for comparison during an incremental backup.
-<p>An incremental backup operation backs up any data that is not present in the directory specified in <span class="keyword parmname">\-\-baseline-dir</span>. If the member cannot find previously backed up data or if the previously backed up data is corrupt, the command performs a full backup on that member.</p></td>
+<p>An incremental backup operation backs up any data that is not present in the directory specified in <span class="keyword parmname">‑‑baseline-dir</span>. If the member cannot find previously backed up data or if the previously backed up data is corrupt, the command performs a full backup on that member.</p></td>
</tr>
</tbody>
</table>
diff --git a/geode-docs/tools_modules/gfsh/command-pages/change.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/change.html.md.erb
index ecf3ac8b66..424dfaf93a 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/change.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/change.html.md.erb
@@ -52,17 +52,17 @@ change loglevel --log-level=value [--members=value(,value)*] [--groups=value(,va
</thead>
<tbody>
<tr>
-<td><span class="keyword parmname">\-\-members</span></td>
+<td><span class="keyword parmname">‑‑members</span></td>
<td>Name or ID of one or more member(s) whose logging level you want to change.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-groups</span></td>
+<td><span class="keyword parmname">‑‑groups</span></td>
<td>One or more group names. The logging level changes for all members of these groups.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-log-level</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>
diff --git a/geode-docs/tools_modules/gfsh/command-pages/close.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/close.html.md.erb
index fe47ca41dd..6f7d7a3219 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/close.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/close.html.md.erb
@@ -46,9 +46,9 @@ close durable-client --durable-client-id=value [--members=value(,value)*]
| Name | Description |
|------------------------------------------------------------|------------------------------------------------------------------------|
-| \\-\\-durable-client-id | *Required.* The ID of the durable client. |
-| \\-\\-members | Name or ID of the member(s) for which the durable client is to be closed. |
-| \\-\\-groups | Group(s) of members for which the durable client is to be closed. |
+| ‑‑durable-client-id | *Required.* The ID of the durable client. |
+| ‑‑members | Name or ID of the member(s) for which the durable client is to be closed. |
+| ‑‑groups | Group(s) of members for which the durable client is to be closed. |
<span class="tablecap">Table 1. Close Durable-Client Parameters</span>
@@ -101,10 +101,10 @@ close durable-cq --durable-client-id=value --durable-cq-name=value
| Name | Description |
|-----------------------------------------------------------|------------------------------------------------------------------------------------------------------|
-| \\-\\-durable-client-id | Required. The ID of the durable client. |
-| \\-\\-durable-cq-name | Required. Name of the CQ to be closed. |
-| \\-\\-members | Name or ID of the member(s) for which the durable client is registered and the durable CQ to be closed. |
-| \\-\\-groups | Group(s) of members for which the durable client is registered and the durable CQ to be closed. |
+| ‑‑durable-client-id | Required. The ID of the durable client. |
+| ‑‑durable-cq-name | Required. Name of the CQ to be closed. |
+| ‑‑members | Name or ID of the member(s) for which the durable client is registered and the durable CQ to be closed. |
+| ‑‑groups | Group(s) of members for which the durable client is registered and the durable CQ to be closed. |
<span class="tablecap">Table 2. Close Durable-CQ Parameters</span>
diff --git a/geode-docs/tools_modules/gfsh/command-pages/compact.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/compact.html.md.erb
index 870307db80..b1f199103f 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/compact.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/compact.html.md.erb
@@ -51,8 +51,8 @@ compact disk-store --name=value [--groups=value(,value)*]
| Name | Description |
|-----------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-name</span> | *Required.* Name of the disk store to be compacted. |
-| <span class="keyword parmname">\\-\\-groups</span> | Group(s) of members that perform disk compaction. If no group is specified, then the disk store is compacted by all members. |
+| <span class="keyword parmname">‑‑name</span> | *Required.* Name of the disk store to be compacted. |
+| <span class="keyword parmname">‑‑groups</span> | Group(s) of members that perform disk compaction. If no group is specified, then the disk store is compacted by all members. |
**Example Commands:**
@@ -95,16 +95,16 @@ compact offline-disk-store --name=value --disk-dirs=value(,value)*
| Name | Description | Default Value |
|--------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|---------------|
-| <span class="keyword parmname">\\-\\-name</span> | *Required.* Name of the offline disk store to be compacted. | |
-| <span class="keyword parmname">\\-\\-disk-dirs</span> | *Required.* One or more directories where data for the disk store was previously written. Separate directories with commas. | |
-| <span class="keyword parmname">\\-\\-max-oplog-size</span> | Maximum size (in megabytes) of the oplogs created by compaction. | -1 |
-| <span class="keyword parmname">\\-\\-J</span> | Arguments passed to the Java Virtual Machine performing the compact operation on the disk store. For example: `-J=-Xmx1024m`. | |
+| <span class="keyword parmname">‑‑name</span> | *Required.* Name of the offline disk store to be compacted. | |
+| <span class="keyword parmname">‑‑disk-dirs</span> | *Required.* One or more directories where data for the disk store was previously written. Separate directories with commas. | |
+| <span class="keyword parmname">‑‑max-oplog-size</span> | Maximum size (in megabytes) of the oplogs created by compaction. | -1 |
+| <span class="keyword parmname">‑‑J</span> | Arguments passed to the Java Virtual Machine performing the compact operation on the disk store. For example: `--J=-Xmx1024m`. | |
**Example Commands:**
``` pre
compact offline-disk-store --name=Disk2 --disk-dirs=/Disks/Disk2
-compact offline-disk-store --name=Disk2 --disk-dirs=/Disks/Disk2 --max-oplog-size=512 -J=-Xmx1024m
+compact offline-disk-store --name=Disk2 --disk-dirs=/Disks/Disk2 --max-oplog-size=512 --J=-Xmx1024m
```
diff --git a/geode-docs/tools_modules/gfsh/command-pages/configure.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/configure.html.md.erb
index 73e150de86..56474913d3 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/configure.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/configure.html.md.erb
@@ -48,11 +48,11 @@ configure pdx [--read-serialized=value] [--ignore-unread-fields=value]
| Name | Description | Default |
|--------------------------------------------|-------------|---------|
-| <span class="keyword parmname">\\-\\-read-serialized</span> | When true, PDX deserialization produces a PdxInstance instead of an instance of the domain class. | false |
-| <span class="keyword parmname">\\-\\-ignore-unread-fields</span> | Controls whether PDX ignores fields that were unread during deserialization. The default is to preserve unread fields by including their data during serialization. However, if you configure the cache to ignore unread fields, then their data will be lost during serialization. You should set this attribute to true only if you know this member will only be reading cache data. In this use case you do not need [...]
-| <span class="keyword parmname">\\-\\-disk-store</span> | Named disk store where the PDX type data will be stored. If specified without a value, then "DEFAULT" is used. | none |
-| <span class="keyword parmname">\\-\\-auto-serializable-classes</span> | Configures ReflectionBasedAutoSerializer as the PDX serializer for member classes. Specifies patterns to be matched against domain class names to determine whether they should be auto-serialized. Classes are not checked for portability to non-java languages (equivalent to `check-portability=false`). | none |
-| <span class="keyword parmname">\\-\\-portable-auto-serializable-classes</span> | Configures ReflectionBasedAutoSerializer as the PDX serializer for member classes. Specifies patterns to be matched against domain class names to determine whether they should be serialized. Serialization done by the PDX autoserializer will throw an exception if the object of these classes are not portable to non-Java languages (equivalent to `check-portability=true`). | none |
+| <span class="keyword parmname">‑‑read-serialized</span> | When true, PDX deserialization produces a PdxInstance instead of an instance of the domain class. | false |
+| <span class="keyword parmname">‑‑ignore-unread-fields</span> | Controls whether PDX ignores fields that were unread during deserialization. The default is to preserve unread fields by including their data during serialization. However, if you configure the cache to ignore unread fields, then their data will be lost during serialization. You should set this attribute to true only if you know this member will only be reading cache data. In this use case you do n [...]
+| <span class="keyword parmname">‑‑disk-store</span> | Named disk store where the PDX type data will be stored. If specified without a value, then "DEFAULT" is used. | none |
+| <span class="keyword parmname">‑‑auto-serializable-classes</span> | Configures ReflectionBasedAutoSerializer as the PDX serializer for member classes. Specifies patterns to be matched against domain class names to determine whether they should be auto-serialized. Classes are not checked for portability to non-java languages (equivalent to `check-portability=false`). | none |
+| <span class="keyword parmname">‑‑portable-auto-serializable-classes</span> | Configures ReflectionBasedAutoSerializer as the PDX serializer for member classes. Specifies patterns to be matched against domain class names to determine whether they should be serialized. Serialization done by the PDX autoserializer will throw an exception if the object of these classes are not portable to non-Java languages (equivalent to `check-portability=true`). | none |
**Example Commands:**
diff --git a/geode-docs/tools_modules/gfsh/command-pages/connect.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/connect.html.md.erb
index 5d85fee16f..8835a1f5ea 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/connect.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/connect.html.md.erb
@@ -64,27 +64,27 @@ connect [--locator=value] [--jmx-manager=value] [--use-http(=value)?] [--url=val
</thead>
<tbody>
<tr>
-<td><span class="keyword parmname">\-\-locator</span></td>
+<td><span class="keyword parmname">‑‑locator</span></td>
<td>Network address of the Locator in the form: <code class="ph codeph">host[port]</code>.</td>
<td><code class="ph codeph">localhost[10334]</code></td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-jmx-manager </span></td>
+<td><span class="keyword parmname">‑‑jmx-manager </span></td>
<td>Network address of the JMX manager in the form: <code class="ph codeph">host[port]</code>.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-use-http</span></td>
+<td><span class="keyword parmname">‑‑use-http</span></td>
<td><b>Deprecated: inferred by the presence of --url.</b> Connects to a JMX manager HTTP service using the HTTP protocol.</td>
<td></td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-url</span></td>
+<td><span class="keyword parmname">‑‑url</span></td>
<td>URL used to connect to a JMX manager's HTTP service.</td>
<td></td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-user</span></td>
+<td><span class="keyword parmname">‑‑username</span><br /><span class="keyword parmname">‑‑user</span></td>
<td>The user name of the credential to use in authentication when connecting
to the JMX manager.
When specified, if the <code>--password</code> option is not also specified,
@@ -94,15 +94,15 @@ This option cannot be used with <code>--token</code>.
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-password</span></td>
-<td>The password portion of the credential to use in authentication
+<td><span class="keyword parmname">‑‑password</span></td>
+<td>The password portion of the credential to use in authentication
when connecting to the JMX manager.
This option cannot be used with <code>--token</code>.
</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-token</span></td>
+<td><span class="keyword parmname">‑‑token</span></td>
<td>The OAuth token to use in authentication
when connecting to the JMX manager. This token will be given to
<code>SecurityManager.authenticate</code> on the JMX manager.
@@ -111,42 +111,42 @@ This option cannot be used with <code>--user</code> or <code>--password</code>.
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-key-store</span></td>
+<td><span class="keyword parmname">‑‑key-store</span></td>
<td>Java keystore file containing this application's certificate and private key. If the<code class="ph codeph"> --key-store-password</code> parameter is not specified, gfsh prompts the operator for the password.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-key-store-password</span></td>
+<td><span class="keyword parmname">‑‑key-store-password</span></td>
<td>Password to access the private key from the keystore file specified by <code class="ph codeph">--key-store</code>.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-trust-store</span></td>
+<td><span class="keyword parmname">‑‑trust-store</span></td>
<td>Java keystore file containing the collection of CA certificates trusted by this application. If the <code class="ph codeph">--trust-store-password</code> parameter is not specified, gfsh prompts the operator for the password.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-trust-store-password</span></td>
+<td><span class="keyword parmname">‑‑trust-store-password</span></td>
<td>Password to unlock the keystore file specified by <code class="ph codeph">--trust-store</code>.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-ciphers</span></td>
+<td><span class="keyword parmname">‑‑ciphers</span></td>
<td>SSL/TLS ciphers used when encrypting the connection. The default is "any".</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-protocols</span></td>
+<td><span class="keyword parmname">‑‑protocols</span></td>
<td>SSL/TLS protocol versions to enable when encrypting the connection. The default is "any".</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-security-properties-file</span></td>
+<td><span class="keyword parmname">‑‑security-properties-file</span></td>
<td>The <code class="ph codeph">gfsecurity.properties</code> file for configuring gfsh to connect to the Locator/Manager. The file path can be absolute or relative to the current gfsh directory.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-use-ssl</span></td>
+<td><span class="keyword parmname">‑‑use-ssl</span></td>
<td>Whether to use SSL for communication with Locator and/or JMX Manager. If set to <code class="ph codeph">true</code>, the connect command also reads <code class="ph codeph">gfsecurity.properties</code>. SSL Options take precedence over values set in the properties file. If none are specified, defaults are used.</td>
<td><ul>
<li>If the parameter is not specified: <code class="ph codeph">false</code></li>
@@ -154,7 +154,7 @@ This option cannot be used with <code>--user</code> or <code>--password</code>.
</ul></td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-skip-ssl-validation</span></td>
+<td><span class="keyword parmname">‑‑skip-ssl-validation</span></td>
<td>When SSL communication is enabled and this option is specified or assigned the value <code>true</code>, this gfsh client accepts any SSL certificate, allowing this gfsh client to authenticate any locator or server to which it is connecting. This option exists to facilitate testing, and it is not intended for production systems.</td>
<td>
<code>false</code>
diff --git a/geode-docs/tools_modules/gfsh/command-pages/create.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/create.html.md.erb
index c276a7198e..a6bb6f04ce 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/create.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/create.html.md.erb
@@ -95,94 +95,94 @@ create async-event-queue --id=value --listener=value [--groups=value(,value)*]
</thead>
<tbody>
<tr>
-<td><span class="keyword parmname">\-\-id</span></td>
+<td><span class="keyword parmname">‑‑id</span></td>
<td><em>Required</em>. ID of the asynchronous event queue</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-groups</span></td>
+<td><span class="keyword parmname">‑‑groups</span></td>
<td>The queue is created on all members of the group(s). If you do not specify a group, the queue is created on all members.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-parallel</span></td>
+<td><span class="keyword parmname">‑‑parallel</span></td>
<td>Specifies whether the queue is parallel.</td>
<td>false</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-enable-batch-conflation</span></td>
+<td><span class="keyword parmname">‑‑enable-batch-conflation</span></td>
<td>Enables batch conflation.</td>
<td>false</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-batch-size</span></td>
+<td><span class="keyword parmname">‑‑batch-size</span></td>
<td>Maximum number of messages that a batch can contain.</td>
<td>100</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-batch-time-interval</span></td>
+<td><span class="keyword parmname">‑‑batch-time-interval</span></td>
<td>Maximum amount of time, in ms, that can elapse before a batch is delivered.</td>
<td>5</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-persistent</span></td>
+<td><span class="keyword parmname">‑‑persistent</span></td>
<td>Boolean value that determines whether <%=vars.product_name%> persists this queue.</td>
<td>false
<p>If specified with out a value, default is true.</p></td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-disk-store</span></td>
+<td><span class="keyword parmname">‑‑disk-store</span></td>
<td>Named disk store to use for storing queue overflow, or for persisting the queue. If you specify a value, the named disk store must exist. If you specify a null value, <%=vars.product_name%> uses the default disk store for overflow and queue persistence.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-disk-synchronous</span></td>
+<td><span class="keyword parmname">‑‑disk-synchronous</span></td>
<td>Specifies whether disk writes are synchronous.</td>
<td>true</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-max-queue-memory</span></td>
+<td><span class="keyword parmname">‑‑max-queue-memory</span></td>
<td>Maximum amount of memory in megabytes that the queue can consume before overflowing to disk.</td>
<td>100</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-dispatcher-threads</span></td>
+<td><span class="keyword parmname">‑‑dispatcher-threads</span></td>
<td>Number of threads used for sending events.</td>
<td>5</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-order-policy</span></td>
-<td>Policy for dispatching events when \-\-dispatcher-threads is > 1. Possible values are <code class="ph codeph">THREAD</code>, <code class="ph codeph">KEY</code>, <code class="ph codeph">PARTITION</code>.</td>
+<td><span class="keyword parmname">‑‑order-policy</span></td>
+<td>Policy for dispatching events when <code>‑‑dispatcher-threads</code> is > 1. Possible values are <code class="ph codeph">THREAD</code>, <code class="ph codeph">KEY</code>, <code class="ph codeph">PARTITION</code>.</td>
<td>KEY</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-gateway-event-filter</span></td>
+<td><span class="keyword parmname">‑‑gateway-event-filter</span></td>
<td>List of fully qualified class names of GatewayEventFilters for this queue. These classes filter events before dispatching to remote servers.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-gateway-event-substitution-filter</span></td>
+<td><span class="keyword parmname">‑‑gateway-event-substitution-filter</span></td>
<td>Fully-qualified class name of the <code class="ph codeph">GatewayEventSubstitutionFilter</code> for this queue.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-listener</span></td>
+<td><span class="keyword parmname">‑‑listener</span></td>
<td><em>Required.</em> Fully-qualified class name of Async Event Listener for this queue</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-listener-param</span></td>
-<td>Parameter name and value to be passed to the Async Event Listener class. Optionally, you can specify a value by following the parameter name with the # character and the value. For example:
+<td><span class="keyword parmname">‑‑listener-param</span></td>
+<td>Parameter name and value to be passed to the Async Event Listener class. Optionally, you can specify a value by following the parameter name with the <code>#</code> character and the value. For example:
<pre class="pre codeblock"><code>--listener-param=myParam#24</code></pre></td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-forward-expiration-destroy</span></td>
+<td><span class="keyword parmname">‑‑forward-expiration-destroy</span></td>
<td>Enables forwarding of expiration destroy operations to AsyncEventListener instances. If specified without a value, this parameter is set to “false”.</td>
<td>false</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-pause-event-processing</span></td>
+<td><span class="keyword parmname">‑‑pause-event-processing</span></td>
<td>Specifies whether event dispatching from the queue to the listener(s) will be paused when the AsyncEventQueue is started. If specified without a value, this parameter is set to "true".</td>
<td>false</td>
</tr>
@@ -213,8 +213,8 @@ create defined indexes [--members=value(,value)*] [--groups=value(,value)*]
| Name | Description | Default |
|------------------------------------------------|--------------------------------------------------------------------|---------|
-| <span class="keyword parmname">\\-\\-members</span> | Name/Id of the member(s) on which index will be created. | |
-| <span class="keyword parmname">\\-\\-groups</span> | The index will be created on all the members in the member group(s). | |
+| <span class="keyword parmname">‑‑members</span> | Name/Id of the member(s) on which index will be created. | |
+| <span class="keyword parmname">‑‑groups</span> | The index will be created on all the members in the member group(s). | |
**Example Commands:**
@@ -235,7 +235,7 @@ If index creation fails, you may receive an error message in gfsh similar to the
``` pre
gfsh>create defined indexes
-Exception : org.apache.geode.cache.query.RegionNotFoundException ,
+Exception : org.apache.geode.cache.query.RegionNotFoundException ,
Message : Region ' /r3' not found: from /r3Occurred on following members
1. india(s1:17866)<v1>:27809
```
@@ -251,7 +251,7 @@ See [Disk Storage](../../../managing/disk_storage/chapter_overview.html)
**Syntax:**
``` pre
-create disk-store --name=value --dir=value(,value)* [--allow-force-compaction(=value)?]
+create disk-store --name=value --dir=value(,value)* [--allow-force-compaction(=value)?]
[--auto-compact(=value)?] [--compaction-threshold=value] [--max-oplog-size=value]
[--queue-size=value] [--time-interval=value] [--write-buffer-size=value]
[--groups=value(,value)*]
@@ -276,45 +276,45 @@ create disk-store --name=value --dir=value(,value)* [--allow-force-compaction(=v
</thead>
<tbody>
<tr>
-<td><span class="keyword parmname">\-\-name</span></td>
+<td><span class="keyword parmname">‑‑name</span></td>
<td><em>Required.</em> The name of this disk store.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-dir</span></td>
+<td><span class="keyword parmname">‑‑dir</span></td>
<td><em>Required.</em> One or more directory names where the disk store files are written. Optionally, directory names may be followed by <code class="ph codeph">#</code> and the maximum number of megabytes that the disk store can use in the directory. For example:
-<pre class="pre codeblock"><code>--dir=/data/ds1
+<pre class="pre codeblock"><code>--dir=/data/ds1
--dir=/data/ds2#5000</code></pre>
If the specified directory does not exist, the command will create the directory for you.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-allow-force-compaction</span></td>
+<td><span class="keyword parmname">‑‑allow-force-compaction</span></td>
<td>Set to true to allow disk compaction to be forced on this disk store.</td>
<td>false</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-auto-compact</span></td>
+<td><span class="keyword parmname">‑‑auto-compact</span></td>
<td>Set to true to automatically compact the disk files.</td>
<td>true</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-compaction-threshold</span></td>
+<td><span class="keyword parmname">‑‑compaction-threshold</span></td>
<td>Percentage of non-garbage remaining, below which the disk store is eligible for compaction.</td>
<td>50</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-max-oplog-size</span></td>
+<td><span class="keyword parmname">‑‑max-oplog-size</span></td>
<td>Maximum size, in megabytes, for an oplog file. When the oplog file reaches this size, the file is rolled over to a new file.</td>
<td>1024</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-queue-size</span></td>
+<td><span class="keyword parmname">‑‑queue-size</span></td>
<td>Maximum number of operations that can be asynchronously queued to be written to disk.</td>
<td>0</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-time-interval</span></td>
+<td><span class="keyword parmname">‑‑time-interval</span></td>
<td>The number of milliseconds that can elapse before unwritten data is written to disk.</td>
<td>1000</td>
</tr>
@@ -324,18 +324,18 @@ If the specified directory does not exist, the command will create the directory
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-write-buffer-size</span></td>
-<td>The size of the write buffer that this disk store uses when writing data to disk. Larger values may increase performance but use more memory. The disk store allocates one direct memory buffer of this size.</td>
+<td><span class="keyword parmname">‑‑write-buffer-size</span></td>
+<td>The size in bytes of the write buffer that this disk store uses when writing data to disk. Larger values may increase performance but use more memory. The disk store allocates one direct memory buffer of this size.</td>
<td>32768</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-disk-usage-warning-percentage</span></td>
+<td><span class="keyword parmname">‑‑disk-usage-warning-percentage</span></td>
<td>Disk usage above this threshold generates a warning message. For example, if the threshold is set to 90%, then on a 1 TB drive falling under 100 GB of free disk space generates the warning.
<p>Set to "0" (zero) to disable.</p></td>
<td>90</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-disk-usage-critical-percentage</span></td>
+<td><span class="keyword parmname">‑‑disk-usage-critical-percentage</span></td>
<td>Disk usage above this threshold generates an error message and shuts down the member's cache. For example, if the threshold is set to 99%, then falling under 10 GB of free disk space on a 1 TB drive generates the error and shuts down the cache.
<p>Set to "0" (zero) to disable.</p></td>
<td>99</td>
@@ -379,8 +379,8 @@ See [Gateway Receivers](../../../topologies_and_comm/topology_concepts/multisite
**Syntax:**
``` pre
-create gateway-receiver [--groups=value(,value)*] [--members=value(,value)*]
- [--manual-start=(value)?] [--start-port=value] [--end-port=value] [--bind-address=value]
+create gateway-receiver [--groups=value(,value)*] [--members=value(,value)*]
+ [--manual-start=(value)?] [--start-port=value] [--end-port=value] [--bind-address=value]
[--maximum-time-between-pings=value] [--socket-buffer-size=value]
[--gateway-transport-filter=value(,value)*] [--hostname-for-senders=value]
[--if-not-exists=(value)?]
@@ -403,12 +403,12 @@ create gateway-receiver [--groups=value(,value)*] [--members=value(,value)*]
</thead>
<tbody>
<tr>
-<td><span class="keyword parmname">\-\-groups</span></td>
+<td><span class="keyword parmname">‑‑groups</span></td>
<td>Gateway receivers are created on the members of the group(s).</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-members</span></td>
+<td><span class="keyword parmname">‑‑members</span></td>
<td>Name of the member(s) on which to create the gateway receiver.
For backward compatibility, no gateway receiver configuration is persisted
if this option is specified and cluster configuration is enabled.
@@ -416,49 +416,49 @@ if this option is specified and cluster configuration is enabled.
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-manual-start</span></td>
+<td><span class="keyword parmname">‑‑manual-start</span></td>
<td>Boolean value that specifies whether you need to manually start the gateway receiver. When specified without providing a boolean value or when specified and set to "true", the gateway receiver must be started manually.</td>
<td>false</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-start-port</span></td>
+<td><span class="keyword parmname">‑‑start-port</span></td>
<td><p>Starting port number to use when specifying the range of possible port numbers this gateway receiver will use to connects to gateway senders in other sites. <%=vars.product_name%> chooses an unused port number in the specified port number range to start the receiver. If no port numbers in the range are available, an exception is thrown.</p>
<p>The <code class="ph codeph">start-port</code> and <code class="ph codeph">end-port</code> values are inclusive. For example, if you specify <code class="ph codeph">start-port="50510"</code> and <code class="ph codeph">end-port="50520"</code>, <%=vars.product_name%> chooses a port value from 50510 to 50520.</p></td>
<td>5000</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-end-port</span></td>
+<td><span class="keyword parmname">‑‑end-port</span></td>
<td><p>Defines the upper bound port number to use when specifying the range of possible port numbers this gateway receiver will use to for connections from gateway senders in other sites. <%=vars.product_name%> chooses an unused port number in the specified port number range to start the receiver. If no port numbers in the range are available, an exception is thrown.</p>
<p>The <code class="ph codeph">end-port</code> and <code class="ph codeph">start-port</code> values are inclusive. For example, if you specify <code class="ph codeph">start-port="50510"</code> and <code class="ph codeph">end-port="50520"</code>, <%=vars.product_name%> chooses a port value from 50510 to 50520.</p></td>
<td>5500</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-bind-address</span></td>
+<td><span class="keyword parmname">‑‑bind-address</span></td>
<td>Network address for connections from gateway senders in other sites. Specify the address as a literal string value.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-socket-buffer-size</span></td>
+<td><span class="keyword parmname">‑‑socket-buffer-size</span></td>
<td>An integer value that sets the buffer size (in bytes) of the socket connection for this gateway receiver. This value should match the <code class="ph codeph">socket-buffer-size</code> setting of gateway senders that connect to this receiver.</td>
<td>32768</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-gateway-transport-filter</span></td>
+<td><span class="keyword parmname">‑‑gateway-transport-filter</span></td>
<td>The fully qualified class name of the GatewayTransportFilter to be added to the Gateway receiver.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-maximum-time-between-pings</span></td>
+<td><span class="keyword parmname">‑‑maximum-time-between-pings</span></td>
<td>Integer value that specifies the time interval (in milliseconds) to use between pings to connected WAN sites. This value determines the maximum amount of time that can elapse before a remote WAN site is considered offline.</td>
<td>60000</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-hostname-for-senders</span></td>
+<td><span class="keyword parmname">‑‑hostname-for-senders</span></td>
<td>The host name or IP address told to gateway senders as the address for them to connect to. The locator informs gateway senders of this value.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-if-not-exists</span></td>
+<td><span class="keyword parmname">‑‑if-not-exists</span></td>
<td>When specified without providing a boolean value or when specified and set to "true", gateway receivers will not be created if they already exist. Command output reports the status of each creation attempt.
</td>
<td>false</td>
@@ -496,12 +496,12 @@ The gateway sender configuration for a specific sender `id` must be identical on
**Syntax:**
``` pre
-create gateway-sender --id=value --remote-distributed-system-id=value
+create gateway-sender --id=value --remote-distributed-system-id=value
[--groups=value(,value)*] [--members=value(,value)*] [--parallel(=value)?]
- [--manual-start=value] [--socket-buffer-size=value] [--socket-read-timeout=value]
+ [--manual-start=value] [--socket-buffer-size=value] [--socket-read-timeout=value]
[--enable-batch-conflation=value] [--batch-size=value] [--batch-time-interval=value]
- [--enable-persistence=value] [--disk-store-name=value] [--disk-synchronous=value]
- [--maximum-queue-memory=value] [--alert-threshold=value] [--dispatcher-threads=value]
+ [--enable-persistence=value] [--disk-store-name=value] [--disk-synchronous=value]
+ [--maximum-queue-memory=value] [--alert-threshold=value] [--dispatcher-threads=value]
[--order-policy=value][--gateway-event-filter=value(,value)*]
[--gateway-transport-filter=value(,value)*]
[--group-transaction-events(=value)?]
@@ -524,92 +524,92 @@ create gateway-sender --id=value --remote-distributed-system-id=value
</thead>
<tbody>
<tr>
-<td><span class="keyword parmname">\-\-id</span></td>
+<td><span class="keyword parmname">‑‑id</span></td>
<td><em>Required.</em> Unique identifier for the gateway sender, usually an identifier associated with a physical location.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-remote-distributed-system-id</span></td>
+<td><span class="keyword parmname">‑‑remote-distributed-system-id</span></td>
<td><em>Required.</em> ID of the remote cluster where this gateway sender sends events.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-groups</span></td>
+<td><span class="keyword parmname">‑‑groups</span></td>
<td>Gateway senders are created on the members of the group(s).</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-members</span></td>
+<td><span class="keyword parmname">‑‑members</span></td>
<td>Name of the member(s) on which to create the gateway sender.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-parallel</span></td>
+<td><span class="keyword parmname">‑‑parallel</span></td>
<td>When set to true, specifies a parallel Gateway Sender.</td>
<td>false</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-enable-batch-conflation</span></td>
+<td><span class="keyword parmname">‑‑enable-batch-conflation</span></td>
<td>Boolean value that determines whether <%=vars.product_name%> should conflate messages.</td>
<td>false</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-manual-start</span></td>
+<td><span class="keyword parmname">‑‑manual-start</span></td>
<td><b>Deprecated.</b> Boolean value that specifies whether you need to manually start the gateway sender. If you supply a null value, the default value of false is used, and the gateway sender starts automatically. <em>A manual start is likely to cause data loss, so manual start should never be used in a production system.</em></td>
<td>false</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-socket-buffer-size</span></td>
+<td><span class="keyword parmname">‑‑socket-buffer-size</span></td>
<td>Size of the socket buffer that sends messages to remote sites. This size should match the size of the <code class="ph codeph">socket-buffer-size</code> attribute of remote gateway receivers that process region events.</td>
<td>32768</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-socket-read-timeout</span></td>
+<td><span class="keyword parmname">‑‑socket-read-timeout</span></td>
<td>Amount of time in milliseconds that the gateway sender will wait to receive an acknowledgment from a remote site. By default this is set to 0, which means there is no timeout. If you do set this timeout, you must set it to a minimum of 30000 (milliseconds). Setting it to a lower number will generate an error message and reset the value to the default of 0.</td>
<td>0</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-batch-size</span></td>
+<td><span class="keyword parmname">‑‑batch-size</span></td>
<td>Maximum number of messages that a batch can contain.</td>
<td>100</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-batch-time-interval</span></td>
+<td><span class="keyword parmname">‑‑batch-time-interval</span></td>
<td>Maximum number of milliseconds that can elapse between sending batches.</td>
<td>1000</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-enable-persistence</span></td>
+<td><span class="keyword parmname">‑‑enable-persistence</span></td>
<td>Boolean value that determines whether <%=vars.product_name%> persists the gateway queue.</td>
<td>false</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-disk-store-name</span></td>
-<td>Named disk store to use for storing the queue overflow, or for persisting the queue. If you specify a value, the named disk store must exist. If you specify a null value, <%=vars.product_name%> uses the default disk store for overflow and queue persistence. For parallel gateway senders, set this to the same disk store the region uses.</td>
+<td><span class="keyword parmname">‑‑disk-store-name</span></td>
+<td>Named disk store to use for storing the queue overflow, or for persisting the queue. If you specify a value, the named disk store must exist. If you specify a null value, <%=vars.product_name%> uses the default disk store for overflow and queue persistence.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-disk-synchronous</span></td>
+<td><span class="keyword parmname">‑‑disk-synchronous</span></td>
<td>For regions that write to disk, boolean that specifies whether disk writes are done synchronously for the region.</td>
<td>true</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-maximum-queue-memory</span></td>
+<td><span class="keyword parmname">‑‑maximum-queue-memory</span></td>
<td>Maximum amount of memory in megabytes that the queue can consume before overflowing to disk.</td>
<td>100 MB</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-alert-threshold</span></td>
+<td><span class="keyword parmname">‑‑alert-threshold</span></td>
<td>Maximum number of milliseconds that a region event can remain in the gateway sender queue before <%=vars.product_name%> logs an alert.</td>
<td>0</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-dispatcher-threads</span></td>
+<td><span class="keyword parmname">‑‑dispatcher-threads</span></td>
<td>Number of dispatcher threads that are used to process region events from a gateway sender queue or asynchronous event queue.</td>
<td>5</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-order-policy</span></td>
+<td><span class="keyword parmname">‑‑order-policy</span></td>
<td>When the <code class="ph codeph">dispatcher-threads</code> attribute is greater than 1, <code class="ph codeph">order-policy</code> configures the way in which multiple dispatcher threads process region events from a serial gateway queue or serial asynchronous event queue. This attribute can have one of the following values:
<dt><b>key</b></dt>
<dd>When distributing region events from the local queue, multiple dispatcher threads preserve the order of key updates.</dd>
@@ -622,18 +622,18 @@ create gateway-sender --id=value --remote-distributed-system-id=value
<td>key</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-gateway-event-filter</span></td>
+<td><span class="keyword parmname">‑‑gateway-event-filter</span></td>
<td>A list of fully-qualified class names of GatewayEventFilters (separated by commas) to be associated with the GatewaySender. This serves as a callback for users to filter out events before dispatching to a remote cluster. For example:
<pre class="pre codeblock"><code>gateway-event-filter=com.user.filters.MyFilter1,com.user.filters.MyFilters2</code></pre></td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-gateway-transport-filter</span></td>
+<td><span class="keyword parmname">‑‑gateway-transport-filter</span></td>
<td>The fully-qualified class name of the GatewayTransportFilter to be added to the GatewaySender.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-group-transaction-events</span></td>
+<td><span class="keyword parmname">‑‑group-transaction-events</span></td>
<td>Boolean value to ensure that all the events of a transaction are sent in the same batch, i.e., they are never spread across different batches.
<p>Only allowed to be set on gateway senders with the <code class="ph codeph">parallel</code> attribute set to false and <code class="ph codeph">dispatcher-threads</code> attribute equal to 1, or on gateway senders with the <code class="ph codeph">parallel</code> attribute set to true. Also, the <code class="ph codeph">enable-batch-conflation</code> attribute of the gateway sender must be set to false.</p>
<p><b>Note:</b> In order to work for a transaction, the regions to which the transaction events belong must be replicated by the same set of senders with this flag enabled.</p>
@@ -642,7 +642,7 @@ create gateway-sender --id=value --remote-distributed-system-id=value
</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-enforce-threads-connect-same-receiver</span></td>
+<td><span class="keyword parmname">‑‑enforce-threads-connect-same-receiver</span></td>
<td>This parameter applies only to serial gateway senders. If true, receiver member id is checked by all dispatcher threads when the connection is established to ensure they connect to the same receiver. Instead of starting all dispatcher threads in parallel, one thread is started first, and after that the rest are started in parallel.</td>
<td>false</td>
</tr>
@@ -675,7 +675,7 @@ See [Working with Indexes](../../../developing/query_index/query_index.html).
**Syntax:**
``` pre
-create index --name=value --expression=value --region=value
+create index --name=value --expression=value --region=value
[--members=value(,value)*] [--type=value] [--groups=value(,value)*]
```
@@ -683,12 +683,12 @@ create index --name=value --expression=value --region=value
| Name | Description | Default |
|----------------------------------------------------|----------------------------------------------------------------------------------------|---------|
-| <span class="keyword parmname">\\-\\-name</span> | *Required.* Name of the index to create. | |
+| <span class="keyword parmname">‑‑name</span> | *Required.* Name of the index to create. | |
| <span class="keyword parmname">‑‑expression</span> | *Required.* Field of the region values that are referenced by the index. | |
-| <span class="keyword parmname">\\-\\-region</span> | *Required.* Name/Path of the region which corresponds to the "from" clause in a query. | |
-| <span class="keyword parmname">\\-\\-members</span> | Name/Id of the member(s) on which index will be created. | |
-| <span class="keyword parmname">\\-\\-type</span> | Type of the index. Valid values are: `range` and `key`. (A third type, `hash`, is still recognized but hash indexes are deprecated.) | `range` |
-| <span class="keyword parmname">\\-\\-groups</span> | The index will be created on all the members in the group(s). | |
+| <span class="keyword parmname">‑‑region</span> | *Required.* Name/Path of the region which corresponds to the "from" clause in a query. | |
+| <span class="keyword parmname">‑‑members</span> | Name/Id of the member(s) on which index will be created. | |
+| <span class="keyword parmname">‑‑type</span> | Type of the index. Valid values are: `range` and `key`. (A third type, `hash`, is still recognized but hash indexes are deprecated.) | `range` |
+| <span class="keyword parmname">‑‑groups</span> | The index will be created on all the members in the group(s). | |
**Example Commands:**
@@ -738,23 +738,23 @@ create jndi-binding --name=value --url=value
| Name | Description | Default |
|----------------------------------------------------|----------------------------------------------------------------------------------------|---------|
-| <span class="keyword parmname">\\-\\-name</span> | *Required.* Name of the binding to create. | |
+| <span class="keyword parmname">‑‑name</span> | *Required.* Name of the binding to create. | |
| <span class="keyword parmname">‑‑url or ‑‑connection-url</span> | *Required.* the JDBC driver connection URL string. For example, `jdbc:hsqldb:hsql://localhost:1701`. | |
-| <span class="keyword parmname">\\-\\-jdbc-driver-class</span> | The fully qualified name of the JDBC driver class. | |
-| <span class="keyword parmname">\\-\\-type</span> | Type of the XA datasource. One of: `MANAGED`, `SIMPLE`, `POOLED`, or `XAPOOLED`. If `--type=POOLED` and a `--conn-pooled-datasource-class` option is not specified, a pool will be created using Hikari. For more information on Hikari, see [https://brettwooldridge.github.io/HikariCP](https://brettwooldridge.github.io/HikariCP). | `SIMPLE` |
-| <span class="keyword parmname">\\-\\-blocking-timeout-seconds</span> | Specifies the maximum time, in seconds, to block while waiting for a connection before throwing an exception. | |
-| <span class="keyword parmname">\\-\\-conn-pooled-datasource-class</span> | The fully qualified name of the connection pool implementation that holds XA datasource connections. If `--type=POOLED`, then this class must implement `org.apache.geode.datasource.PooledDataSourceFactory`. | |
-| <span class="keyword parmname">\\-\\-idle-timeout-seconds</span> | Specifies the time, in seconds, that a connection may be idle before being closed. | |
-| <span class="keyword parmname">\\-\\-init-pool-size</span> | Specifies the initial number of connections the pool should hold. | |
-| <span class="keyword parmname">\\-\\-login-timeout-seconds</span> | The quantity of seconds after which the client thread will be disconnected due to inactivity. | |
-| <span class="keyword parmname">\\-\\-managed-conn-factory-class</span> | The fully qualified name of the connection factory implementation. | |
-| <span class="keyword parmname">\\-\\-max-pool-size</span> | The maximum number of connections that may be created in a pool. | |
-| <span class="keyword parmname">\\-\\-password</span> | The default password used when creating a new connection. | |
-| <span class="keyword parmname">\\-\\-transaction-type</span> | Type of the transaction. One of `XATransaction`, `NoTransaction`, or `LocalTransaction`. | |
-| <span class="keyword parmname">\\-\\-username</span> | Specifies the user name to be used when creating a new connection. When specified, if the `--password` option is not also specified, gfsh will prompt for the password. | |
-| <span class="keyword parmname">\\-\\-xa-datasource-class</span> | The fully qualified name of the `javax.sql.XADataSource` implementation class. | |
-| <span class="keyword parmname">\\-\\-if-not-exists</span> | When true, a duplicate jndi binding will not be created if one with the same name already exists. When false, an attempt to create a duplicate jndi binding results in an error. The option is set to true if the option is specified without a value. | false |
-| <span class="keyword parmname">\\-\\-datasource-config-properties</span> | Properties for the custom `XADataSource` driver. Append a JSON string containing a (name, type, value) tuple to set any property. If `--type=POOLED`, the properties will configure the database data source. If `--type=POOLED` and the value of a name within the tuple begins with the string "pool.", then the properties will configure the pool data source. For example: `--datasource-config-properties={'name':'name [...]
+| <span class="keyword parmname">‑‑jdbc-driver-class</span> | The fully qualified name of the JDBC driver class. | |
+| <span class="keyword parmname">‑‑type</span> | Type of the XA datasource. One of: `MANAGED`, `SIMPLE`, `POOLED`, or `XAPOOLED`. If `--type=POOLED` and a `--conn-pooled-datasource-class` option is not specified, a pool will be created using Hikari. For more information on Hikari, see [https://brettwooldridge.github.io/HikariCP](https://brettwooldridge.github.io/HikariCP). | `SIMPLE` |
+| <span class="keyword parmname">‑‑blocking-timeout-seconds</span> | Specifies the maximum time, in seconds, to block while waiting for a connection before throwing an exception. | |
+| <span class="keyword parmname">‑‑conn-pooled-datasource-class</span> | The fully qualified name of the connection pool implementation that holds XA datasource connections. If `--type=POOLED`, then this class must implement `org.apache.geode.datasource.PooledDataSourceFactory`. | |
+| <span class="keyword parmname">‑‑idle-timeout-seconds</span> | Specifies the time, in seconds, that a connection may be idle before being closed. | |
+| <span class="keyword parmname">‑‑init-pool-size</span> | Specifies the initial number of connections the pool should hold. | |
+| <span class="keyword parmname">‑‑login-timeout-seconds</span> | The quantity of seconds after which the client thread will be disconnected due to inactivity. | |
+| <span class="keyword parmname">‑‑managed-conn-factory-class</span> | The fully qualified name of the connection factory implementation. | |
+| <span class="keyword parmname">‑‑max-pool-size</span> | The maximum number of connections that may be created in a pool. | |
+| <span class="keyword parmname">‑‑password</span> | The default password used when creating a new connection. | |
+| <span class="keyword parmname">‑‑transaction-type</span> | Type of the transaction. One of `XATransaction`, `NoTransaction`, or `LocalTransaction`. | |
+| <span class="keyword parmname">‑‑username</span> | Specifies the user name to be used when creating a new connection. When specified, if the `--password` option is not also specified, gfsh will prompt for the password. | |
+| <span class="keyword parmname">‑‑xa-datasource-class</span> | The fully qualified name of the `javax.sql.XADataSource` implementation class. | |
+| <span class="keyword parmname">‑‑if-not-exists</span> | When true, a duplicate jndi binding will not be created if one with the same name already exists. When false, an attempt to create a duplicate jndi binding results in an error. The option is set to true if the option is specified without a value. | false |
+| <span class="keyword parmname">‑‑datasource-config-properties</span> | Properties for the custom `XADataSource` driver. Append a JSON string containing a (name, type, value) tuple to set any property. If `--type=POOLED`, the properties will configure the database data source. If `--type=POOLED` and the value of a name within the tuple begins with the string "pool.", then the properties will configure the pool data source. For example: `--datasource-config-properties={'nam [...]
**Example Commands:**
@@ -783,22 +783,22 @@ create lucene index --name=value --region=value --field=value(,value)*
| Name | Description | Default |
|----------------------------------------------------|----------------------------------------------------------------------------------------|---------|
-| <span class="keyword parmname">\\-\\-name</span> | *Required.* Name of the index to create. | |
-| <span class="keyword parmname">\\-\\-region</span> | *Required.* Name/Path of the region on which to define the index. | |
-| <span class="keyword parmname">\\-\\-field</span> | *Required.* Field(s) of the region values that are referenced by the index, specified as a comma-separated list. To treat the entire value as a single field, specify `__REGION_VALUE_FIELD`. | |
+| <span class="keyword parmname">‑‑name</span> | *Required.* Name of the index to create. | |
+| <span class="keyword parmname">‑‑region</span> | *Required.* Name/Path of the region on which to define the index. | |
+| <span class="keyword parmname">‑‑field</span> | *Required.* Field(s) of the region values that are referenced by the index, specified as a comma-separated list. To treat the entire value as a single field, specify `__REGION_VALUE_FIELD`. | |
| <span class="keyword parmname">‑‑analyzer</span> | Analyzer(s) to extract terms from text, specified as a comma-separated list. If not specified, the default analyzer is used for all fields. If specified, the number of analyzers must exactly match the number of fields specified. When listing analyzers, use the keyword `DEFAULT` for any field that will use the default analyzer. | Lucene `StandardAnalyzer` |
| <span class="keyword parmname">‑‑serializer</span> | Fully qualified class name of the serializer to be used with this index. The serializer must implement the `LuceneSerializer` interface. You can use the built-in `org.apache.geode.cache.lucene.FlatFormatSerializer` to index and search collections and nested fields. If not specified, the simple default serializer is used, which indexes and searches only the top level fields of the region objects. | simple serializer |
-| <span class="keyword parmname">\\-\\-group</span> | The index will be created on all the members in the specified member groups. | |
+| <span class="keyword parmname">‑‑group</span> | The index will be created on all the members in the specified member groups. | |
**Example Commands:**
``` pre
-gfsh>create lucene index --name=customerIndex --region=/Customer
+gfsh>create lucene index --name=customerIndex --region=/Customer
--field=__REGION_VALUE_FIELD
-gfsh>create lucene index --name=analyzerIndex --region=/Person
- --field=name,email,address,revenue
+gfsh>create lucene index --name=analyzerIndex --region=/Person
+ --field=name,email,address,revenue
--analyzer=DEFAULT,org.apache.lucene.analysis.core.KeywordAnalyzer,
examples.MyCharacterAnalyzer,DEFAULT
```
@@ -872,219 +872,219 @@ for syntax details.
</thead>
<tbody>
<tr>
-<td><span class="keyword parmname">\-\-name</span></td>
+<td><span class="keyword parmname">‑‑name</span></td>
<td><em>Required.</em> Name/Path of the region to be created.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-type</span></td>
+<td><span class="keyword parmname">‑‑type</span></td>
<td><em>Required</em> (if template-region is not specified.) Type of region to create. Options include: PARTITION, PARTITION_REDUNDANT, REPLICATE, LOCAL, etc.
-<p>To get a list of of all region type options, add the <span class="keyword parmname">\-\-type</span> parameter and then select the TAB key to display a full list.</p></td>
+<p>To get a list of of all region type options, add the <span class="keyword parmname">‑‑type</span> parameter and then select the TAB key to display a full list.</p></td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-template-region </span></td>
+<td><span class="keyword parmname">‑‑template-region </span></td>
<td><em>Required</em> (if type is not specified.) Name/Path of the region whose attributes should be duplicated when creating this region.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-groups</span></td>
+<td><span class="keyword parmname">‑‑groups</span></td>
<td>Group(s) of members on which the region will be created.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-if-not-exists</span></td>
+<td><span class="keyword parmname">‑‑if-not-exists</span></td>
<td>A new region will not be created if a region with the same name already exists. By default, an attempt to create a duplicate region is reported as an error.
If this option is specified without a value or is specified with a value of <code>true</code>, then gfsh displays a "Skipping..." acknowledgement, but does not throw an error.</td>
<td>false</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-key-constraint</span></td>
+<td><span class="keyword parmname">‑‑key-constraint</span></td>
<td>Fully qualified class name of the objects allowed as region keys. Ensures that keys for region entries are all of the same class.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-value-constraint </span></td>
+<td><span class="keyword parmname">‑‑value-constraint </span></td>
<td>Fully qualified class name of the objects allowed as region values. If not specified, then region values can be of any class.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-enable-statistics</span></td>
+<td><span class="keyword parmname">‑‑enable-statistics</span></td>
<td>Whether to gather statistics for the region. Must be true to use expiration on the region.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-entry-idle-time-expiration</span></td>
+<td><span class="keyword parmname">‑‑entry-idle-time-expiration</span></td>
<td>How long, in seconds, the region's entries can remain in the cache without being accessed.</td>
<td>no expiration</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-entry-idle-time-expiration-action </span></td>
+<td><span class="keyword parmname">‑‑entry-idle-time-expiration-action </span></td>
<td>Action to be taken on an entry that has exceeded the idle expiration. Valid expiration actions include destroy, local-destroy, invalidate (default), local-invalidate.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-entry-time-to-live-expiration</span></td>
+<td><span class="keyword parmname">‑‑entry-time-to-live-expiration</span></td>
<td>How long, in seconds, the region's entries can remain in the cache without being accessed or updated. The default is no expiration of this type.</td>
<td>no expiration</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-entry-time-to-live-expiration-action</span></td>
+<td><span class="keyword parmname">‑‑entry-time-to-live-expiration-action</span></td>
<td>Action to be taken on an entry that has exceeded the TTL expiration. Valid expiration actions include destroy, local-destroy, invalidate (default), local-invalidate.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-entry-idle-time-custom-expiry</span></td>
+<td><span class="keyword parmname">‑‑entry-idle-time-custom-expiry</span></td>
<td>The name of a class implementing CustomExpiry for entry idle time. Append a JSON string for initialization properties.</td>
<td></td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-entry-time-to-live-custom-expiry</span></td>
+<td><span class="keyword parmname">‑‑entry-time-to-live-custom-expiry</span></td>
<td>The name of a class implementing CustomExpiry for entry time to live. Append a JSON string for initialization properties.</td>
<td></td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-region-idle-time-expiration</span></td>
+<td><span class="keyword parmname">‑‑region-idle-time-expiration</span></td>
<td>How long, in seconds, the region can remain in the cache without its entries being accessed. The default is no expiration of this type.</td>
<td></td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-region-idle-time-expiration-action</span></td>
+<td><span class="keyword parmname">‑‑region-idle-time-expiration-action</span></td>
<td>Action to be taken on a region that has exceeded the idle expiration. Valid expiration actions include destroy, local-destroy, invalidate (default), local-invalidate. The destroy and local-destroy actions destroy the region. The invalidate and local-invalidate actions leave the region in place, but invalidate all of its entries.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-region-time-to-live-expiration</span></td>
+<td><span class="keyword parmname">‑‑region-time-to-live-expiration</span></td>
<td>How long, in seconds, the region can remain in the cache without its entries being accessed or updated. The default is no expiration of this type.</td>
<td>no expiration</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-region-time-to-live-expiration-action</span></td>
+<td><span class="keyword parmname">‑‑region-time-to-live-expiration-action</span></td>
<td>Action to be taken on a region that has exceeded the TTL expiration. Valid expiration actions include destroy, local-destroy, invalidate (default), local-invalidate. The destroy and local-destroy actions destroy the region. The invalidate and local-invalidate actions leave the region in place, but invalidate all of its entries.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-disk-store</span></td>
+<td><span class="keyword parmname">‑‑disk-store</span></td>
<td>Disk Store to be used by this region. The <a href="list.html#topic_BC14AD57EA304FB3845766898D01BD04">list disk-stores</a> command can be used to display existing disk stores.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-enable-synchronous-disk</span></td>
+<td><span class="keyword parmname">‑‑enable-synchronous-disk</span></td>
<td>Whether writes are done synchronously for regions that persist data to disk.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-enable-async-conflation</span></td>
+<td><span class="keyword parmname">‑‑enable-async-conflation</span></td>
<td>Whether to allow aggregation of asynchronous TCP/IP messages sent by the producer member of the region. A false value causes all asynchronous messages to be sent individually.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-enable-subscription-conflation</span></td>
+<td><span class="keyword parmname">‑‑enable-subscription-conflation</span></td>
<td>Whether the server should conflate its messages to the client. A false value causes all server-client messages to be sent individually.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-cache-listener</span></td>
+<td><span class="keyword parmname">‑‑cache-listener</span></td>
<td>Fully qualified class name of a plug-in to be instantiated for receiving after-event notification of changes to the region and its entries. Any number of cache listeners can be configured. A fully qualified class name may be appended with a JSON specification that will be parsed to become the fields of the parameter to the <code>init()</code> method for a class that implements the <code>Declarable</code> interface.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-cache-loader</span></td>
+<td><span class="keyword parmname">‑‑cache-loader</span></td>
<td>Fully qualified class name of a plug-in to be instantiated for receiving notification of cache misses in the region. At most, one cache loader can be defined in each member for the region. For distributed regions, a cache loader may be invoked remotely from other members that have the region defined. A fully qualified class name may be appended with a JSON specification that will be parsed to become the fields of the parameter to the <code>initialize()</code> method for a class that [...]
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-cache-writer</span></td>
+<td><span class="keyword parmname">‑‑cache-writer</span></td>
<td>Fully qualified class name of a plug-in to be instantiated for receiving before-event notification of changes to the region and its entries. The plug-in may cancel the event. At most, one cache writer can be defined in each member for the region. A fully qualified class name may be appended with a JSON specification that will be parsed to become the fields of the parameter to the <code>init()</code> method for a class that implements the <code>Declarable</code> interface.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-async-event-queue-id</span></td>
+<td><span class="keyword parmname">‑‑async-event-queue-id</span></td>
<td>IDs of the Async Event Queues that will be used for write-behind operations.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-gateway-sender-id</span></td>
+<td><span class="keyword parmname">‑‑gateway-sender-id</span></td>
<td>IDs of the Gateway Senders to which data will be routed.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-enable-concurrency-checks</span></td>
+<td><span class="keyword parmname">‑‑enable-concurrency-checks</span></td>
<td>Whether Region Version Vectors are implemented. Region Version Vectors are an extension to the versioning scheme that aid in synchronization of replicated regions.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-enable-cloning</span></td>
+<td><span class="keyword parmname">‑‑enable-cloning</span></td>
<td>Determines how fromDelta applies deltas to the local cache for delta propagation. When true, the updates are applied to a clone of the value and then the clone is saved to the cache. When false, the value is modified in place in the cache.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-concurrency-level </span></td>
+<td><span class="keyword parmname">‑‑concurrency-level </span></td>
<td>Estimate of the maximum number of application threads that will concurrently access a region entry at one time. This attribute does not apply to partitioned regions.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-colocated-with </span></td>
+<td><span class="keyword parmname">‑‑colocated-with </span></td>
<td>Central Region with which this region should be colocated.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-local-max-memory</span></td>
+<td><span class="keyword parmname">‑‑local-max-memory</span></td>
<td>Maximum amount of memory, in megabytes, to be used by the region in this process. (The default is 90% of available heap.)</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-recovery-delay </span></td>
+<td><span class="keyword parmname">‑‑recovery-delay </span></td>
<td>Delay in milliseconds that existing members will wait after a member crashes before restoring this region's redundancy on the remaining members. The default value (-1) indicates that redundancy will not be recovered after a failure.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-redundant-copies </span></td>
+<td><span class="keyword parmname">‑‑redundant-copies </span></td>
<td>Number of extra copies of buckets desired. Extra copies allow for both high availability in the face of VM departure (intended or unintended) and load balancing read operations. (Allowed values: 0, 1, 2 and 3)</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-startup-recovery-delay </span></td>
+<td><span class="keyword parmname">‑‑startup-recovery-delay </span></td>
<td>Delay in milliseconds that new members will wait before assuming their share of cluster-level redundancy. This allows time for multiple regions to start before the redundancy workload is parceled out to the new members. A value of -1 indicates that adding new members will not trigger redundancy recovery.</td>
<td>The default is to recover redundancy immediately when a new member is added.</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-total-max-memory </span></td>
+<td><span class="keyword parmname">‑‑total-max-memory </span></td>
<td>Maximum amount of memory, in megabytes, to be used by the region in all processes.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-total-num-buckets </span></td>
+<td><span class="keyword parmname">‑‑total-num-buckets </span></td>
<td>Total number of hash buckets to be used by the region in all processes.</td>
<td>113</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-compressor</span></td>
+<td><span class="keyword parmname">‑‑compressor</span></td>
<td>Java class name that implements compression for the region. You can write a custom compressor that implements <code class="ph codeph">org.apache.geode.compression.Compressor</code> or you can specify the Snappy compressor (<code class="ph codeph">org.apache.geode.compression.SnappyCompressor</code>), which is bundled with <%=vars.product_name%>. See <a href="../../../managing/region_compression.html">Region Compression</a>.</td>
<td>no compression</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-off-heap</span></td>
+<td><span class="keyword parmname">‑‑off-heap</span></td>
<td>Specifies whether the region values are stored in heap memory or off-heap memory. When true, region values are in off-heap memory. If the parameter is specified without a value, the value of true is used.</td>
<td>false</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-partition-resolver</span></td>
+<td><span class="keyword parmname">‑‑partition-resolver</span></td>
<td>Specifies the full path to a custom partition resolver. Specify <code class="ph codeph">org.apache.geode.cache.util.StringPrefixPartitionResolver</code> to use the included string prefix partition resolver.</td>
<td></td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-eviction-entry-count</span></td>
+<td><span class="keyword parmname">‑‑eviction-entry-count</span></td>
<td>Enables eviction, where the eviction policy is based on the number of entries in the region.</td>
<td></td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-eviction-max-memory</span></td>
+<td><span class="keyword parmname">‑‑eviction-max-memory</span></td>
<td>Enables eviction, where the eviction policy is based on the amount of memory consumed by the region, specified in megabytes.</td>
<td></td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-eviction-action</span></td>
+<td><span class="keyword parmname">‑‑eviction-action</span></td>
<td>Action to take when the eviction threshold is reached.
<div class="p">
<table>
@@ -1104,7 +1104,7 @@ If this option is specified without a value or is specified with a value of <cod
<td></td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-eviction-object-sizer</span></td>
+<td><span class="keyword parmname">‑‑eviction-object-sizer</span></td>
<td>Specifies your implementation of the ObjectSizer interface to measure the size of objects in the region.
The sizer applies only to heap and memory based eviction.</td>
<td></td>
@@ -1129,7 +1129,7 @@ org.apache.geode.examples.MyCacheListener2 \
create region --name=region3 --type=PARTITION_PERSISTENT --redundant-copies=2 \
--total-max-memory=1000 --startup-recovery-delay=5 --total-num-buckets=100 \
--disk-store=DiskStore2 --cache-listener=org.apache.geode.examples.MyCacheListener3 \
---group=Group2
+--group=Group2
create region --name=region4 --type=REPLICATE_PROXY \
--cache-listener=org.apache.geode.examples.MyCacheListener1 --group=Group1,Group2
@@ -1149,5 +1149,3 @@ Member | Status
------- | ---------------------------------------
server1 | Region "/myRegion" created on "server1"
```
-
-
diff --git a/geode-docs/tools_modules/gfsh/command-pages/define.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/define.html.md.erb
index b6f961a720..38dba44925 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/define.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/define.html.md.erb
@@ -33,10 +33,10 @@ define index --name=value --expression=value --region=value [--type=value]
| Name | Description | Default Value |
|----------------------------------------------------|----------------------------------------------------------------------------------------|---------------|
-| <span class="keyword parmname">\\-\\-name </span> | *Required.* Name of the index to define. | |
+| <span class="keyword parmname">‑‑name </span> | *Required.* Name of the index to define. | |
| <span class="keyword parmname">‑‑expression</span> | *Required.* Field of the region values that are referenced by the index. | |
-| <span class="keyword parmname">\\-\\-region</span> | *Required.* Name/Path of the region which corresponds to the "from" clause in a query. | |
-| <span class="keyword parmname">\\-\\-type</span> | Type of the index. Valid values are: range, key and hash. | range |
+| <span class="keyword parmname">‑‑region</span> | *Required.* Name/Path of the region which corresponds to the "from" clause in a query. | |
+| <span class="keyword parmname">‑‑type</span> | Type of the index. Valid values are: range, key and hash. | range |
<span class="tablecap">Table 1. Define Index Parameters</span>
diff --git a/geode-docs/tools_modules/gfsh/command-pages/deploy.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/deploy.html.md.erb
index 0564b9ca9c..f1d406e062 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/deploy.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/deploy.html.md.erb
@@ -36,8 +36,8 @@ deploy [--groups=value(,value)*] [--jars=value(,value)*] [--dir=value]
| Name | Description |
|-----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|
| <span class="keyword parmname">‑‑groups</span> | Group(s) to which the specified JARs will be deployed. If this option is not specified, the deployment will occur on all members. |
-| <span class="keyword parmname">\\-\\-jars</span> | Path(s) of the JAR(s) to deploy. |
-| <span class="keyword parmname">\\-\\-dir</span> | Directory from which to deploy the JARs. |
+| <span class="keyword parmname">‑‑jars</span> | Path(s) of the JAR(s) to deploy. |
+| <span class="keyword parmname">‑‑dir</span> | Directory from which to deploy the JARs. |
<span class="tablecap">Table 1. Deploy Parameters</span>
diff --git a/geode-docs/tools_modules/gfsh/command-pages/describe.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/describe.html.md.erb
index 5e04d865f4..1cba0733ee 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/describe.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/describe.html.md.erb
@@ -121,8 +121,8 @@ describe config --member=value [--hide-defaults(=value)?]
| Name | Description | Default Value |
|-------------------------------------------------------|----------------------------------------------------------------------------------|---------------|
-| <span class="keyword parmname">\\-\\-member </span> | Name or ID of a member whose configuration is to be shown. | |
-| <span class="keyword parmname">\\-\\-hide-defaults</span> | Whether to hide configuration information for properties with the default value. | true |
+| <span class="keyword parmname">‑‑member </span> | Name or ID of a member whose configuration is to be shown. | |
+| <span class="keyword parmname">‑‑hide-defaults</span> | Whether to hide configuration information for properties with the default value. | true |
**Example Commands:**
@@ -204,8 +204,8 @@ describe disk-store --member=value --name=value
| Name | Description |
|------------------------------------------------|------------------------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-member</span> | *Required.* Name/ID of the member with the disk store to be described. |
-| <span class="keyword parmname">\\-\\-name </span> | *Required*. Name of the disk store to be described. |
+| <span class="keyword parmname">‑‑member</span> | *Required.* Name/ID of the member with the disk store to be described. |
+| <span class="keyword parmname">‑‑name </span> | *Required*. Name of the disk store to be described. |
**Example Commands:**
@@ -257,7 +257,7 @@ describe jndi-binding --name=value
| Name | Description |
|----------------------------------------------------|------------------------------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-name</span> | *Required.* Name of the JNDI binding to be described. |
+| <span class="keyword parmname">‑‑name</span> | *Required.* Name of the JNDI binding to be described. |
**Example Commands:**
@@ -296,8 +296,8 @@ describe lucene index --name=value --region=value
| Name | Description |
|----------------------------------------------------|------------------------------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-name</span> | *Required.* Name of the Lucene index to describe |
-| <span class="keyword parmname">\\-\\-region</span> | *Required.* Name and path of the region in which the Lucene index exists |
+| <span class="keyword parmname">‑‑name</span> | *Required.* Name of the Lucene index to describe |
+| <span class="keyword parmname">‑‑region</span> | *Required.* Name and path of the region in which the Lucene index exists |
@@ -389,10 +389,10 @@ describe offline-disk-store --name=value --disk-dirs=value(,value)* [--pdx=value
| Name | Description |
|----------------------------------------------------|------------------------------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-name</span> | *Required.* Name of the disk store to be described. |
-| <span class="keyword parmname">\\-\\-disk-dirs </span> | *Required.* Directory that contains the disk store files. |
-| <span class="keyword parmname">\\-\\-pdx</span> | If set (or set to true), display all the pdx types stored in the disk store. |
-| <span class="keyword parmname">\\-\\-region</span> | Name and path of the region in the disk store to be described. |
+| <span class="keyword parmname">‑‑name</span> | *Required.* Name of the disk store to be described. |
+| <span class="keyword parmname">‑‑disk-dirs </span> | *Required.* Directory that contains the disk store files. |
+| <span class="keyword parmname">‑‑pdx</span> | If set (or set to true), display all the pdx types stored in the disk store. |
+| <span class="keyword parmname">‑‑region</span> | Name and path of the region in the disk store to be described. |
**Example Commands:**
@@ -490,7 +490,7 @@ describe region --name=value
| Name | Description |
|-----------------------------------------------|------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-name </span> | *Required.* Name/Path of the region to be described. |
+| <span class="keyword parmname">‑‑name </span> | *Required.* Name/Path of the region to be described. |
**Example Commands:**
diff --git a/geode-docs/tools_modules/gfsh/command-pages/destroy.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/destroy.html.md.erb
index be6b082459..194581c4e0 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/destroy.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/destroy.html.md.erb
@@ -74,7 +74,7 @@ destroy async-event-queue --id=value [--groups=value(,value)*] [--if-exists=valu
| Name | Description |
|-----------------------------------------------|---------------------------------------------------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-id</span> | *Required.* ID of the async event queue to be deleted. |
+| <span class="keyword parmname">‑‑id</span> | *Required.* ID of the async event queue to be deleted. |
| <span class="keyword parmname">‑‑groups</span> | Group(s) of members on which the async event queue will be destroyed. If no group is specified, the queue is destroyed on all members. |
| ‑‑if‑exists | If the specified async event queue does not exist, gfsh responds with a message to that effect. If this parameter is true, the response is prefixed with the label "Skipping: ". Useful for scripted tests. Default (if the parameter is not specified): false. Default (if the parameter is specified without value): true. |
@@ -101,7 +101,7 @@ destroy disk-store --name=value [--groups=value(,value)*] [--if-exists=value]
| Name | Description |
|-----------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-name</span> | *Required.* Name of the disk store to be deleted. |
+| <span class="keyword parmname">‑‑name</span> | *Required.* Name of the disk store to be deleted. |
| <span class="keyword parmname">‑‑groups</span> | Group(s) of members on which the disk store will be destroyed. If no group is specified, the disk store is destroyed on all members. |
| ‑‑if‑exists | If the specified disk store does not exist, gfsh responds with a message to that effect. If this parameter is true, the response is prefixed with the label "Skipping: ". Useful for scripted tests. Default (if the parameter is not specified): false. Default (if the parameter is specified without value): true. |
@@ -139,8 +139,8 @@ destroy function --id=value [--groups=value(,value)*] [--member=value]
| Name | Description |
|------------------------------------------------|--------------------------------------------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-id</span> | *Required.* Unique function identifier. Use the `list functions` command to obtain the ID. |
-| <span class="keyword parmname">\\-\\-groups</span> | One or more groups of members from which this function will be unregistered. |
+| <span class="keyword parmname">‑‑id</span> | *Required.* Unique function identifier. Use the `list functions` command to obtain the ID. |
+| <span class="keyword parmname">‑‑groups</span> | One or more groups of members from which this function will be unregistered. |
| <span class="keyword parmname">‑‑member</span> | Name or ID of the member from which this function will be unregistered. |
@@ -170,7 +170,7 @@ destroy gateway-receiver [--group=value(,value)*]
| Name | Description |
|------------------------------------------------|--------------------------------------------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-group</span> | One or more groups of members on which the gateway receiver will be destroyed. |
+| <span class="keyword parmname">‑‑group</span> | One or more groups of members on which the gateway receiver will be destroyed. |
| <span class="keyword parmname">‑‑members</span> | Name or ID of each member on which the gateway receiver will be destroyed. |
| ‑‑if‑exists | If this option is true and the gateway receiver does not exist, gfsh responds with a message prefixed with the label "Skipping: ". If this option is false and the gateway receiver does not exist, an error message is output. Default (if this option is not specified): false. Default (if this option is specified without a value): true. |
@@ -214,8 +214,8 @@ destroy gateway-sender --id=value [--groups=value(,value)*]
| Name | Description |
|------------------------------------------------|--------------------------------------------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-id</span> | *Required.* Unique gateway sender identifier. Use the `list gateways` command to obtain the ID. |
-| <span class="keyword parmname">\\-\\-groups</span> | One or more groups of members from which this gateway sender will be destroyed. |
+| <span class="keyword parmname">‑‑id</span> | *Required.* Unique gateway sender identifier. Use the `list gateways` command to obtain the ID. |
+| <span class="keyword parmname">‑‑groups</span> | One or more groups of members from which this gateway sender will be destroyed. |
| <span class="keyword parmname">‑‑members</span> | Name or ID of the member(s) from which this gateway sender will be destroyed. |
| ‑‑if‑exists | If the specified gateway sender does not exist, gfsh responds with a message to that effect. If this parameter is true, the response is prefixed with the label "Skipping: ". Useful for scripted tests. Default (if the parameter is not specified): false. Default (if the parameter is specified without value): true. |
@@ -245,10 +245,10 @@ You must specify at least one of the parameter options. If you enter `destroy in
| Name | Description |
|------------------------------------------------|------------------------------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-name</span> | Name of the index to be removed. |
+| <span class="keyword parmname">‑‑name</span> | Name of the index to be removed. |
| ‑‑members | Id of the member(s) on which index is to be removed. |
-| <span class="keyword parmname">\\-\\-region</span> | Name of the region from which an index or all indexes are to be destroyed. |
-| <span class="keyword parmname">\\-\\-groups</span> | The index will be removed on all the members in the group(s). |
+| <span class="keyword parmname">‑‑region</span> | Name of the region from which an index or all indexes are to be destroyed. |
+| <span class="keyword parmname">‑‑groups</span> | The index will be removed on all the members in the group(s). |
| ‑‑if‑exists | If the specified index does not exist, gfsh responds with a message to that effect. If this parameter is true, the response is prefixed with the label "Skipping: ". Useful for scripted tests. Default (if the parameter is not specified): false. Default (if the parameter is specified without value): true. |
@@ -276,7 +276,7 @@ destroy jndi-binding --name=value [--if-exists=value]
| Name | Description |
|----------------------------------------------|--------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-name</span> | *Required.* Name of the JNDI binding to be destroyed. |
+| <span class="keyword parmname">‑‑name</span> | *Required.* Name of the JNDI binding to be destroyed. |
| ‑‑if‑exists | Skip the destroy operation when the specified JNDI binding does not exist. Without this option, an error results from the specification of a JNDI binding that does not exist. Default (if the parameter is not specified): false. Default (if the parameter is specified without value): true. |
**Example Command:**
@@ -330,7 +330,7 @@ destroy region --name=value [--if-exists=value]
| Name | Description |
|----------------------------------------------|--------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-name</span> | *Required.* Name and path of the region to be removed. |
+| <span class="keyword parmname">‑‑name</span> | *Required.* Name and path of the region to be removed. |
| ‑‑if‑exists | If the specified region does not exist, gfsh responds with a message to that effect. If this parameter is true, the response is prefixed with the label "Skipping: ". Useful for scripted tests. Default (if the parameter is not specified): false. Default (if the parameter is specified without value): true. |
diff --git a/geode-docs/tools_modules/gfsh/command-pages/echo.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/echo.html.md.erb
index a76a33ee0e..75a5deb734 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/echo.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/echo.html.md.erb
@@ -37,7 +37,7 @@ echo [--string=value]
| Name | Description |
|-------------------------------------------------|--------------------------------------------------------------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-string </span> | String to be echoed. For example, `SYS_USER variable is set to ${SYS_USER}`. |
+| <span class="keyword parmname">‑‑string </span> | String to be echoed. For example, `SYS_USER variable is set to ${SYS_USER}`. |
<span class="tablecap">Table 1. Echo Parameters</span>
diff --git a/geode-docs/tools_modules/gfsh/command-pages/execute.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/execute.html.md.erb
index bb8b76438f..ff2a6cdd49 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/execute.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/execute.html.md.erb
@@ -39,13 +39,13 @@ execute function --id=value [--groups=value(,value)*]
| | |
|----------------------------------------------------------|-------------------------------------------------------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-id</span> | *Required.* ID of the function to execute. |
-| <span class="keyword parmname">\\-\\-groups</span> | One or more groups of members on which this function should be executed. |
-| <span class="keyword parmname">\\-\\-members</span> | Name/ID of the member(s) on which the function will be executed. |
-| <span class="keyword parmname">\\-\\-region</span> | Region on which the data dependent function will be executed. |
-| <span class="keyword parmname">\\-\\-arguments</span> | Arguments to the function in comma separated string format. |
-| <span class="keyword parmname">\\-\\-result-collector</span> | Fully qualified class name of the `ResultCollector` to instantiate for gathering results. |
-| <span class="keyword parmname">\\-\\-filter</span> | Key list which causes the function to only be executed on members which have entries with these keys. |
+| <span class="keyword parmname">‑‑id</span> | *Required.* ID of the function to execute. |
+| <span class="keyword parmname">‑‑groups</span> | One or more groups of members on which this function should be executed. |
+| <span class="keyword parmname">‑‑members</span> | Name/ID of the member(s) on which the function will be executed. |
+| <span class="keyword parmname">‑‑region</span> | Region on which the data dependent function will be executed. |
+| <span class="keyword parmname">‑‑arguments</span> | Arguments to the function in comma separated string format. |
+| <span class="keyword parmname">‑‑result-collector</span> | Fully qualified class name of the `ResultCollector` to instantiate for gathering results. |
+| <span class="keyword parmname">‑‑filter</span> | Key list which causes the function to only be executed on members which have entries with these keys. |
<span class="tablecap">Table 1. Execute Function Parameters</span>
diff --git a/geode-docs/tools_modules/gfsh/command-pages/export.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/export.html.md.erb
index adaed01003..0fc1a76be7 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/export.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/export.html.md.erb
@@ -108,9 +108,9 @@ export config [--members=value(,value)*] [--groups=value(,value)*]
| Name | Description |
|------------------------------------------------|----------------------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-members</span> | Name/Id of the member(s) whose configuration will be exported. |
-| <span class="keyword parmname">\\-\\-groups</span> | Group(s) of members whose configuration will be exported. |
-| <span class="keyword parmname">\\-\\-dir</span> | Directory to which the exported configuration files will be written. |
+| <span class="keyword parmname">‑‑members</span> | Name/Id of the member(s) whose configuration will be exported. |
+| <span class="keyword parmname">‑‑groups</span> | Group(s) of members whose configuration will be exported. |
+| <span class="keyword parmname">‑‑dir</span> | Directory to which the exported configuration files will be written. |
**Example Commands:**
@@ -159,11 +159,11 @@ In this scenario, partitioned region data is exported simultaneously on all host
| Name | Description |
|------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-region</span> | *Required.* Region from which data is to be exported. |
+| <span class="keyword parmname">‑‑region</span> | *Required.* Region from which data is to be exported. |
| <span class="keyword parmname">‑‑member</span> | *Required.* Name/Id of a member that hosts the region. In a serial export, all data is exported to the specified file on the host where the member is running. In a parallel export, data from a partitioned region partially hosted on this member is exported for each partition to files on the nodes that host those partitions. |
-| <span class="keyword parmname">\\-\\-file</span> | File to which the exported data is to be written. The file must have an extension of `.gfd`. Cannot be specified at the same time as \\-\\-dir, cannot be used with ‑‑parallel.|
-| <span class="keyword parmname">\\-\\-dir</span> | Directory to which the exported data is to be written. Required if \\-\\-parallel is true. Cannot be specified at the same time as \\-\\-file.|
-| <span class="keyword parmname">\\-\\-parallel</span> | Export local data on each node to a directory on that machine. Available for partitioned regions only. |
+| <span class="keyword parmname">‑‑file</span> | File to which the exported data is to be written. The file must have an extension of `.gfd`. Cannot be specified at the same time as ‑‑dir, cannot be used with ‑‑parallel.|
+| <span class="keyword parmname">‑‑dir</span> | Directory to which the exported data is to be written. Required if ‑‑parallel is true. Cannot be specified at the same time as ‑‑file.|
+| <span class="keyword parmname">‑‑parallel</span> | Export local data on each node to a directory on that machine. Available for partitioned regions only. |
**Example Commands:**
@@ -202,17 +202,17 @@ export logs [--dir=value] [--groups=value(,value)*] [--members=value(,value)*]
| Name | Description | Default Value |
|--------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------|---------------|
-| <span class="keyword parmname">\\-\\-dir</span> | Local directory to which log files will be written when logs are exported using an http connection. Ignored when the command is executed over JMX. | |
-| <span class="keyword parmname">\\-\\-groups</span> | Group(s) of members whose log files will be exported. | |
+| <span class="keyword parmname">‑‑dir</span> | Local directory to which log files will be written when logs are exported using an http connection. Ignored when the command is executed over JMX. | |
+| <span class="keyword parmname">‑‑groups</span> | Group(s) of members whose log files will be exported. | |
| <span class="keyword parmname">‑‑members</span> | Name/ID of the member(s) whose log files will be exported. | |
-| <span class="keyword parmname">\\-\\-log-level</span> | Minimum level of log entries to export. Valid values are: `OFF`, `FATAL`, `ERROR`, `WARN`, `INFO`, `DEBUG`, `TRACE`, and `ALL`. | `INFO` |
-| <span class="keyword parmname">\\-\\-only-log-level</span> | Whether to only include only entries that exactly match the <span class="keyword parmname">\\-\\-log-level</span> specified. | false |
+| <span class="keyword parmname">‑‑log-level</span> | Minimum level of log entries to export. Valid values are: `OFF`, `FATAL`, `ERROR`, `WARN`, `INFO`, `DEBUG`, `TRACE`, and `ALL`. | `INFO` |
+| <span class="keyword parmname">‑‑only-log-level</span> | Whether to only include only entries that exactly match the <span class="keyword parmname">‑‑log-level</span> specified. | false |
| <span class="keyword parmname">‑‑merge‑log</span> | Whether to merge logs after exporting to the target directory (deprecated). | false |
-| <span class="keyword parmname">\\-\\-start-time</span> | Log entries that occurred after this time will be exported. Format: `yyyy/MM/dd/HH/mm/ss/SSS/z` OR `yyyy/MM/dd`. When using the `yyyy/MM/dd/HH/mm/ss/SSS/z` format, the time zone, denoted `z`, should be specified as either a 3-letter time zone such as `PST` or as an offset to GMT/UTC such as `GMT+08:00`. | no limit |
-| <span class="keyword parmname">\\-\\-end-time</span> | Log entries that occurred before this time will be exported. Format: `yyyy/MM/dd/HH/mm/ss/SSS/z` OR `yyyy/MM/dd`. When using the `yyyy/MM/dd/HH/mm/ss/SSS/z` format, the time zone, denoted `z`, should be specified as either a 3-letter time zone such as `PST` or as an offset to GMT/UTC such as `GMT+08:00`. An end time specified by only a date implements a time of `00:00`. This exports logs written up until `23:59:59.999` on the [...]
-| <span class="keyword parmname">\\-\\-logs-only</span> | Whether to export only logs (not statistics) | If parameter not specified: false. If parameter specified without a value: true |
-| <span class="keyword parmname">\\-\\-stats-only</span> | Whether to export only statistics (not logs) | If parameter not specified: false. If parameter specified without a value: true |
-| <span class="keyword parmname">\\-\\-file-size-limit</span> | Limits total unzipped size of the exported files. Specify 0 (zero) for no limit. Value is in megabytes by default or [k,m,g,t] may be specified. | If parameter not specified: 100m. If parameter specified without a value: 0 |
+| <span class="keyword parmname">‑‑start-time</span> | Log entries that occurred after this time will be exported. Format: `yyyy/MM/dd/HH/mm/ss/SSS/z` OR `yyyy/MM/dd`. When using the `yyyy/MM/dd/HH/mm/ss/SSS/z` format, the time zone, denoted `z`, should be specified as either a 3-letter time zone such as `PST` or as an offset to GMT/UTC such as `GMT+08:00`. | no limit |
+| <span class="keyword parmname">‑‑end-time</span> | Log entries that occurred before this time will be exported. Format: `yyyy/MM/dd/HH/mm/ss/SSS/z` OR `yyyy/MM/dd`. When using the `yyyy/MM/dd/HH/mm/ss/SSS/z` format, the time zone, denoted `z`, should be specified as either a 3-letter time zone such as `PST` or as an offset to GMT/UTC such as `GMT+08:00`. An end time specified by only a date implements a time of `00:00`. This exports logs written up until `23:59:59.999 [...]
+| <span class="keyword parmname">‑‑logs-only</span> | Whether to export only logs (not statistics) | If parameter not specified: false. If parameter specified without a value: true |
+| <span class="keyword parmname">‑‑stats-only</span> | Whether to export only statistics (not logs) | If parameter not specified: false. If parameter specified without a value: true |
+| <span class="keyword parmname">‑‑file-size-limit</span> | Limits total unzipped size of the exported files. Specify 0 (zero) for no limit. Value is in megabytes by default or [k,m,g,t] may be specified. | If parameter not specified: 100m. If parameter specified without a value: 0 |
**Example commands, showing output:**
@@ -254,9 +254,9 @@ export offline-disk-store --name=value --disk-dirs=value(,value)* --dir=value
| Name | Description |
|---------------------------------------------------|----------------------------------------------------|
-| <span class="keyword parmname">\\-\\-name</span> | *Required.* Name of the disk store to be exported. |
-| <span class="keyword parmname">\\-\\-disk-dirs</span> | Directories which contain the disk store files. |
-| <span class="keyword parmname">\\-\\-dir</span> | Directory to export the snapshot files to. |
+| <span class="keyword parmname">‑‑name</span> | *Required.* Name of the disk store to be exported. |
+| <span class="keyword parmname">‑‑disk-dirs</span> | Directories which contain the disk store files. |
+| <span class="keyword parmname">‑‑dir</span> | Directory to export the snapshot files to. |
**Example Commands:**
@@ -282,10 +282,10 @@ export stack-traces [--members=value(,value)*] [--groups=value(,value)*]
| Name | Description |
|------------------------------------------------|-----------------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-members</span> | Name or ID of the member(s) whose stack traces will be exported. |
-| <span class="keyword parmname">\\-\\-groups</span> | Group(s) of members whose stack traces will be exported. |
-| <span class="keyword parmname">\\-\\-file</span> | File name to which the stack traces will be written. When not specified, the file name will be the string "stacktrace_" followed by the current time in milliseconds. |
-| <span class="keyword parmname">\\-\\-abort-if-file-exists</span> | When true, abort the command if the file already exists in the locator's directory. If this option is not specified, the default value is false. |
+| <span class="keyword parmname">‑‑members</span> | Name or ID of the member(s) whose stack traces will be exported. |
+| <span class="keyword parmname">‑‑groups</span> | Group(s) of members whose stack traces will be exported. |
+| <span class="keyword parmname">‑‑file</span> | File name to which the stack traces will be written. When not specified, the file name will be the string "stacktrace_" followed by the current time in milliseconds. |
+| <span class="keyword parmname">‑‑abort-if-file-exists</span> | When true, abort the command if the file already exists in the locator's directory. If this option is not specified, the default value is false. |
**Example Commands:**
diff --git a/geode-docs/tools_modules/gfsh/command-pages/gc.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/gc.html.md.erb
index f9ee8089f1..81246a5f00 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/gc.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/gc.html.md.erb
@@ -39,8 +39,8 @@ gc [--groups=value(,value)*] [--member=value]
| Name | Description |
|------------------------------------------------|-----------------------------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-groups</span> | One or more group(s) of members on which garbage collection will be forced. |
-| <span class="keyword parmname">\\-\\-member</span> | Name/ID of the member on which garbage collection will be forced. |
+| <span class="keyword parmname">‑‑groups</span> | One or more group(s) of members on which garbage collection will be forced. |
+| <span class="keyword parmname">‑‑member</span> | Name/ID of the member on which garbage collection will be forced. |
<span class="tablecap">Table 1. GC Parameters</span>
diff --git a/geode-docs/tools_modules/gfsh/command-pages/get.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/get.html.md.erb
index a1886e5e4a..2e8ed25a3e 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/get.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/get.html.md.erb
@@ -33,11 +33,11 @@ get --key=value --region=value [--key-class=value] [--value-class=value]
| Name | Description | Default Value |
|------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-key </span> | *Required.* String or JSON text from which to create the key. For example: "`James`", "`100L`" and "`('id': 'l34s')`". | |
+| <span class="keyword parmname">‑‑key </span> | *Required.* String or JSON text from which to create the key. For example: "`James`", "`100L`" and "`('id': 'l34s')`". | |
| <span class="keyword parmname">‑‑region</span> | *Required.* Region from which to get the entry. | |
-| <span class="keyword parmname">\\-\\-key-class</span> | Fully qualified class name of the key's type. | The default is the key constraint for the current region or String. |
-| <span class="keyword parmname">\\-\\-value-class</span> | Fully qualified class name of the value's type. | The default is the value constraint for the current region or String. |
-| <span class="keyword parmname">\\-\\-load-on-cache-miss</span> | Explicitly enables or disables the use of any registered CacheLoaders on the specified Region when retrieving a value for the specified Key on Cache misses. | true (enabled) |
+| <span class="keyword parmname">‑‑key-class</span> | Fully qualified class name of the key's type. | The default is the key constraint for the current region or String. |
+| <span class="keyword parmname">‑‑value-class</span> | Fully qualified class name of the value's type. | The default is the value constraint for the current region or String. |
+| <span class="keyword parmname">‑‑load-on-cache-miss</span> | Explicitly enables or disables the use of any registered CacheLoaders on the specified Region when retrieving a value for the specified Key on Cache misses. | true (enabled) |
<span class="tablecap">Table 1. Get Parameters</span>
diff --git a/geode-docs/tools_modules/gfsh/command-pages/history.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/history.html.md.erb
index aa625c2d04..adb28f8f62 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/history.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/history.html.md.erb
@@ -39,8 +39,8 @@ history [--file=<history text file>]
| Name | Description | Default Value |
|---------|----------------------------------------------------------|---------------|
-| \\-\\-file | File to which the history is to be saved. | |
-| \\-\\-clear | When set to `true`, clears the history of gfsh commands. | false |
+| ‑‑file | File to which the history is to be saved. | |
+| ‑‑clear | When set to `true`, clears the history of gfsh commands. | false |
<span class="tablecap">Table 1. History Parameters</span>
diff --git a/geode-docs/tools_modules/gfsh/command-pages/import.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/import.html.md.erb
index 005b0c6889..7e0bcaea10 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/import.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/import.html.md.erb
@@ -56,7 +56,7 @@ import cluster-configuration [--action=value] [--group(=value)?]
| <span class="keyword parmname">‑‑action</span> | When the value is `APPLY` (the default), the configuration is applied to the running servers that have no configuration. If any servers already have configuration, the command fails. When the value is `STAGE`, the configuration is overwritten and will be used during future server creation; the configuration of currently running servers is not changed. | |
| <span class="keyword parmname">‑‑group</span> | Do the import for the specified server group. When no group is specified, the `cluster` is implied. | |
| <span class="keyword parmname">‑‑xml-file</span> | Filename from which to import the cluster configuration. May also include an absolute or relative path. Only specify one of `--xml-file` or `--zip-file-name`. | |
-| <span class="keyword parmname">\\-\\-zip-file-name</span> | Name of the ZIP file containing the cluster configuration artifacts to be imported. Only specify one of `--xml-file` or `--zip-file-name`. | |
+| <span class="keyword parmname">‑‑zip-file-name</span> | Name of the ZIP file containing the cluster configuration artifacts to be imported. Only specify one of `--xml-file` or `--zip-file-name`. | |
**Example Commands:**
@@ -108,10 +108,10 @@ In this scenario, partitioned region data is imported simultaneously on all host
| Name | Description | Default Value |
|------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|
-| <span class="keyword parmname">\\-\\-region</span> | *Required.* Region into which data will be imported. | |
+| <span class="keyword parmname">‑‑region</span> | *Required.* Region into which data will be imported. | |
| <span class="keyword parmname">‑‑member</span> | *Required.* Name/ID of a member that hosts the region. In a serial import, all data is imported from the specified file on the host where the member is running. In a parallel import, data from a partitioned region partially hosted on this member is imported for each partition from files on the nodes that host those partitions. | |
-| <span class="keyword parmname">\\-\\-file </span> | File from which the imported data will be read. The file must have an extension of `.gfd` and must be on the file system of the member (or accessible to that member via NFS) that is being targeted for the import. Cannot be specified at the same time as \\-\\-dir, cannot be used with ‑‑parallel. | |
-| <span class="keyword parmname">\\-\\-dir</span> | Directory from which the data is to be imported. Required if \\-\\-parallel is true. Cannot be specified at the same time as \\-\\-file. If a given node has no data file in the specified directory, the import operation is silently skipped for that node. | |
+| <span class="keyword parmname">‑‑file </span> | File from which the imported data will be read. The file must have an extension of `.gfd` and must be on the file system of the member (or accessible to that member via NFS) that is being targeted for the import. Cannot be specified at the same time as ‑‑dir, cannot be used with ‑‑parallel. | |
+| <span class="keyword parmname">‑‑dir</span> | Directory from which the data is to be imported. Required if ‑‑parallel is true. Cannot be specified at the same time as ‑‑file. If a given node has no data file in the specified directory, the import operation is silently skipped for that node. | |
| <span class="keyword parmname">‑‑invoke‑callbacks</span> | Boolean value that, when true, invokes callbacks during the data import. | false |
**Example Commands:**
diff --git a/geode-docs/tools_modules/gfsh/command-pages/list.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/list.html.md.erb
index 3a7a92462d..86d33d69b7 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/list.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/list.html.md.erb
@@ -218,9 +218,9 @@ list durable-cqs --durable-client-id=value
| Name | Description |
|------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-durable-client-id </span> | *Required.* The ID used to identify the durable client. |
-| <span class="keyword parmname">\\-\\-members</span> | Name or Id of the member(s) for which the durable client is registered and durable CQs will be displayed. |
-| <span class="keyword parmname">\\-\\-groups</span> | Group(s) of members for which the durable client is registered and durable CQs will be displayed. |
+| <span class="keyword parmname">‑‑durable-client-id </span> | *Required.* The ID used to identify the durable client. |
+| <span class="keyword parmname">‑‑members</span> | Name or Id of the member(s) for which the durable client is registered and durable CQs will be displayed. |
+| <span class="keyword parmname">‑‑groups</span> | Group(s) of members for which the durable client is registered and durable CQs will be displayed. |
**Example Commands**:
@@ -271,8 +271,8 @@ list functions [--matches=value] [--groups=value(,value)*]
| Name | Description |
|--------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-matches </span> | Pattern that the function ID must match in order to be included. Uses Java pattern matching rules, not UNIX. For example, to match any character any number of times use ".\*" rather than "\*". |
-| <span class="keyword parmname">\\-\\-groups</span> | Group(s) of members for which functions will be displayed. Use a comma separated list for multiple groups. |
+| <span class="keyword parmname">‑‑matches </span> | Pattern that the function ID must match in order to be included. Uses Java pattern matching rules, not UNIX. For example, to match any character any number of times use ".\*" rather than "\*". |
+| <span class="keyword parmname">‑‑groups</span> | Group(s) of members for which functions will be displayed. Use a comma separated list for multiple groups. |
| <span class="keyword parmname">‑‑members </span> | Name or ID of the member(s) for which functions will be displayed. Use a comma separated list for multiple members. |
@@ -330,9 +330,9 @@ list gateways [--members=value(,value)*] [--groups=value(,value)*] [--senders-on
| Name | Description |
|------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|
| <span class="keyword parmname">‑‑members</span> | Member(s) whose gateways senders and receiver display. |
-| <span class="keyword parmname">\\-\\-groups</span> | Group(s) of members for which Gateway Senders and Receivers will be displayed. Use a comma separated list for multiple groups. |
-| \\-\\-senders\\-only | List only gateway senders. This parameter cannot be used together with `--receivers-only` |
-| \\-\\-receivers\\-only | List only gateway receivers. This parameter cannot be used together with `--senders-only`. |
+| <span class="keyword parmname">‑‑groups</span> | Group(s) of members for which Gateway Senders and Receivers will be displayed. Use a comma separated list for multiple groups. |
+| ‑‑senders‑only | List only gateway senders. This parameter cannot be used together with `--receivers-only` |
+| ‑‑receivers‑only | List only gateway receivers. This parameter cannot be used together with `--senders-only`. |
**Example Commands:**
@@ -385,7 +385,7 @@ list indexes [--with-stats(=value)?]
| Name | Description | Default Value |
|----------------------------------------------------|--------------------------------------------------------|---------------|
-| <span class="keyword parmname">\\-\\-with-stats</span> | Specifies whether statistics should also be displayed. | false |
+| <span class="keyword parmname">‑‑with-stats</span> | Specifies whether statistics should also be displayed. | false |
**Example Commands:**
@@ -477,7 +477,7 @@ list lucene indexes [--with-stats(=value)]
| Name | Description | Default Value |
|----------------------------------------------------|--------------------------------------------------------|---------------|
-| <span class="keyword parmname">\\-\\-with\\-stats</span> | Specifies whether statistics should also be displayed. | false if not specified, true if specified |
+| <span class="keyword parmname">‑‑with‑stats</span> | Specifies whether statistics should also be displayed. | false if not specified, true if specified |
**Example Commands:**
@@ -525,7 +525,7 @@ list members [--group=value]
| Name | Description |
|-----------------------------------------------|-------------------------------------------------|
-| <span class="keyword parmname">\\-\\-group</span> | Group name for which members will be displayed. |
+| <span class="keyword parmname">‑‑group</span> | Group name for which members will be displayed. |
**Example Commands:**
@@ -561,8 +561,8 @@ list regions [--groups=value(,value)*] [--members=value(,value)*]
| Name | Description |
|-------------------------------------------------|-----------------------------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-groups</span> | Group(s) of members for which regions will be displayed. |
-| <span class="keyword parmname">\\-\\-members </span> | Name or ID of the member(s) for which regions will be displayed. |
+| <span class="keyword parmname">‑‑groups</span> | Group(s) of members for which regions will be displayed. |
+| <span class="keyword parmname">‑‑members </span> | Name or ID of the member(s) for which regions will be displayed. |
**Example Commands:**
diff --git a/geode-docs/tools_modules/gfsh/command-pages/load-balance.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/load-balance.html.md.erb
index c27c0d7713..ffd7aabbb6 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/load-balance.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/load-balance.html.md.erb
@@ -38,7 +38,7 @@ load-balance gateway-sender --id=value
| Name | Description |
|--------------------------------------------|---------------------------------------|
-| <span class="keyword parmname">\\-\\-id</span> | *Required.* ID of the Gateway Sender. |
+| <span class="keyword parmname">‑‑id</span> | *Required.* ID of the Gateway Sender. |
<span class="tablecap">Table 1. Load-Balance Gateway-Sender Parameters</span>
diff --git a/geode-docs/tools_modules/gfsh/command-pages/locate.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/locate.html.md.erb
index 1dc6628fab..5f0db842be 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/locate.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/locate.html.md.erb
@@ -38,10 +38,10 @@ locate entry --key=value --region=value [--key-class=value]
| Name | Description | Default Value |
|-----------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|
-| <span class="keyword parmname">\\-\\-key</span> | *Required.* String or JSON text from which to create a key. Examples include: "`James`", "`100L`" and "`('id': 'l34s')`". | |
-| <span class="keyword parmname">\\-\\-region</span> | *Required.* Region in which to locate values. | |
-| <span class="keyword parmname">\\-\\-key-class</span> | Fully qualified class name of the key's type. | `java.lang.String` |
-| <span class="keyword parmname">\\-\\-value-class</span> | Fully qualified class name of the value's type. | `java.lang.String` |
+| <span class="keyword parmname">‑‑key</span> | *Required.* String or JSON text from which to create a key. Examples include: "`James`", "`100L`" and "`('id': 'l34s')`". | |
+| <span class="keyword parmname">‑‑region</span> | *Required.* Region in which to locate values. | |
+| <span class="keyword parmname">‑‑key-class</span> | Fully qualified class name of the key's type. | `java.lang.String` |
+| <span class="keyword parmname">‑‑value-class</span> | Fully qualified class name of the value's type. | `java.lang.String` |
| <span class="keyword parmname">‑‑recursive</span> | Whether to traverse regions and subregions recursively. | false |
<span class="tablecap">Table 1. Locate Entry Parameters</span>
diff --git a/geode-docs/tools_modules/gfsh/command-pages/netstat.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/netstat.html.md.erb
index 2c6097d2c4..3d2be6d425 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/netstat.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/netstat.html.md.erb
@@ -36,9 +36,9 @@ netstat [--members=value(,value)*] [--group=value] [--file=value]
| Name | Description | Default Value |
|---------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
-| <span class="keyword parmname">\\-\\-members </span> | Name or ID of the member(s) on which to run the `netstat` command. | |
-| <span class="keyword parmname">\\-\\-group</span> | Group of members on which to run the `netstat` command. | |
-| <span class="keyword parmname">\\-\\-file</span> | Text file to which output from the `netstat` command will be written. A "`.txt`" extension will be added if it is not already part of the specified name. | |
+| <span class="keyword parmname">‑‑members </span> | Name or ID of the member(s) on which to run the `netstat` command. | |
+| <span class="keyword parmname">‑‑group</span> | Group of members on which to run the `netstat` command. | |
+| <span class="keyword parmname">‑‑file</span> | Text file to which output from the `netstat` command will be written. A "`.txt`" extension will be added if it is not already part of the specified name. | |
| <span class="keyword parmname">‑‑with‑lsof</span> | Specifies whether `lsof` (list open files) command output should also be displayed. Not applicable for Microsoft Windows hosts. | false |
<span class="tablecap">Table 1. Netstat Parameters</span>
diff --git a/geode-docs/tools_modules/gfsh/command-pages/pause.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/pause.html.md.erb
index d368f78084..888f176eee 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/pause.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/pause.html.md.erb
@@ -36,9 +36,9 @@ pause gateway-sender --id=value [--groups=value(,value)*]
| Name | Description |
|------------------------------------------------|----------------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-id</span> | *Required.* ID of the gateway sender. |
-| <span class="keyword parmname">\\-\\-groups</span> | Group(s) of members on which to pause the gateway sender. |
-| <span class="keyword parmname">\\-\\-members</span> | Name or ID of the member(s) on which to pause the gateway sender. |
+| <span class="keyword parmname">‑‑id</span> | *Required.* ID of the gateway sender. |
+| <span class="keyword parmname">‑‑groups</span> | Group(s) of members on which to pause the gateway sender. |
+| <span class="keyword parmname">‑‑members</span> | Name or ID of the member(s) on which to pause the gateway sender. |
<span class="tablecap">Table 1. Pause Gateway-Sender Parameters</span>
diff --git a/geode-docs/tools_modules/gfsh/command-pages/pdx.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/pdx.html.md.erb
index 4a3e85e700..f38c37eeb8 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/pdx.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/pdx.html.md.erb
@@ -33,10 +33,10 @@ pdx rename --old=value --new=value --disk-store=value --disk-dirs=value(,value)*
| Name | Description |
|----------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-old</span> | *Required.* If a PDX type's fully qualified class name has a word that matches this text then it will be renamed. Words are delimited by '.' and '$'. |
-| <span class="keyword parmname">\\-\\-new</span> | *Required.* The text to replace the word that matched old. |
+| <span class="keyword parmname">‑‑old</span> | *Required.* If a PDX type's fully qualified class name has a word that matches this text then it will be renamed. Words are delimited by '.' and '$'. |
+| <span class="keyword parmname">‑‑new</span> | *Required.* The text to replace the word that matched old. |
| <span class="keyword parmname">‑‑disk‑store</span> | *Required.* Name of the disk store to operate on. |
-| <span class="keyword parmname">\\-\\-disk-dirs</span> | *Required.* Directories which contain the disk store files. |
+| <span class="keyword parmname">‑‑disk-dirs</span> | *Required.* Directories which contain the disk store files. |
**Example Commands:**
diff --git a/geode-docs/tools_modules/gfsh/command-pages/put.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/put.html.md.erb
index 890832011e..ddc8a76a39 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/put.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/put.html.md.erb
@@ -32,13 +32,13 @@ put --key=value --value=value --region=value [--key-class=value]
| Name | Description | Default Value |
|---------------------------------------------------|------------------------------------------------------------------------------------------------------------|--------------------|
-| <span class="ph">\\-\\-key</span> | *Required.* String or JSON text from which to create the key. For example: "`James`", "`100L`" and "`('id': 'l34s')`". | |
-| <span class="keyword parmname">\\-\\-value</span> | *Required.* String or JSON text from which to create the value. For example: "`James`", "`100L`" and "`('id': 'l34s')`". | |
+| <span class="ph">‑‑key</span> | *Required.* String or JSON text from which to create the key. For example: "`James`", "`100L`" and "`('id': 'l34s')`". | |
+| <span class="keyword parmname">‑‑value</span> | *Required.* String or JSON text from which to create the value. For example: "`James`", "`100L`" and "`('id': 'l34s')`". | |
| <span class="keyword parmname">‑‑region</span> | *Required.* Region into which the entry will be put. | |
| <span class="keyword parmname">‑‑key-class</span> | Fully qualified class name of the key's type. | `java.lang.String` |
-| <span class="keyword parmname">\\-\\-value-class</span> | Fully qualified class name of the value's type. The type may not be an internal PDX class. | `java.lang.String` |
| <span class="keyword parmname">‑‑value-class</span> | Fully qualified class name of the value's type. The type may not be an internal PDX class. | `java.lang.String` |
-| <span class="keyword parmname">\\-\\-if-not-exists</span> | Skip the put operation when an entry with the same key already exists. | false |
+| <span class="keyword parmname">‑‑value-class</span> | Fully qualified class name of the value's type. The type may not be an internal PDX class. | `java.lang.String` |
+| <span class="keyword parmname">‑‑if-not-exists</span> | Skip the put operation when an entry with the same key already exists. | false |
**Example Commands:**
@@ -48,7 +48,7 @@ put --key=('id':'133abg125') --value=('firstname':'James','lastname':'Gosling')
put --key=('133abg124') --value=('Hello World!!') --region=/region2
-put --key=('100F') --value=('2146547689879658564') --region=/region1/region12
+put --key=('100F') --value=('2146547689879658564') --region=/region1/region12
--key-class=java.lang.Float --value-class=java.lang.Long
```
diff --git a/geode-docs/tools_modules/gfsh/command-pages/rebalance.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/rebalance.html.md.erb
index 2394298329..93b757d8e7 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/rebalance.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/rebalance.html.md.erb
@@ -36,10 +36,10 @@ rebalance [--include-region=value(,value)*]
| Name | Description | Default Value |
|---------------------------------------------------------|----------------------------------------------------------------------------------------------------------|--------------------------------------|
-| <span class="keyword parmname">\\-\\-include-region</span> | Partitioned Region paths to be included for rebalance operation. Includes take precedence over excludes. | |
-| <span class="keyword parmname">\\-\\-exclude-region </span> | Partitioned Region paths to be excluded for rebalance operation. | |
-| <span class="keyword parmname">\\-\\-time-out</span> | Time to wait (in seconds) before GFSH returns to a prompt while rebalancing continues in the background. | -1 (wait for rebalancing to complete |
-| <span class="keyword parmname">\\-\\-simulate</span> | Whether to only simulate rebalancing. The --time-out parameter is not available when simulating. | false |
+| <span class="keyword parmname">‑‑include-region</span> | Partitioned Region paths to be included for rebalance operation. Includes take precedence over excludes. | |
+| <span class="keyword parmname">‑‑exclude-region </span> | Partitioned Region paths to be excluded for rebalance operation. | |
+| <span class="keyword parmname">‑‑time-out</span> | Time to wait (in seconds) before GFSH returns to a prompt while rebalancing continues in the background. | -1 (wait for rebalancing to complete |
+| <span class="keyword parmname">‑‑simulate</span> | Whether to only simulate rebalancing. The --time-out parameter is not available when simulating. | false |
<span class="tablecap">Table 1. Rebalance Parameters</span>
diff --git a/geode-docs/tools_modules/gfsh/command-pages/remove.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/remove.html.md.erb
index a1c4a01195..ced441326e 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/remove.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/remove.html.md.erb
@@ -33,10 +33,10 @@ remove --region=value [--key=value] [--all(=value)?] [--key-class=value]
| Name | Description | Default Value |
|----------------------------------------------------|-----------------------------------------------------------------------------|-------------------------------------------------|
-| <span class="keyword parmname">\\-\\-key</span> | String or JSON text that will be used to create a key to retrieve a value . | |
+| <span class="keyword parmname">‑‑key</span> | String or JSON text that will be used to create a key to retrieve a value . | |
| <span class="keyword parmname">‑‑key‑class </span> | Fully qualified class name of the key's type. | key constraint for the current region or String |
-| <span class="keyword parmname">\\-\\-region</span> | *Required.* Region from which to remove the entry. | |
-| <span class="keyword parmname">\\-\\-all</span> | A boolean value that, when true, clears the region by removing all entries. This option is not available for partitioned regions. | false |
+| <span class="keyword parmname">‑‑region</span> | *Required.* Region from which to remove the entry. | |
+| <span class="keyword parmname">‑‑all</span> | A boolean value that, when true, clears the region by removing all entries. This option is not available for partitioned regions. | false |
**Example Commands:**
diff --git a/geode-docs/tools_modules/gfsh/command-pages/resume.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/resume.html.md.erb
index 8f4d72e446..bd934a7a30 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/resume.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/resume.html.md.erb
@@ -49,9 +49,9 @@ resume async-event-queue-dispatcher --id=value [--groups=value(,value)*]
| Name | Description |
|------------------------------------------------|--------------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-id</span> | *Required.* ID of the Asynchronous Event Queue. |
-| <span class="keyword parmname">\\-\\-groups</span> | Group(s) of members on which to resume event dispatching for this queue. |
-| <span class="keyword parmname">\\-\\-members</span> | Name/Id of the member(s) on which to resume event dispatching for this queue. |
+| <span class="keyword parmname">‑‑id</span> | *Required.* ID of the Asynchronous Event Queue. |
+| <span class="keyword parmname">‑‑groups</span> | Group(s) of members on which to resume event dispatching for this queue. |
+| <span class="keyword parmname">‑‑members</span> | Name/Id of the member(s) on which to resume event dispatching for this queue. |
**Example Commands:**
@@ -76,9 +76,9 @@ resume gateway-sender --id=value [--groups=value(,value)*]
| Name | Description |
|------------------------------------------------|--------------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-id</span> | *Required.* ID of the Gateway Sender. |
-| <span class="keyword parmname">\\-\\-groups</span> | Group(s) of members on which to resume the Gateway Sender. |
-| <span class="keyword parmname">\\-\\-members</span> | Name/Id of the member(s) on which to resume the Gateway Sender. |
+| <span class="keyword parmname">‑‑id</span> | *Required.* ID of the Gateway Sender. |
+| <span class="keyword parmname">‑‑groups</span> | Group(s) of members on which to resume the Gateway Sender. |
+| <span class="keyword parmname">‑‑members</span> | Name/Id of the member(s) on which to resume the Gateway Sender. |
**Example Commands:**
diff --git a/geode-docs/tools_modules/gfsh/command-pages/revoke.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/revoke.html.md.erb
index 92bef822e2..f44637e8e3 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/revoke.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/revoke.html.md.erb
@@ -35,7 +35,7 @@ revoke missing-disk-store --id=value
| Name | Description |
|------|---------------------------------------------------------|
-| \\-\\-id | *Required.* ID of the missing disk store to be revoked. |
+| ‑‑id | *Required.* ID of the missing disk store to be revoked. |
<span class="tablecap">Table 1. Revoke Missing-Disk-Store Parameters</span>
diff --git a/geode-docs/tools_modules/gfsh/command-pages/run.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/run.html.md.erb
index 5d4453502b..656d2db2ea 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/run.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/run.html.md.erb
@@ -52,21 +52,20 @@ run --file=value [--quiet(=value)?] [--continue-on-error(=value)?]
</thead>
<tbody>
<tr>
-<td><span class="keyword parmname">\-\-file</span></td>
+<td><span class="keyword parmname">‑‑file</span></td>
<td><em>Required.</em> Path of the file scripted with commands that <code class="ph codeph">gfsh</code> recognizes. Path should be relative or absolute.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-quiet</span></td>
+<td><span class="keyword parmname">‑‑quiet</span></td>
<td>Specifies whether to show command output.
<div class="note note">
-**Note:**
-<p>All commands in a script are run non-interactively when the <code class="ph codeph">run</code> command is used. This option does not change that functionality.</p>
+<p><strong>Note:</strong> All commands in a script are run non-interactively when the <code class="ph codeph">run</code> command is used. This option does not change that functionality.</p>
</div></td>
<td>false</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-continue-on-error</span></td>
+<td><span class="keyword parmname">‑‑continue-on-error</span></td>
<td>Specifies whether further execution of the script should continue if there is an error while executing one of the commands fails.</td>
<td>false</td>
</tr>
diff --git a/geode-docs/tools_modules/gfsh/command-pages/search.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/search.html.md.erb
index f88d942206..f7e78bd100 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/search.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/search.html.md.erb
@@ -51,12 +51,12 @@ search lucene --name=value --region=value --queryString=value --defaultField=val
</thead>
<tbody>
<tr>
-<td><span class="keyword parmname">\-\-name</span></td>
+<td><span class="keyword parmname">‑‑name</span></td>
<td><em>Required</em>. Name of the Lucene index to search.</td>
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-region</span></td>
+<td><span class="keyword parmname">‑‑region</span></td>
<td><em>Required</em>. Name/Path of the region where the Lucene index exists.</td>
<td> </td>
</tr>
@@ -71,11 +71,11 @@ search lucene --name=value --region=value --queryString=value --defaultField=val
<td> </td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-limit</span></td>
+<td><span class="keyword parmname">‑‑limit</span></td>
<td>Number of search results needed.</td>
<td>If the parameter is not specified: -1</td>
</tr>
-<td><span class="keyword parmname">\-\-keys-only</span></td>
+<td><span class="keyword parmname">‑‑keys-only</span></td>
<td>Return only keys of search results.</td>
<td>If the parameter is not specified: false</td>
</tr>
diff --git a/geode-docs/tools_modules/gfsh/command-pages/sh.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/sh.html.md.erb
index ca3a4b8e48..ee36c43428 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/sh.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/sh.html.md.erb
@@ -21,7 +21,7 @@ limitations under the License.
Execute operating system commands.
-Executes operating system (OS) commands. Use '`&`' to return to the `gfsh` prompt immediately.
+Executes operating system (OS) commands. Use "`&`" to return to the `gfsh` prompt immediately.
**Note:**
Commands that pass output to another shell command are not supported.
@@ -38,7 +38,7 @@ sh command [--use-console(=value)?]
| Name | Description | Default Value |
|-----------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
-| <span class="keyword parmname">\\-\\-use-console</span> | Set this parameter on UNIX systems for applications which need a handle to the console. Adds "`</dev/tty >/dev/tty`" to the specified command. | false |
+| <span class="keyword parmname">‑‑use-console</span> | Set this parameter on UNIX systems for applications which need a handle to the console. Adds "`</dev/tty >/dev/tty`" to the specified command. | false |
<span class="tablecap">Table 1. Sh Parameters</span>
diff --git a/geode-docs/tools_modules/gfsh/command-pages/show.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/show.html.md.erb
index f9b1a40824..0e87a16bca 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/show.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/show.html.md.erb
@@ -59,7 +59,7 @@ show dead-locks --file=value
| Name | Description |
|----------------------------------------------|-------------------------------------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-file</span> | *Required.* Name of the file to which dependencies between members will be written. |
+| <span class="keyword parmname">‑‑file</span> | *Required.* Name of the file to which dependencies between members will be written. |
<span class="tablecap">Table 1. Show Dead-Locks Parameters</span>
@@ -94,8 +94,8 @@ show log --member=value [--lines=value]
| Name | Description | Default Value |
|------------------------------------------------------------|--------------------------------------------|---------------------------------|
-| <span class="keyword parmname">\\-\\-member</span> | *Required.* Name/ID of the member whose log file will be displayed. | |
-| <span class="keyword parmname">\\-\\-lines </span> | Number of lines from the log file to display. The maximum is 100. | 0 |
+| <span class="keyword parmname">‑‑member</span> | *Required.* Name/ID of the member whose log file will be displayed. | |
+| <span class="keyword parmname">‑‑lines </span> | Number of lines from the log file to display. The maximum is 100. | 0 |
**Example Commands:**
@@ -152,23 +152,23 @@ show metrics [--member=value] [--region=value] [--file=value]
</thead>
<tbody>
<tr>
-<td><span class="keyword parmname">\-\-member</span></td>
+<td><span class="keyword parmname">‑‑member</span></td>
<td>Name/ID of the member whose metrics will be displayed/exported.</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-region</span></td>
+<td><span class="keyword parmname">‑‑region</span></td>
<td>Name/Path of the region whose metrics will be displayed/exported.</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-file</span></td>
+<td><span class="keyword parmname">‑‑file</span></td>
<td>Name of the file to which metrics will be written.</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-port</span></td>
+<td><span class="keyword parmname">‑‑port</span></td>
<td>Port number of the Cache Server whose metrics are to be displayed/exported. This can only be used along with the <code class="ph codeph">--member</code> parameter.</td>
</tr>
<tr>
-<td><span class="keyword parmname">\-\-categories</span></td>
+<td><span class="keyword parmname">‑‑categories</span></td>
<td>Categories available based upon the parameters specified (listed above) are:
<ul>
<li><strong>region specified</strong>: cluster, region, partition, diskstore, callback, eviction</li>
@@ -269,10 +269,10 @@ show subscription-queue-size --durable-client-Id=value
| Name | Description |
|------------------------------------------------------------|------------------------------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-durable-client-id </span> | *Required.* The ID used to identify the durable client. |
-| <span class="keyword parmname">\\-\\-durable-cq-name </span> | The name that identifies the CQ. |
-| <span class="keyword parmname">\\-\\-members </span> | Name/Id of the member(s) for which subscription queue events are to be counted. |
-| <span class="keyword parmname">\\-\\-groups</span> | Group(s) of members for which subscription queue events are to be counted. |
+| <span class="keyword parmname">‑‑durable-client-id </span> | *Required.* The ID used to identify the durable client. |
+| <span class="keyword parmname">‑‑durable-cq-name </span> | The name that identifies the CQ. |
+| <span class="keyword parmname">‑‑members </span> | Name/Id of the member(s) for which subscription queue events are to be counted. |
+| <span class="keyword parmname">‑‑groups</span> | Group(s) of members for which subscription queue events are to be counted. |
<span class="tablecap">Table 4. Show Subscription-Queue-Size Parameters</span>
diff --git a/geode-docs/tools_modules/gfsh/command-pages/shutdown.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/shutdown.html.md.erb
index 84f5f19978..a11daeffa7 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/shutdown.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/shutdown.html.md.erb
@@ -35,8 +35,8 @@ shutdown [--time-out=value] [--include-locators=value]
| Name | Description | Default Value |
|----------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|---------------|
-| <span class="keyword parmname">\\-\\-time-out </span> | Time to wait (in seconds) for a graceful shutdown. Should be at least 10 seconds. The default value if not specified is 10. | 10 |
-| <span class="keyword parmname">\\-\\-include-locators</span> | To shutdown locators, specify this option as true. | false |
+| <span class="keyword parmname">‑‑time-out </span> | Time to wait (in seconds) for a graceful shutdown. Should be at least 10 seconds. The default value if not specified is 10. | 10 |
+| <span class="keyword parmname">‑‑include-locators</span> | To shutdown locators, specify this option as true. | false |
<span class="tablecap">Table 1. Shutdown Parameters</span>
diff --git a/geode-docs/tools_modules/gfsh/command-pages/sleep.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/sleep.html.md.erb
index 6a0754c0fd..0af2559bc8 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/sleep.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/sleep.html.md.erb
@@ -35,7 +35,7 @@ sleep [--time=value]
| Name | Description | Default Value |
|-----------------------------------------------|-----------------------------|---------------|
-| <span class="keyword parmname">\\-\\-time </span> | Number of seconds to sleep. | 3 |
+| <span class="keyword parmname">‑‑time </span> | Number of seconds to sleep. | 3 |
<span class="tablecap">Table 1. Sleep Parameters</span>
diff --git a/geode-docs/tools_modules/gfsh/command-pages/start.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/start.html.md.erb
index 525fe950b8..7db0c622c9 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/start.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/start.html.md.erb
@@ -66,8 +66,8 @@ start gateway-receiver [--groups=value(,value)*] [--members=value(,value)*]
| Name | Description |
|---------------|---------------------------------------------------------------------|
-| \\-\\-members | Name or ID of the member(s) on which to start the Gateway Receiver. |
-| \\-\\-groups | Group(s) of members on which to start the Gateway Receiver. |
+| ‑‑members | Name or ID of the member(s) on which to start the Gateway Receiver. |
+| ‑‑groups | Group(s) of members on which to start the Gateway Receiver. |
**Example Commands:**
@@ -118,10 +118,10 @@ start gateway-sender --id=value [--groups=value(,value)*] [--members=value(,valu
| Name | Description | Default Value |
|--------------|----------------|---------------|
-| \\-\\-id | *Required.* ID of the GatewaySender. | |
-| \\-\\-groups | Group(s) of members on which to start the Gateway Sender. | |
+| ‑‑id | *Required.* ID of the GatewaySender. | |
+| ‑‑groups | Group(s) of members on which to start the Gateway Sender. | |
| ‑‑members | Member(s) on which to start the Gateway Sender. | |
-| \\-\\-clean-queues | Option to clean existing queue at start of the Gateway Sender. This option is only applicable for Gateway Senders with enabled persistence. | false |
+| ‑‑clean-queues | Option to clean existing queue at start of the Gateway Sender. This option is only applicable for Gateway Senders with enabled persistence. | false |
**Example Commands:**
@@ -176,11 +176,11 @@ start jconsole [--interval=<seconds>] [--notile] [--version]
| Name | Description | Default Value |
|------------------|----------------|---------------|
-| \\-\\-interval | Set the update interval to n seconds (default is 4 seconds). (Equivalent to JConsole's `-interval=n`) | 4 |
-| \\-\\-notile | Whether to initially tile windows for two or more connections. This parameter is passed as `-notile` to JConsole. | false |
+| ‑‑interval | Set the update interval to n seconds (default is 4 seconds). (Equivalent to JConsole's `-interval=n`) | 4 |
+| ‑‑notile | Whether to initially tile windows for two or more connections. This parameter is passed as `-notile` to JConsole. | false |
| ‑‑pluginpath | Directories or JAR files which are searched for JConsole plugins. The path should contain a provider-configuration file named:`META-INF/services/com.sun.tools.jconsole.JConsolePlugin` containing one line for each plugin specifying the fully qualified class name of the class implementing the `com.sun.tools.jconsole.JConsolePlugin` class. | |
-| \\-\\-version | Display the JConsole version information. This parameter is passed as `-version` to JConsole. | false |
-| \\-\\-J | Arguments passed to the JVM on which JConsole runs | |
+| ‑‑version | Display the JConsole version information. This parameter is passed as `-version` to JConsole. | false |
+| ‑‑J | Arguments passed to the JVM on which JConsole runs | |
**Example Commands:**
@@ -237,7 +237,7 @@ start jvisualvm [--J=value(,value)*]
| Name | Description |
|------------|-------------|
-| \\-\\-J | VM-option passed to the spawned CacheServer VM.<br/>For example: `--J=-Dfoo.bar=true` for setting foo.bar to 'true'. |
+| ‑‑J | VM-option passed to the spawned CacheServer VM.<br/>For example: `--J=-Dfoo.bar=true` for setting foo.bar to 'true'. |
**Example Commands:**
@@ -272,7 +272,7 @@ start locator --name=value [--bind-address=value] [--force(=value)]
[--properties-file=value] [--security-properties-file=value] [--initial-heap=value] [--max-heap=value]
[--connect(=value)] [--enable-cluster-configuration(=value)] [--load-cluster-configuration-from-dir(=value)]
[--cluster-config-dir=value] [--redirect-output(=value)]
- [--http-service-port=value] [--http-service-bind-address=value]
+ [--http-service-port=value] [--http-service-bind-address=value]
[--J=value(,value)*]
```
@@ -280,30 +280,30 @@ start locator --name=value [--bind-address=value] [--force(=value)]
| Name | Description | Default Value |
|--------------|----------------|---------------|
-| \\-\\-name | Name to be used for this <%=vars.product_name%> locator service. If not specified, gfsh generates a random name. | |
-| \\-\\-bind-address | IP address on which the locator will be bound. | bind to all addresses |
-| \\-\\-force | Whether to allow the PID file from a previous locator run to be overwritten. | false |
-| \\-\\-groups | Group(s) the locator will be a part of. | |
-| \\-\\-hostname-for-clients | Host name or IP address that will be sent to clients so they can connect to this locator. | uses `bind-address` |
-| \\-\\-classpath | Application classes to be added to the locator's CLASSPATH after the core jar file. See <a href="../../../getting_started/setup_classpath.html">Setting Up the CLASSPATH</a> for details. | |
-| \\-\\-locators | List of locators used by this locator to join the appropriate <%=vars.product_name%> cluster. | |
-| \\-\\-log-level | Level of output logged to the locator log file. Possible values for log-level include: ALL, TRACE, DEBUG, INFO, WARN, ERROR, FATAL, OFF. | |
-| \\-\\-mcast-address | IP address or hostname used to bind the UPD socket for multi-cast networking so the locator can locate other members in the <%=vars.product_name%> cluster. If mcast-port is zero, then mcast-address is ignored. | |
-| \\-\\-mcast-port | Port used for multi-cast networking so the locator can locate other members of the <%=vars.product_name%> cluster. A zero value disables mcast. | |
-| \\-\\-port | Port the locator will listen on. | 10334 |
-| \\-\\-dir | Directory in which the Locator will be started and run. | `./<locator-member-name>` |
-| \\-\\-properties-file | Specify the `gemfire.properties` file for configuring the locator's cluster. The file's path should be absolute or relative to gfsh's working directory. | |
-| \\-\\-security-properties-file | The `gfsecurity.properties` file for configuring the Locator's security configuration in the cluster. The file's path can be absolute or relative to gfsh's working directory. | |
-| \\-\\-initial-heap | Size has the same format as the `-Xmx`/`-Xms` JVM options. <p><b>Note:</b> If you use the `-J-Xms` and `-J-Xmx` JVM properties instead of `-initial-heap` and `-max-heap`, then <%=vars.product_name%> does not use default JVM resource management properties. If you use the JVM properties, you must then specify all properties manually for eviction, garbage collection, heap percentage, and so forth.</p> | |
-| \\-\\-max-heap | Size has the same format as the `-Xmx`/`-Xms` JVM options. <p><b>Note:</b> If you use the `-J-Xms` and `-J-Xmx` JVM properties instead of `-initial-heap` and `-max-heap`, then <%=vars.product_name%> does not use default JVM resource management properties. If you use the JVM properties, you must then specify all properties manually for eviction, garbage collection, heap percentage, and so forth.</p><p><b>Note:</b> The additional GC parameters [...]
-| \\-\\-connect | When connect is set to false, gfsh does not automatically connect to the locator which is started using this command. | true |
-| \\-\\-enable-cluster-configuration | Enables cluster configuration behavior where locators maintain configurations for all members of the cluster.<br/>See <a href="../../../configuring/cluster_config/gfsh_persist.html">Overview of the Cluster Configuration Service</a>. | true |
-| \\-\\-load-cluster-configuration-from-dir | <b>Deprecated. Use `gfsh import cluster-configuration` for this functionality.</b><br/> Loads the cluster configuration from the `shared-config` directory. (When set to false, the configuration is loaded from the disk store of the internal, persistent region used by the locator to persist the configuration.) | false |
-| \\-\\-cluster-config-dir | Directory used by the cluster configuration service to store the cluster configuration on the filesystem | cluster-config |
-| \\-\\-redirect-output | When true, redirect standard output and standard error to the locator log file. If specified without a value, the value is set to true. | false |
-| \\-\\-http-service-port | Specifies the HTTP service port. | 7070 |
-| \\-\\-http-service-bind-address | Specifies the IP address to which the HTTP service will be bound. | the local host machine's address |
-| \\-\\-J | Argument passed to the JVM on which the Locator will run. For example, specifying `--J=-Dfoo.bar=true` sets property "foo.bar" to "true".<p><b>Note:</b> If the argument you are passing contains spaces or commas, enclose the option in single quotes. For example:<br/>`start locator --name=locator1 --port=9009 --mcast-port=0 --J='-Dgemfire.remote-locators=192.0.2.0[9009],192.0.2.1[9009]'`</p> | none |
+| ‑‑name | Name to be used for this <%=vars.product_name%> locator service. If not specified, gfsh generates a random name. | |
+| ‑‑bind-address | IP address on which the locator will be bound. | bind to all addresses |
+| ‑‑force | Whether to allow the PID file from a previous locator run to be overwritten. | false |
+| ‑‑groups | Group(s) the locator will be a part of. | |
+| ‑‑hostname-for-clients | Host name or IP address that will be sent to clients so they can connect to this locator. | uses `bind-address` |
+| ‑‑classpath | Application classes to be added to the locator's CLASSPATH after the core jar file. See <a href="../../../getting_started/setup_classpath.html">Setting Up the CLASSPATH</a> for details. | |
+| ‑‑locators | List of locators used by this locator to join the appropriate <%=vars.product_name%> cluster. | |
+| ‑‑log-level | Level of output logged to the locator log file. Possible values for log-level include: <code>ALL</code>, <code>TRACE</code>, <code>DEBUG</code>, <code>INFO</code>, <code>WARN</code>, <code>ERROR</code>, <code>FATAL</code>, <code>OFF</code>. | |
+| ‑‑mcast-address | IP address or hostname used to bind the UPD socket for multi-cast networking so the locator can locate other members in the <%=vars.product_name%> cluster. If mcast-port is zero, then mcast-address is ignored. | |
+| ‑‑mcast-port | Port used for multi-cast networking so the locator can locate other members of the <%=vars.product_name%> cluster. A zero value disables mcast. | |
+| ‑‑port | Port the locator will listen on. | 10334 |
+| ‑‑dir | Directory in which the Locator will be started and run. | `./<locator-member-name>` |
+| ‑‑properties-file | Specify the `gemfire.properties` file for configuring the locator's cluster. The file's path should be absolute or relative to gfsh's working directory. | |
+| ‑‑security-properties-file | The `gfsecurity.properties` file for configuring the Locator's security configuration in the cluster. The file's path can be absolute or relative to gfsh's working directory. | |
+| ‑‑initial-heap | Size has the same format as the `-Xmx`/`-Xms` JVM options. <p><b>Note:</b> If you use the `-J-Xms` and `-J-Xmx` JVM properties instead of `-initial-heap` and `-max-heap`, then <%=vars.product_name%> does not use default JVM resource management properties. If you use the JVM properties, you must then specify all properties manually for eviction, garbage collection, heap percentage, and so forth.</p> | |
+| ‑‑max-heap | Size has the same format as the `-Xmx`/`-Xms` JVM options. <p><b>Note:</b> If you use the `-J-Xms` and `-J-Xmx` JVM properties instead of `-initial-heap` and `-max-heap`, then <%=vars.product_name%> does not use default JVM resource management properties. If you use the JVM properties, you must then specify all properties manually for eviction, garbage collection, heap percentage, and so forth.</p><p><b>Note:</b> The additional GC par [...]
+| ‑‑connect | When connect is set to false, gfsh does not automatically connect to the locator which is started using this command. | true |
+| ‑‑enable-cluster-configuration | Enables cluster configuration behavior where locators maintain configurations for all members of the cluster.<br/>See <a href="../../../configuring/cluster_config/gfsh_persist.html">Overview of the Cluster Configuration Service</a>. | true |
+| ‑‑load-cluster-configuration-from-dir | <b>Deprecated. Use `gfsh import cluster-configuration` for this functionality.</b><br/> Loads the cluster configuration from the `shared-config` directory. (When set to false, the configuration is loaded from the disk store of the internal, persistent region used by the locator to persist the configuration.) | false |
+| ‑‑cluster-config-dir | Directory used by the cluster configuration service to store the cluster configuration on the filesystem | cluster-config |
+| ‑‑redirect-output | When true, redirect standard output and standard error to the locator log file. If specified without a value, the value is set to true. | false |
+| ‑‑http-service-port | Specifies the HTTP service port. | 7070 |
+| ‑‑http-service-bind-address | Specifies the IP address to which the HTTP service will be bound. | the local host machine's address |
+| ‑‑J | Argument passed to the JVM on which the Locator will run. For example, specifying `--J=-Dfoo.bar=true` sets property "foo.bar" to "true".<p><b>Note:</b> If the argument you are passing contains spaces or commas, enclose the option in single quotes. For example:<br/>`start locator --name=locator1 --port=9009 --mcast-port=0 --J='-Dgemfire.remote-locators=192.0.2.0[9009],192.0.2.1[9009]'`</p> | none |
**Example Commands:**
@@ -330,7 +330,7 @@ start pulse [--url=value]
| Name | Description | Default Value |
|--------------|----------------|---------------|
-| \\-\\-url | URL of the Pulse Web application | `http://localhost:7070/pulse` |
+| ‑‑url | URL of the Pulse Web application | `http://localhost:7070/pulse` |
**Example Commands:**
@@ -384,54 +384,54 @@ start server --name=value [--assign-buckets(=value)] [--bind-address=value]
| Name | Description | Default Value |
|--------------|----------------|---------------|
-| \\-\\-name | Member name for this server. If not specified, gfsh generates a random name. | |
-| \\-\\-assign-buckets | Whether to assign buckets to the partitioned regions of the cache on server start. | false |
-| \\-\\-bind-address | The IP address on which the server will be bound. | binds to all local addresses |
-| \\-\\-cache-xml-file | Specifies the name of the XML file or resource to initialize the cache with when it is created. | |
-| \\-\\-classpath | Application classes to be added to the server's CLASSPATH after the core jar file.<br/>See <a href="../../../getting_started/setup_classpath.html">Setting Up the CLASSPATH</a> for details. | |
-| \\-\\-include-system-classpath | When true, include the System CLASSPATH on the Server's CLASSPATH, as the System CLASSPATH is not included by default. If specified without a value, the value is set to true. | false |
-| \\-\\-disable-default-server | Whether the cache server will be started by default. If the parameter is specified without a value, the value is set to true. If set to true, the cache server acts as a peer. | false |
-| \\-\\-disable-exit-when-out-of-memory | Prevents the JVM from exiting when an OutOfMemoryError occurs. | false |
-| \\-\\-enable-time-statistics | Causes additional time-based statistics to be gathered for <%=vars.product_name%> operations. | true |
-| \\-\\-properties-file | The `gemfire.properties` file for configuring the server's cluster. The file's path can be absolute or relative to the gfsh working directory. | |
-| \\-\\-security-properties-file | The `gfsecurity.properties` file for configuring the server's security configuration in the cluster. The file's path can be absolute or relative to gfsh directory. | |
-| \\-\\-groups | Group(s) the Cache Server will be a part of. | |
-| \\-\\-force | Whether to allow the PID file from a previous Cache Server run to be overwritten. | false |
-| \\-\\-locators | Sets the list of locators used by the Cache Server to join the appropriate <%=vars.product_name%> cluster. | |
-| \\-\\-locator-wait-time | Sets the number of seconds the server will wait for a locator to become available during startup before giving up. | 0 |
-| \\-\\-log-level | Sets the level of output logged to the Cache Server log file. Possible values for log-level include: ALL, TRACE, DEBUG, INFO, WARN, ERROR, FATAL, OFF. | |
-| \\-\\-mcast-address | The IP address or hostname used to bind the UDP socket for multi-cast networking so the Cache Server can locate other members in the <%=vars.product_name%> cluster. If mcast-port is zero, then mcast-address is ignored. | |
-| \\-\\-mcast-port | Sets the port used for multi-cast networking so the Cache Server can locate other members of the <%=vars.product_name%> cluster. A zero value disables mcast. | |
+| ‑‑name | Member name for this server. If not specified, gfsh generates a random name. | |
+| ‑‑assign-buckets | Whether to assign buckets to the partitioned regions of the cache on server start. | false |
+| ‑‑bind-address | The IP address on which the server will be bound. | binds to all local addresses |
+| ‑‑cache-xml-file | Specifies the name of the XML file or resource to initialize the cache with when it is created. | |
+| ‑‑classpath | Application classes to be added to the server's CLASSPATH after the core jar file.<br/>See <a href="../../../getting_started/setup_classpath.html">Setting Up the CLASSPATH</a> for details. | |
+| ‑‑include-system-classpath | When true, include the System CLASSPATH on the Server's CLASSPATH, as the System CLASSPATH is not included by default. If specified without a value, the value is set to true. | false |
+| ‑‑disable-default-server | Whether the cache server will be started by default. If the parameter is specified without a value, the value is set to true. If set to true, the cache server acts as a peer. | false |
+| ‑‑disable-exit-when-out-of-memory | Prevents the JVM from exiting when an OutOfMemoryError occurs. | false |
+| ‑‑enable-time-statistics | Causes additional time-based statistics to be gathered for <%=vars.product_name%> operations. | true |
+| ‑‑properties-file | The `gemfire.properties` file for configuring the server's cluster. The file's path can be absolute or relative to the gfsh working directory. | |
+| ‑‑security-properties-file | The `gfsecurity.properties` file for configuring the server's security configuration in the cluster. The file's path can be absolute or relative to gfsh directory. | |
+| ‑‑groups | Group(s) the Cache Server will be a part of. | |
+| ‑‑force | Whether to allow the PID file from a previous Cache Server run to be overwritten. | false |
+| ‑‑locators | Sets the list of locators used by the Cache Server to join the appropriate <%=vars.product_name%> cluster. | |
+| ‑‑locator-wait-time | Sets the number of seconds the server will wait for a locator to become available during startup before giving up. | 0 |
+| ‑‑log-level | Sets the level of output logged to the Cache Server log file. Possible values for log-level include: <code>ALL</code>, <code>TRACE</code>, <code>DEBUG</code>, <code>INFO</code>, <code>WARN</code>, <code>ERROR</code>, <code>FATAL</code>, <code>OFF</code>. | |
+| ‑‑mcast-address | The IP address or hostname used to bind the UDP socket for multi-cast networking so the Cache Server can locate other members in the <%=vars.product_name%> cluster. If mcast-port is zero, then mcast-address is ignored. | |
+| ‑‑mcast-port | Sets the port used for multi-cast networking so the Cache Server can locate other members of the <%=vars.product_name%> cluster. A zero value disables mcast. | |
| ‑‑memcached-port | If specified and is non-zero, sets the port number for an embedded Gemcached server and starts the Gemcached server. | |
| ‑‑memcached-protocol | Sets the protocol used by an embedded Gemcached server. Valid values are `BINARY` and `ASCII`. If you omit this property, the ASCII protocol is used. | |
-| \\-\\-server-bind-address | Overrides the `bind-address` on which this server will listen for client connections. Set this option in a multi-homed server environment to distinguish communications from clients. Setting a value of the empty string ("") uses the value of `bind-address`. | value of `bind-address` |
-| \\-\\-server-port | Port the Server will listen on for client connections. | 40404 |
-| \\-\\-spring-xml-location | Specifies the location of a Spring XML configuration file(s) for bootstrapping and configuring a <%=vars.product_name%> Server. This configuration file can exist on the CLASSPATH (default) or any location supported by Spring's Resource(Loader) location specifiers (for example, classpath:, file:, etc).<br/>ResourceLoader is described in the <a href="http://docs.spring.io/spring/docs/4.0.9.RELEASE/spring-framework-reference/htmlsingle/#resources-re [...]
-| \\-\\-rebalance | Whether to initiate rebalancing across the <%=vars.product_name%> cluster. | false |
-| \\-\\-dir | Specify the directory in which the server will run in. This directory is written to the location where you started `gfsh`.| If not specified, the directory is named after the server. |
-| \\-\\-statistic-archive-file | The file that statistic samples are written to. For example: "StatisticsArchiveFile.gfs". Must be defined to store the archiving to a file. An empty string (default) disables statistic archival. | not set |
-| \\-\\-initial-heap | Initial size of the heap in the same format as the JVM -Xms parameter.<p><b>Note:</b> If you use the `--J=-Xms` and `--J=-Xmx` JVM properties instead of `--initial-heap` and `--max-heap`, then <%=vars.product_name%> does not use default JVM resource management properties. If you use the JVM properties, you must then specify all properties manually for eviction, garbage collection, heap percentage, and so forth.</p> | |
-| \\-\\-max-heap | Maximum size of the heap in the same format as the JVM -Xmx parameter.<p><b>Note:</b> If you use the `--J=-Xms` and `--J=-Xmx` JVM properties instead of `--initial-heap` and `--max-heap`, then <%=vars.product_name%> does not use default JVM resource management properties. If you use the JVM properties, you must then specify all properties manually for eviction, garbage collection, heap percentage, and so forth.</p><p><b>Note:</b> The additional G [...]
-| \\-\\-J | Argument passed to the JVM on which the Cache Server will run. For example, `--J=-Dfoo.bar=true` will set the property "foo.bar" to "true".<p>If the argument you are passing contains spaces or commas, enclose the option in single quotes.</p> | |
-| \\-\\-use-cluster-configuration | Specifies whether the server requests a cluster configuration from the locator.<p>See <a href="../../../configuring/cluster_config/gfsh_persist.html">Overview of the Cluster Configuration Service</a>.</p>| true |
-| \\-\\-critical-heap-percentage | Set the percentage of heap at or above which the cache is considered in danger of becoming inoperable due to garbage collection pauses or out of memory exceptions. Past the threshold, operations that require heap space will throw a `LowMemoryException`. This feature requires additional VM flags to perform properly; you must set `--initial-heap` and `--max-heap` or the corresponding JVM properties to use this threshold. You must also set `--max-he [...]
-| \\-\\-critical-off-heap-percentage | The percentage of off-heap memory used at or above which the cache is considered in danger of becoming inoperable due to out of memory exceptions. Past the threshold, operations that require heap space will throw a `LowMemoryException`.|0 (no critical off-heap threshold enforced)|
-| \\-\\-eviction-heap-percentage | Set the percentage of heap at or above which the eviction should begin on Regions configured for HeapLRU eviction. Changing this value may cause eviction to begin immediately. Only one change to this attribute or critical heap percentage will be allowed at any given time and its effect will be fully realized before the next change is allowed. This feature requires additional VM flags to perform properly; you must set `--initial-heap` and `--max-h [...]
-| \\-\\-eviction-off-heap-percentage | The percentage of off-heap memory used at or above which the eviction should begin on regions configured for off-heap and HeapLRU eviction. Changing this value may cause eviction to begin immediately. Only one change to this attribute or critical off-heap percentage will be allowed at any given time, and its effect will be fully realized before the next change is allowed.|<ul><li>0, if no region is configured with heap eviction</li><li>If `critic [...]
-| \\-\\-hostname-for-clients | Sets the IP address or host name that a locator will provide to clients. Clients use the address to connect to a server. Set this value when clients use a different address to connect with the server than the `bind-address`, as those clients might with servers in a private cloud or multi-homed environment. Not specifying this option or setting this option to the empty string ("") causes the `bind-address` to be given to clients.| |
-| \\-\\-max-connections | Sets the maximum number of client connections allowed. When the maximum is reached the cache server will stop accepting connections. | |
-| \\-\\-message-time-to-live | Sets the time (in seconds ) after which a message in the client queue will expire. | |
-| \\-\\-max-message-count | Sets maximum number of messages that can be enqueued in a client-queue.| |
-| \\-\\-max-threads | Sets the maximum number of threads allowed in this cache server to service client requests. The default of 0 causes the cache server to dedicate a thread for every client connection. When client-server TLS/SSL is configured, values other than the default are not supported. | |
-| \\-\\-socket-buffer-size | Sets the buffer size in bytes of the socket connection for this CacheServer. The default is 32768 bytes.| |
-| \\-\\-lock-memory | (Linux only) When true, the member's heap and off-heap memory are locked in RAM, preventing them from being paged to disk. You must increase the related `ulimit` operating system resource to allow the OS to lock memory chunks of sufficient size.| false |
-| \\-\\-off-heap-memory-size | The integer quantity of off-heap memory to be used for storing region values. Specified in Gigabytes with a 'g' suffix, or Megabytes with an 'm' suffix. For example, allocate a 2 Gigabyte off-heap space with `--off-heap-memory-size=2g`. The default value of 0 does not use any off-heap memory.| 0 |
-| \\-\\-start-rest-api | When true, starts the REST API service. | false |
-| \\-\\-redirect-output | When true, redirect standard output and standard error to the server log file. If specified without a value, the value is set to true. | false |
-| \\-\\-http-service-port | Specifies the HTTP service port. | 7070 |
-| \\-\\-http-service-bind-address | Specifies the IP address to which the HTTP service will be bound. | the local host machine's address |
-| \\-\\-user | The user name of the credential to use in authenticating to the cluster. When specified, if the `--password` option is not also specified, then `gfsh` will prompt for the password.| |
-| \\-\\-password | The password portion of the credential to use in authenticating to the cluster. | |
+| ‑‑server-bind-address | Overrides the `bind-address` on which this server will listen for client connections. Set this option in a multi-homed server environment to distinguish communications from clients. Setting a value of the empty string ("") uses the value of `bind-address`. | value of `bind-address` |
+| ‑‑server-port | Port the Server will listen on for client connections. | 40404 |
+| ‑‑spring-xml-location | Specifies the location of a Spring XML configuration file(s) for bootstrapping and configuring a <%=vars.product_name%> Server. This configuration file can exist on the CLASSPATH (default) or any location supported by Spring's Resource(Loader) location specifiers (for example, classpath:, file:, etc).<br/>ResourceLoader is described in the <a href="http://docs.spring.io/spring/docs/4.0.9.RELEASE/spring-framework-reference/htmlsingle/#reso [...]
+| ‑‑rebalance | Whether to initiate rebalancing across the <%=vars.product_name%> cluster. | false |
+| ‑‑dir | Specify the directory in which the server will run in. This directory is written to the location where you started `gfsh`.| If not specified, the directory is named after the server. |
+| ‑‑statistic-archive-file | The file that statistic samples are written to. For example: "StatisticsArchiveFile.gfs". Must be defined to store the archiving to a file. An empty string (default) disables statistic archival. | not set |
+| ‑‑initial-heap | Initial size of the heap in the same format as the JVM -Xms parameter.<p><b>Note:</b> If you use the `--J=-Xms` and `--J=-Xmx` JVM properties instead of `--initial-heap` and `--max-heap`, then <%=vars.product_name%> does not use default JVM resource management properties. If you use the JVM properties, you must then specify all properties manually for eviction, garbage collection, heap percentage, and so forth.</p> | |
+| ‑‑max-heap | Maximum size of the heap in the same format as the JVM -Xmx parameter.<p><b>Note:</b> If you use the `--J=-Xms` and `--J=-Xmx` JVM properties instead of `--initial-heap` and `--max-heap`, then <%=vars.product_name%> does not use default JVM resource management properties. If you use the JVM properties, you must then specify all properties manually for eviction, garbage collection, heap percentage, and so forth.</p><p><b>Note:</b> The addi [...]
+| ‑‑J | Argument passed to the JVM on which the Cache Server will run. For example, `--J=-Dfoo.bar=true` will set the property "foo.bar" to "true".<p>If the argument you are passing contains spaces or commas, enclose the option in single quotes.</p> | |
+| ‑‑use-cluster-configuration | Specifies whether the server requests a cluster configuration from the locator.<p>See <a href="../../../configuring/cluster_config/gfsh_persist.html">Overview of the Cluster Configuration Service</a>.</p>| true |
+| ‑‑critical-heap-percentage | Set the percentage of heap at or above which the cache is considered in danger of becoming inoperable due to garbage collection pauses or out of memory exceptions. Past the threshold, operations that require heap space will throw a `LowMemoryException`. This feature requires additional VM flags to perform properly; you must set `--initial-heap` and `--max-heap` or the corresponding JVM properties to use this threshold. You must also set ` [...]
+| ‑‑critical-off-heap-percentage | The percentage of off-heap memory used at or above which the cache is considered in danger of becoming inoperable due to out of memory exceptions. Past the threshold, operations that require heap space will throw a `LowMemoryException`.|0 (no critical off-heap threshold enforced)|
+| ‑‑eviction-heap-percentage | Set the percentage of heap at or above which the eviction should begin on Regions configured for HeapLRU eviction. Changing this value may cause eviction to begin immediately. Only one change to this attribute or critical heap percentage will be allowed at any given time and its effect will be fully realized before the next change is allowed. This feature requires additional VM flags to perform properly; you must set `--initial-heap` and [...]
+| ‑‑eviction-off-heap-percentage | The percentage of off-heap memory used at or above which the eviction should begin on regions configured for off-heap and HeapLRU eviction. Changing this value may cause eviction to begin immediately. Only one change to this attribute or critical off-heap percentage will be allowed at any given time, and its effect will be fully realized before the next change is allowed.|<ul><li>0, if no region is configured with heap eviction</li><li>If [...]
+| ‑‑hostname-for-clients | Sets the IP address or host name that a locator will provide to clients. Clients use the address to connect to a server. Set this value when clients use a different address to connect with the server than the `bind-address`, as those clients might with servers in a private cloud or multi-homed environment. Not specifying this option or setting this option to the empty string ("") causes the `bind-address` to be given to clients.| |
+| ‑‑max-connections | Sets the maximum number of client connections allowed. When the maximum is reached the cache server will stop accepting connections. | |
+| ‑‑message-time-to-live | Sets the time (in seconds ) after which a message in the client queue will expire. | |
+| ‑‑max-message-count | Sets maximum number of messages that can be enqueued in a client-queue.| |
+| ‑‑max-threads | Sets the maximum number of threads allowed in this cache server to service client requests. The default of 0 causes the cache server to dedicate a thread for every client connection. When client-server TLS/SSL is configured, values other than the default are not supported. | |
+| ‑‑socket-buffer-size | Sets the buffer size in bytes of the socket connection for this CacheServer. The default is 32768 bytes.| |
+| ‑‑lock-memory | (Linux only) When true, the member's heap and off-heap memory are locked in RAM, preventing them from being paged to disk. You must increase the related `ulimit` operating system resource to allow the OS to lock memory chunks of sufficient size.| false |
+| ‑‑off-heap-memory-size | The integer quantity of off-heap memory to be used for storing region values. Specified in Gigabytes with a "g" suffix, or Megabytes with an "m" suffix. For example, allocate a 2 Gigabyte off-heap space with `--off-heap-memory-size=2g`. The default value of 0 does not use any off-heap memory.| 0 |
+| ‑‑start-rest-api | When true, starts the REST API service. | false |
+| ‑‑redirect-output | When true, redirect standard output and standard error to the server log file. If specified without a value, the value is set to true. | false |
+| ‑‑http-service-port | Specifies the HTTP service port. | 7070 |
+| ‑‑http-service-bind-address | Specifies the IP address to which the HTTP service will be bound. | the local host machine's address |
+| ‑‑username<br />‑‑user | The user name of the credential to use in authenticating to the cluster. When specified, if the `--password` option is not also specified, then `gfsh` will prompt for the password.| |
+| ‑‑password | The password portion of the credential to use in authenticating to the cluster. | |
### <a id="topic_3764EE2DB18B4AE4A625E0354471738A__section_A50120613D3C4A848463236C4EFF18C7" class="no-quick-link"></a>Examples
diff --git a/geode-docs/tools_modules/gfsh/command-pages/status.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/status.html.md.erb
index a6a221ad63..570b2ee9cb 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/status.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/status.html.md.erb
@@ -94,8 +94,8 @@ status gateway-receiver [--groups=value(,value)*] [--members=value(,value)*]
| Name | Description |
|------------------------------------------------|-----------------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-groups</span> | Group(s) of Gateway Receivers for which to display status. |
-| <span class="keyword parmname">\\-\\-members</span> | Name or ID of the Gateway Receiver(s) for which to display status. |
+| <span class="keyword parmname">‑‑groups</span> | Group(s) of Gateway Receivers for which to display status. |
+| <span class="keyword parmname">‑‑members</span> | Name or ID of the Gateway Receiver(s) for which to display status. |
<span class="tablecap">Table 1. Status Gateway-Receiver Parameters</span>
@@ -152,8 +152,8 @@ status gateway-sender --id=value [--groups=value(,value)*]
| Name | Description |
|--------------------------------------------------|-----------------------------------------------------------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-id </span> | *Required.* ID of the Gateway Sender. |
-| <span class="keyword parmname">\\-\\-groups </span> | Group(s) of Gateway Senders for which to display status. Comma separated list for multiple member groups. |
+| <span class="keyword parmname">‑‑id </span> | *Required.* ID of the Gateway Sender. |
+| <span class="keyword parmname">‑‑groups </span> | Group(s) of Gateway Senders for which to display status. Comma separated list for multiple member groups. |
| <span class="keyword parmname">‑‑members </span> | Name/ID of the Gateway Sender(s) for which to display status. |
<span class="tablecap">Table 2. Status Gateway-Sender Parameters</span>
@@ -224,10 +224,10 @@ status locator [--name=value] [--host=value] [--port=value] [--dir=value] [--sec
| Name | Description | Default Value |
|----------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|
| <span class="keyword parmname">‑‑name</span> | Name/ID of the locator for which to display status. You must be connected to the JMX Manager to use this option. Can be used to obtain status of remote locators. See [Using gfsh to Manage a Remote Cluster Over HTTP or HTTPS](../../../configuring/cluster_config/gfsh_remote.html). | |
-| <span class="keyword parmname">\\-\\-host</span> | Hostname or IP address on which the Locator is running. | |
-| <span class="keyword parmname">\\-\\-port</span> | Port on which the locator is listening. | 10334 |
-| <span class="keyword parmname">\\-\\-dir</span> | Directory in which the locator was started. | current directory |
-| <span class="keyword parmname">\\-\\-security\\-properties\\-file</span> | The properties file for configuring SSL to connect to the SSL-enabled Locator. The file's path can be absolute or relative to the gfsh directory. [...]
+| <span class="keyword parmname">‑‑host</span> | Hostname or IP address on which the Locator is running. | |
+| <span class="keyword parmname">‑‑port</span> | Port on which the locator is listening. | 10334 |
+| <span class="keyword parmname">‑‑dir</span> | Directory in which the locator was started. | current directory |
+| <span class="keyword parmname">‑‑security‑properties‑file</span> | The properties file for configuring SSL to connect to the SSL-enabled Locator. The file's path can be absolute or relative to the gfsh directory. [...]
<span class="tablecap">Table 3. Status Locator Parameters</span>
@@ -297,7 +297,7 @@ status server [--name=value] [--dir=value]
| Name | Description | Default Value |
|----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|
| <span class="keyword parmname">‑‑name</span> | Name or ID of the Cache Server for which to display status. You must be connected to the JMX Manager to use this option. Can be used to obtain status of remote servers. See [Using gfsh to Manage a Remote Cluster Over HTTP or HTTPS](../../../configuring/cluster_config/gfsh_remote.html). | |
-| <span class="keyword parmname">\\-\\-dir </span> | Directory in which the <%=vars.product_name%> Cache Server was started. | current directory |
+| <span class="keyword parmname">‑‑dir </span> | Directory in which the <%=vars.product_name%> Cache Server was started. | current directory |
<span class="tablecap">Table 4. Status Server Parameters</span>
diff --git a/geode-docs/tools_modules/gfsh/command-pages/stop.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/stop.html.md.erb
index 138d48475a..68a8661036 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/stop.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/stop.html.md.erb
@@ -55,7 +55,7 @@ stop gateway-receiver [--groups=value(,value)*] [--members=value(,value)*]
| Name | Description |
|-------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-groups</span> | Group(s) of members on which to stop the Gateway Receiver. Use a comma-separated list for multiple member groups. |
+| <span class="keyword parmname">‑‑groups</span> | Group(s) of members on which to stop the Gateway Receiver. Use a comma-separated list for multiple member groups. |
| <span class="keyword parmname">‑‑members </span> | Name/Id of the member(s) on which to stop the Gateway Receiver. |
<span class="tablecap">Table 1. Stop Gateway-Receiver Parameters</span>
@@ -108,9 +108,9 @@ stop gateway-sender --id=value [--groups=value(,value)*] [--members=value(,value
| Name | Description |
|-------------------------------------------------|------------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-id </span> | *Required.* ID of the Gateway Sender. |
-| <span class="keyword parmname">\\-\\-groups</span> | Group(s) of members on which to stop the Gateway Sender. |
-| <span class="keyword parmname">\\-\\-members</span> | Name/Id of the member(s) on which to stop the Gateway Sender. |
+| <span class="keyword parmname">‑‑id </span> | *Required.* ID of the Gateway Sender. |
+| <span class="keyword parmname">‑‑groups</span> | Group(s) of members on which to stop the Gateway Sender. |
+| <span class="keyword parmname">‑‑members</span> | Name/Id of the member(s) on which to stop the Gateway Sender. |
<span class="tablecap">Table 2. Stop Gateway-Sender Parameters</span>
@@ -163,7 +163,7 @@ stop locator --name=value | --dir=value
| Name | Description | Default V [...]
|----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------- [...]
| <span class="keyword parmname">‑‑name</span> | The <%=vars.product_name%> member name of the locator to stop. You must be connected to the JMX Manager to use this option. Can be used to stop remote locators. See [Using gfsh to Manage a Remote Cluster Over HTTP or HTTPS](../../../configuring/cluster_config/gfsh_remote.html). | |
-| <span class="keyword parmname">\\-\\-dir</span> | Directory in which the locator was started. | current directory |
+| <span class="keyword parmname">‑‑dir</span> | Directory in which the locator was started. | current directory |
<span class="tablecap">Table 3. Stop Locator Parameters</span>
@@ -210,7 +210,7 @@ stop server [--name=value] [--dir=value]
| Name | Description | Default Value |
|-----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|
| <span class="keyword parmname">‑‑name </span> | Name/Id of the <%=vars.product_name%> Cache Server to stop. You must be connected to the JMX Manager to use this option. Can be used to stop remote servers. See [Using gfsh to Manage a Remote Cluster Over HTTP or HTTPS](../../../configuring/cluster_config/gfsh_remote.html). | |
-| <span class="keyword parmname">\\-\\-dir </span> | Directory in which the <%=vars.product_name%> Cache Server was started. | current directory |
+| <span class="keyword parmname">‑‑dir </span> | Directory in which the <%=vars.product_name%> Cache Server was started. | current directory |
<span class="tablecap">Table 4. Stop Server Parameters</span>
diff --git a/geode-docs/tools_modules/gfsh/command-pages/undeploy.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/undeploy.html.md.erb
index c795536c52..699e8639b8 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/undeploy.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/undeploy.html.md.erb
@@ -35,8 +35,8 @@ undeploy [--jars=value(,value)*] [--groups=value(,value)*]
| Name | Description | Default Value |
|-----------------------------------------------|--------------------------------------------------------------|-------------------------------------|
-| <span class="keyword parmname">\\-\\-groups</span> | Group(s) from which the specified JAR(s) will be undeployed. | undeploy will occur on all members |
-| <span class="keyword parmname">\\-\\-jars</span> | JAR or JARs to be undeployed. | All JARs will be undeployed |
+| <span class="keyword parmname">‑‑groups</span> | Group(s) from which the specified JAR(s) will be undeployed. | undeploy will occur on all members |
+| <span class="keyword parmname">‑‑jars</span> | JAR or JARs to be undeployed. | All JARs will be undeployed |
<span class="tablecap">Table 1. Undeploy Parameters</span>
diff --git a/geode-docs/tools_modules/gfsh/command-pages/validate.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/validate.html.md.erb
index 0fc460d79b..5b9e30bc65 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/validate.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/validate.html.md.erb
@@ -34,8 +34,8 @@ validate offline-disk-store --name=value --disk-dirs=value(,value)*
| Name | Description |
|----------------------------------------------------|-------------------------------------------------------------------------------|
-| <span class="keyword parmname">\\-\\-name</span> | *Required.* Name of the disk store to be validated. |
-| <span class="keyword parmname">\\-\\-disk-dirs </span> | *Required.* Directories where data for the disk store was previously written. |
+| <span class="keyword parmname">‑‑name</span> | *Required.* Name of the disk store to be validated. |
+| <span class="keyword parmname">‑‑disk-dirs </span> | *Required.* Directories where data for the disk store was previously written. |
<span class="tablecap">Table 1. Validate Offline-Disk-Store Parameters</span>
diff --git a/geode-docs/tools_modules/gfsh/command-pages/version.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/version.html.md.erb
index 217bf2300e..28ce8136f1 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/version.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/version.html.md.erb
@@ -33,7 +33,7 @@ version [--full]
| Name | Description | Defalut Value |
|-----------------------------------------------|---------------------------------------------------------|---------------|
-| <span class="keyword parmname">\\-\\-full </span> | Show the full version information. | false |
+| <span class="keyword parmname">‑‑full </span> | Show the full version information. | false |
<span class="tablecap">Table 1. Version Parameters</span>
diff --git a/geode-docs/topologies_and_comm/topology_concepts/using_bind_addresses.html.md.erb b/geode-docs/topologies_and_comm/topology_concepts/using_bind_addresses.html.md.erb
index b9f0130838..940eab51dd 100644
--- a/geode-docs/topologies_and_comm/topology_concepts/using_bind_addresses.html.md.erb
+++ b/geode-docs/topologies_and_comm/topology_concepts/using_bind_addresses.html.md.erb
@@ -41,7 +41,7 @@ This table lists the settings used for peer and server communication, ordered by
| Property Setting Ordered by Precedence | Peer | Server | Gateway Receiver | Syntax |
|------------------------------------------------------|------|--------|------------------|---------------------------------------------------|
| cache.xml <cache-server> bind-address | | X | | <cache-server>bind-address=*address* |
-| gfsh start server command-line --server-bind-address | | X | X | gfsh start server --server-bind-address=*address* |
+| gfsh start server command-line ‑‑server-bind-address | | X | X | gfsh start server ‑‑server-bind-address=*address* |
| gemfire.properties server-bind-address | | X | X | server-bind-address=*address* |
| gemfire.properties bind-address | X | X | X | bind-address=*address* |
@@ -72,7 +72,7 @@ This table lists the settings used for peer, server, and gateway receiver commun
|------------------------------------------------------|------|--------|------------------|---------------------------------------------------|
| cache.xml <gateway-receiver> bind-address | | | X | <gateway-receiver>bind-address=*address* |
| cache.xml <cache-server> bind-address | | X | | <cache-server>bind-address=*address* |
-| gfsh start server command-line --server-bind-address | | X | X | gfsh start server --server-bind-address=*address* |
+| gfsh start server command-line ‑‑server-bind-address | | X | X | gfsh start server ‑‑server-bind-address=*address* |
| gemfire.properties server-bind-address | | X | X | server-bind-address=*address* |
| gemfire.properties bind-address | X | X | X | bind-address=*address* |