[
https://issues.apache.org/jira/browse/GEODE-7926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073063#comment-17073063
]
ASF subversion and git services commented on GEODE-7926:
--------------------------------------------------------
Commit ba6436debc4ed23b670435d9c1ab1b12846d6238 in geode's branch
refs/heads/feature/GEODE-7926 from Bruce Schuchardt
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ba6436d ]
GEODE-7926: GMSMemberData is doing unnecessary reverse-DNS lookups
The hostname established in GMSMemberData by its serialization method
isn't important for Membership communications. There's no reason to do
an InetAddress -> hostname lookup in this method, and it's slowing
things down when sending messages via JGroups.
> 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)
