geode-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dbar...@apache.org
Subject [geode] branch develop updated: User Guide: fixed typo in the cluster config section
Date Wed, 01 Nov 2017 21:50:32 GMT
This is an automated email from the ASF dual-hosted git repository.

dbarnes pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/geode.git


The following commit(s) were added to refs/heads/develop by this push:
     new 721a7e9  User Guide: fixed typo in the cluster config section
721a7e9 is described below

commit 721a7e95b864789dce863d21b4b7e04ec49adf6b
Author: Dave Barnes <dbarnes@pivotal.io>
AuthorDate: Wed Nov 1 14:50:27 2017 -0700

    User Guide: fixed typo in the cluster config section
---
 .../cluster_config/gfsh_config_troubleshooting.html.md.erb            | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/geode-docs/configuring/cluster_config/gfsh_config_troubleshooting.html.md.erb
b/geode-docs/configuring/cluster_config/gfsh_config_troubleshooting.html.md.erb
index 0243245..ecc7e14 100644
--- a/geode-docs/configuring/cluster_config/gfsh_config_troubleshooting.html.md.erb
+++ b/geode-docs/configuring/cluster_config/gfsh_config_troubleshooting.html.md.erb
@@ -45,7 +45,7 @@ You can export a zip file that contains all artifacts of a cluster configuration
 
 ## Individual Configuration Files and Cluster Configuration Files
 
-<%=vars.product_name%> applies the cluster-wide configuration files first and then
group-level configurations next. If a member has its own configuration files defined (cache.xml
and gemfire.properties files), those configurations are applied last. Whenever possible, use
the member group-level configuration files in the cluster-configuration service to apply non-cluster-wide
configurations on individual members.
+<%=vars.product_name%> applies the cluster-wide configuration files first and then
group-level configurations next. If a member has its own configuration files defined (cache.xml
and gemfire.properties files), those configurations are applied last. Whenever possible, use
the member group-level configuration files in the cluster configuration service to apply non-cluster-wide
configurations on individual members.
 
 ## Troubleshooting Tips
 
@@ -55,7 +55,7 @@ You can export a zip file that contains all artifacts of a cluster configuration
     Cluster configuration service is up and running.
     ```
 
-    If you do not see this message, there may be a problem with the cluster configuration
service. Use the `status cluster-configuration-service` command to check the status of the
cluster configuration.
+    If you do not see this message, there may be a problem with the cluster configuration
service. Use the `status cluster-config-service` command to check the status of the cluster
configuration.
 
     -   If the command returns RUNNING, the cluster configuration is running normally.
     -   If the command returns WAITING, run the `status locator` command. The output of this
command returns the cause of the WAITING status.

-- 
To stop receiving notification emails like this one, please contact
['"commits@geode.apache.org" <commits@geode.apache.org>'].

Mime
View raw message