[
https://issues.apache.org/jira/browse/GIRAPH-904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14021508#comment-14021508
]
Pavan Kumar commented on GIRAPH-904:
------------------------------------
+1 will commit the change
It is because of the difference in the way
InetSocketAddress and InetAddress behave when returning the name
for instance this is a the pseudocode of what I used
InetSocketAddress address = new InetSocketAddress("[masked].FACEBOOK.com",
8080);
System.out.println(address.getHostName()); // => HAS UPPER CASE
System.out.println(InetAddress.getByName("[masked].FACEBOOK.com").getCanonicalHostName());
// has lowercase
System.out.println(InetAddress.getLocalHost().getCanonicalHostName());
> Giraph can hang when hostnames include uppercase letters
> --------------------------------------------------------
>
> Key: GIRAPH-904
> URL: https://issues.apache.org/jira/browse/GIRAPH-904
> Project: Giraph
> Issue Type: Bug
> Components: bsp, conf and scripts, zookeeper
> Affects Versions: 1.1.0
> Reporter: Jaeho Shin
> Attachments: GIRAPH-904.BspServiceMaster-fix.patch,
> GIRAPH-904.getHostname-fix.patch, GIRAPH-904.patch
>
>
> We found that Giraph jobs were consistently hanging if uppercase letters were
> included in the DNS (or /etc/hosts) resolved hostnames ({{foo.stanford.edu}}
> vs. {{foo.Stanford.EDU}} from our DNS). Normalizing the hostnames to lower
> case from {{GiraphConfiguration#getLocalHostname()}} fixed our problem.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
