[
https://issues.apache.org/jira/browse/GEODE-6303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-6303:
----------------------------------
Labels: pull-request-available (was: )
> Membership gets confused by multiple locators being specified by gfsh
> ---------------------------------------------------------------------
>
> Key: GEODE-6303
> URL: https://issues.apache.org/jira/browse/GEODE-6303
> Project: Geode
> Issue Type: Bug
> Components: membership
> Reporter: Bruce Schuchardt
> Assignee: Bruce Schuchardt
> Priority: Major
> Labels: pull-request-available
>
> I started a locator using gfsh and a gemfire.properties file that specified
> that locator.
> gfsh start locator --name=locator1 --properties-file=$PWD/gemfire.properties
> gemfire.properties:
> locators=trout.gemstone.com[30015]
> locator-wait-time=120
> jmx-manager-start=true
> jmx-manager-port=30016
> log-level=info
> statistic-sampling-enabled=true
> statistic-sample-rate=60000
> max-wait-time-reconnect=5000
> log-level=fine
>
> Log files show that the locator was given two addresses in its "locators"
> setting. One was the address I had in my gemfire.properties file and the
> other was the same but using its numeric IPv4 address.
> locators=trout.gemstone.com[30015],10.118.26.122[30015]
>
> Logs show that both of these addresses were contacted during startup and this
> caused the locator to take more time starting up.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
