geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Barnes (JIRA)" <>
Subject [jira] [Resolved] (GEODE-2052) Docs to segregate types of properties
Date Thu, 16 Feb 2017 18:29:41 GMT


Dave Barnes resolved GEODE-2052.
    Resolution: Fixed

Table of geode-* (gemfire-*) properties updated with a new column designating each property
as applicable to Server / Locator / Client. Info was obtained from developers and reviewed
by the ticket reporter.

> Docs to segregate types of properties
> -------------------------------------
>                 Key: GEODE-2052
>                 URL:
>             Project: Geode
>          Issue Type: Improvement
>          Components: docs
>            Reporter: Pulkit Chandra
>            Assignee: Dave Barnes
> Geode has a lot of properties. But they are not mentioned in context but rather listed
as geode properties which can go in and
> It would nice to have a segregation by Locator and Server under 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 do not get applied when supplied
in 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](
> ~~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

View raw message