[
https://issues.apache.org/jira/browse/GEODE-7926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073068#comment-17073068
]
ASF subversion and git services commented on GEODE-7926:
--------------------------------------------------------
Commit 88c165c4bb40750c02f38eedb5b5198fe5ffd123 in geode's branch
refs/heads/feature/GEODE-7926b from Bruce Schuchardt
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=88c165c ]
GEODE-7926: GMSMemberData is doing unnecessary reverse-DNS lookups
Removed hostname lookup from GMSMemberData a serialization method.
InternalDistributedMember does its own hostname lookup & there's no
reason for the lookup in GMSMemberData. I found it was slowing down UDP
communications.
> GMSMemberData is doing unnecessary reverse-DNS lookups
> ------------------------------------------------------
>
> Key: GEODE-7926
> URL: https://issues.apache.org/jira/browse/GEODE-7926
> Project: Geode
> Issue Type: Bug
> Components: membership, messaging
> Reporter: Bruce J Schuchardt
> Assignee: Bruce J Schuchardt
> Priority: Major
>
> When we send a message via JGroups we write a serialized GMSMemberData in the
> header of the message. When this is deserialized we are currently using
> InetAddress.getHostName() to establish a hostname for the new instance. This
> is costly and unnecessary. We should just use getHostAddress() if we need a
> hostname in the address data. Geode's InternalDistributedMember doesn't rely
> on GMSMemberData to establish hostnames for geode-core and other downstream
> modules.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
