You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@giraph.apache.org by "Tsuyoshi Ozawa (JIRA)" <ji...@apache.org> on 2016/09/09 06:29:20 UTC

[jira] [Comment Edited] (GIRAPH-1110) Use Configuration.setInt instead of Client.setPingInterval in GiraphJob

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

Tsuyoshi Ozawa edited comment on GIRAPH-1110 at 9/9/16 6:28 AM:
----------------------------------------------------------------

This problem will be fixed on next minor releases(2.6.5 and 2.7.4). This workaround seems temporal solution to me. Hence, it looks better to me to release Hadoop's next point releases soon.


was (Author: ozawa):
This problem will be fixed on next minor releases(2.6.5 and 2.7.4). This workaround seems temporal solution to me. It looks beeter to me to release next point releases soon.

> 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)