hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6099) Allow configuring the IPC module to send pings
Date Fri, 10 Jul 2009 12:27:14 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-6099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12729620#action_12729620

Hadoop QA commented on HADOOP-6099:

-1 overall.  Here are the results of testing the latest attachment 
  against trunk revision 792812.

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 3 new or modified tests.

    -1 patch.  The patch command could not apply the patch.

Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/562/console

This message is automatically generated.

> Allow configuring the IPC module to send pings
> ----------------------------------------------
>                 Key: HADOOP-6099
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6099
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ipc
>            Reporter: dhruba borthakur
>            Assignee: dhruba borthakur
>             Fix For: 0.21.0
>         Attachments: ipcPing.txt, ipcPing2.txt
> The IPC Client sets a socketTimeout for the time period specified by the pingInterval
and then sends a ping every pingInterval. This means that if a RPC server does not respond
to a RPC client, then the RPC client blocks forever. This is a problem for applications that
wants to switch quickly from one un-responsive HDFS cluster  to a good one. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message