[
https://issues.apache.org/jira/browse/GEODE-6303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749285#comment-16749285
]
ASF subversion and git services commented on GEODE-6303:
--------------------------------------------------------
Commit 106200b893a4d20ef988b38cdb4d0114000dab18 in geode's branch
refs/heads/feature/GEODE-6303 from Bruce Schuchardt
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=106200b ]
GEODE-6303 Membership gets confused by multiple locators being specified by gfsh
Added canonicalization of locator addresses so that duplicate
entries in the "locators" setting are ignored.
> 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
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)
