giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Akira Ajisaka (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GIRAPH-1110) Use Configuration.setInt instead of Client.setPingInterval in GiraphJob
Date Fri, 09 Sep 2016 07:01:21 GMT

    [ https://issues.apache.org/jira/browse/GIRAPH-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15476148#comment-15476148
] 

Akira Ajisaka commented on GIRAPH-1110:
---------------------------------------

bq. This workaround seems temporal solution to me.
No, this is not a workaround. The problem will be fixed in 2.6.5/2.7.4, but not in 2.8.0+.
I'm thinking we need to change the code in Apache Giraph as well.

> Use Configuration.setInt instead of Client.setPingInterval in GiraphJob
> -----------------------------------------------------------------------
>
>                 Key: GIRAPH-1110
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-1110
>             Project: Giraph
>          Issue Type: Improvement
>            Reporter: Akira Ajisaka
>         Attachments: GIRAPH-1110.01.patch
>
>
> After HADOOP-11252, Client.setPingInterval is not public.
> {code:title=GiraphJob}
>     Client.setPingInterval(giraphConfiguration, 60000 * 5);
> {code}
> should be
> {code}
>     giraphConfiguration.setInt("ipc.ping.interval", 60000 * 5);
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message