Pulkit Chandra created GEODE-2052:
-------------------------------------
Summary: Docs to segregate types of properties
Key: GEODE-2052
URL: https://issues.apache.org/jira/browse/GEODE-2052
Project: Geode
Issue Type: Improvement
Components: docs
Reporter: Pulkit Chandra
GemFire has a lot of properties. But they are not mentioned in context but
rather listed as gemfire properties which can go in gemfire.properties and
gfsecurity.properties.
It would nice to have a segregation by Locator and server under
gemfire.properties. The reason for this ask is that some properties do not
apply to both locator and server. Currently the only way to know this is by
experience or trial and error.
We also found out that some of the gemfire.properties do not get applied when
supplied in gemfire.properties but rather have to be passed as command line
properties. e.g. enabling rest api.
It would be nice to call that out clearly in docs.
There are example of properties which have to be applied together in order to
enable a functionality e.g. rest api needs bind address property and
http-service-port. Its not called out clearly in the docs that they are
*mandatory*.
[link to docs
section](http://geode.incubator.apache.org/docs/guide/rest_apps/setup_config.html)
quote
```
To enable the developer REST API service in Apache Geode, set the
start-dev-rest-api Geode property to true when starting a data node using
either gfsh or the ServerLauncher API. Setting this property to true on a data
node will start up an embedded Jetty server and deploy the REST developer API
WAR file.
```
It should highlight that its necessary to have 2 more properties bind-address
and http-service-port defined to make it work.
We would be happy to provide further details on this matter if needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
