You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@geode.apache.org by bs...@apache.org on 2016/06/10 21:18:08 UTC

[2/2] incubator-geode git commit: GEODE-1527: Locator javadoc mentions the old "gemfire" command

GEODE-1527: Locator javadoc mentions the old "gemfire" command

Altered the javadoc to point the user at gfsh instead of gemfire.


Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/d28ac959
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/d28ac959
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/d28ac959

Branch: refs/heads/develop
Commit: d28ac959400e49d512561f3204696d85b306e8d4
Parents: f8dd6ce
Author: Bruce Schuchardt <bs...@pivotal.io>
Authored: Fri Jun 10 14:11:42 2016 -0700
Committer: Bruce Schuchardt <bs...@pivotal.io>
Committed: Fri Jun 10 14:17:56 2016 -0700

----------------------------------------------------------------------
 .../gemstone/gemfire/distributed/Locator.java   | 20 +++++++++-----------
 1 file changed, 9 insertions(+), 11 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/d28ac959/geode-core/src/main/java/com/gemstone/gemfire/distributed/Locator.java
----------------------------------------------------------------------
diff --git a/geode-core/src/main/java/com/gemstone/gemfire/distributed/Locator.java b/geode-core/src/main/java/com/gemstone/gemfire/distributed/Locator.java
index ddcc48a..8795b71 100644
--- a/geode-core/src/main/java/com/gemstone/gemfire/distributed/Locator.java
+++ b/geode-core/src/main/java/com/gemstone/gemfire/distributed/Locator.java
@@ -31,13 +31,7 @@ import com.gemstone.gemfire.internal.i18n.LocalizedStrings;
  * Represents a distribution locator server that provides discovery information
  * to members and clients of a GemFire distributed system. In most GemFire
  * distributed cache architectures, distribution locators are run in their own
- * process. A stand-alone locator process is managed using 
- * {@linkplain com.gemstone.gemfire.admin.DistributionLocator administration
- * API} or the <code>gemfire</code> command line utility:
- * 
- * <PRE>
- * $ gemfire start-locator
- * </PRE>
+ * process. A stand-alone locator process is managed using gfsh command line utility. 
  * 
  * The stand-alone locator configuration provides high-availability of
  * membership information.
@@ -47,12 +41,16 @@ import com.gemstone.gemfire.internal.i18n.LocalizedStrings;
  * This class allows a GemFire application VM to host a distribution locator.
  * Such a configuration minimizes the number of processes that are required to
  * run GemFire. However, hosting distribution locators is not generally
- * recommended because if the application VM exits, the primary membership list
- * for the distributed system would be lost and it would not be possible for new
- * applications to connect to the distributed system.
+ * recommended because if the application VM exits it would not be possible for new
+ * applications to connect to the distributed system until it is restarted.
  * 
  * <P>
+ * Locators persist membership information in a locatorXXXview.dat file.  This
+ * file is used to recover information about the cluster when a locator starts
+ * if there are no other currently running locators.  It allows the restarted
+ * locator to rejoin the cluster.
  * 
+ * <P>
  * <b>NOTE:</b> In this release of the product locators log membership views and
  * cache server status in a locatorXXXviews.log file, where XXX is the locator's port.
  * This is a rolling log
@@ -61,8 +59,8 @@ import com.gemstone.gemfire.internal.i18n.LocalizedStrings;
  * or be started so that it creates a DistributedSystem.  This means that it is
  * not possible in this release to use APIs to start a locator and <i>then</i>
  * start a DistributedSystem.
- * 
  * <P>
+ *   
  *  
  * @since GemFire 4.0
  */