You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Dave Barnes (JIRA)" <ji...@apache.org> on 2017/06/13 17:04:00 UTC

[jira] [Created] (GEODE-3069) Cluster config: unnecessary & misleading warning when cluster config not in use

Dave Barnes created GEODE-3069:
----------------------------------

             Summary: Cluster config: unnecessary & misleading warning when cluster config not in use
                 Key: GEODE-3069
                 URL: https://issues.apache.org/jira/browse/GEODE-3069
             Project: Geode
          Issue Type: Improvement
          Components: configuration, docs
            Reporter: Dave Barnes


Following the user guide example for "Using the Swagger UI to Browse REST APIs" (http://geode.apache.org/docs/guide/11/rest_apps/using_swagger.html), the user sets up a jmx manager on a server, without starting a locator (which is not needed for the example).

Then, when creating a region, the user gets an error message indicating that there's a problem and recommending a procedure to fix it:
```
gfsh>create region --name=region1 --type=REPLICATE --key-constraint=java.lang.String
Failed to persist the configuration changes due to this command, Revert the command to maintain consistency.
Please use "status cluster-config-service" to determine whether Cluster configuration service is RUNNING.
   Member     | Status
------------- | --------------------------------------------
gfsec-server1 | Region "/region1" created on "gfsec-server1"
```
This warning ("Failed to persist...Please use...") is new (the user guide example, written for an earlier version, doesn't show it) and misleading, as the operation has succeeded.
For v1.2, the user guide has been changed to also start a locator, which instantiates the cluster configuration service, but the correct fix is to suppress this message, as the locator is superfluous in this case.

NB: To recreate, follow the example instructions in the user guide, being sure to add the 'optional' --J=-Dgemfire.http-service-port=8080 parameter to the start server command.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)