Description
When user starts locator with --connect=false, it should not retrieve cluster-configuration service status.
gfsh>start locator --name=locator1 --connect=false Starting a Geode Locator in /Users/sai/workspace/debug/apache-geode-1.5.0-SNAPSHOT/bin/locator1... ... Locator in /Users/sai/workspace/debug/apache-geode-1.5.0-SNAPSHOT/bin/locator1 on 10.118.19.26[10334] as locator1 is currently online. Process ID: 21762 Uptime: 2 seconds Geode Version: 1.5.0-SNAPSHOT Java Version: 1.8.0_151 Log File: /Users/sai/workspace/debug/apache-geode-1.5.0-SNAPSHOT/bin/locator1/locator1.log JVM Arguments: -Dgemfire.enable-cluster-configuration=true -Dgemfire.load-cluster-configuration-from-dir=false -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806 Class-Path: /Users/sai/workspace/debug/apache-geode-1.5.0-SNAPSHOT/lib/geode-core-1.5.0-SNAPSHOT.jar:/Users/sai/workspace/debug/apache-geode-1.5.0-SNAPSHOT/lib/geode-dependencies.jar Cluster configuration service is up and running.
As you can see that it retrieves the status and displays cluster configuration service is running.