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: Corrections to the cluster config deployment section
Date Wed, 01 Nov 2017 23:17:16 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 8f3d052  User Guide: Corrections to the cluster config deployment section
8f3d052 is described below

commit 8f3d052f851a4aeb0d1ed9548cb52849c2c1c7e3
Author: Dave Barnes <dbarnes@pivotal.io>
AuthorDate: Wed Nov 1 16:17:11 2017 -0700

    User Guide: Corrections to the cluster config deployment section
---
 .../cluster_config/gfsh_load_from_shared_dir.html.md.erb            | 4 ----
 .../configuring/running/deploying_config_jar_files.html.md.erb      | 6 ++----
 2 files changed, 2 insertions(+), 8 deletions(-)

diff --git a/geode-docs/configuring/cluster_config/gfsh_load_from_shared_dir.html.md.erb b/geode-docs/configuring/cluster_config/gfsh_load_from_shared_dir.html.md.erb
index d8ba4d9..3b5a9eb 100644
--- a/geode-docs/configuring/cluster_config/gfsh_load_from_shared_dir.html.md.erb
+++ b/geode-docs/configuring/cluster_config/gfsh_load_from_shared_dir.html.md.erb
@@ -38,7 +38,3 @@ You can use this technique to migrate a single server's configuration into
the c
 
     After successful startup, the locator should report that the "Cluster configuration service
is up and running." Any servers that join this cluster and have `--use-cluster-configuration`
set to true will pick up these configuration files.
 
-**Note:**
-If you make any manual modifications to the cluster.xml or cluster.properties (or group\_name.xml
or group\_name.properties) files, you must stop the locator and then restart the locator using
the `--load-cluster-configuration-from-dir` parameter. Direct file modifications are not picked
up iby the cluster configuration service without a locator restart.
-
-
diff --git a/geode-docs/configuring/running/deploying_config_jar_files.html.md.erb b/geode-docs/configuring/running/deploying_config_jar_files.html.md.erb
index 23a9201..19a5cba 100644
--- a/geode-docs/configuring/running/deploying_config_jar_files.html.md.erb
+++ b/geode-docs/configuring/running/deploying_config_jar_files.html.md.erb
@@ -43,10 +43,8 @@ myConfig/myCache.xml
 
 In this example, you would perform the following steps to deploy the configuration jar file:
 
-1.  Set the system property, `gemfire.cache-xml-file`, to `myConfig/myCache.xml`
+1.  Set the system property `gemfire.cache-xml-file` to `myConfig/myCache.xml`.
 2.  Set your `CLASSPATH` to include `my.jar`.
-3.  Verify there is no file named `myCache.xml` in `./myConfig/myCache.xml`, the current
directory location of the file
+3.  Verify there is no file already  in the filesystem named `./myConfig/myCache.xml`, so
<%=vars.product_name%> will be forced to search the jar file to find it.
 
 When you start your application, the configuration file is loaded from the jar file.
-
-

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

Mime
View raw message