[ https://issues.apache.org/jira/browse/GEODE-8872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17288311#comment-17288311 ]
ASF GitHub Bot commented on GEODE-8872: --------------------------------------- mivanac commented on pull request #5948: URL: https://github.com/apache/geode/pull/5948#issuecomment-783284073 When deploying geode, for locator we define hostname-for-clients. This is extern address used for WAN, and extern clients. If we also deploy some clients in internal network (for example in the same kubernetes cluster as geode), then for those clients to connect with locator, communication will go from internal network to external, then from external to internal. This increases latency, and we should communicate over the shortest path. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Add client option, to request locators internal host addresses > --------------------------------------------------------------- > > Key: GEODE-8872 > URL: https://issues.apache.org/jira/browse/GEODE-8872 > Project: Geode > Issue Type: New Feature > Components: client/server > Reporter: Mario Ivanac > Assignee: Mario Ivanac > Priority: Major > Labels: pull-request-available > > Additional option for clients, when pool is created, to request locators > internal host addresses. > When sending LocatorListRequest in some cases we need to get internal host > addresses. -- This message was sent by Atlassian Jira (v8.3.4#803005)