You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Jinmei Liao (Jira)" <ji...@apache.org> on 2022/05/18 19:13:00 UTC
[jira] [Commented] (GEODE-10318) locators property is unexpectedly being modified in InternalLocator
[ https://issues.apache.org/jira/browse/GEODE-10318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17539020#comment-17539020 ]
Jinmei Liao commented on GEODE-10318:
-------------------------------------
We should not have duplicate entries in the locators attributes. User's original specification should be honored first. The order of precedence to use in the locator's list is:
To summarize the thread, the order of precedence is:
# Address from locator list
# hostname-for-client
# bind-address
# guess, prefer hostname
> locators property is unexpectedly being modified in InternalLocator
> -------------------------------------------------------------------
>
> Key: GEODE-10318
> URL: https://issues.apache.org/jira/browse/GEODE-10318
> Project: Geode
> Issue Type: Bug
> Components: locator
> Reporter: Jinmei Liao
> Priority: Major
> Labels: needsTriage
>
> if a locator is started with existing "locators" attributes that points to itself using ip address, ie.
> {code:java}
> locators=192.168.0.15[22348]
> {code}
> if the machine has a hostname specified in its host file
> {code:java}
> 192.168.0.15 abc-a01
> {code}
> Then after the locator is started, the log banner would show duplicate entries in the locators attributes:
> {code:java}
> locators=192.168.0.15[22348],abc-a01[22348]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)