You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2013/04/25 23:16:18 UTC

[jira] [Commented] (HADOOP-9503) Remove sleep between IPC client connect timeouts

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

Hudson commented on HADOOP-9503:
--------------------------------

Integrated in Hadoop-trunk-Commit #3666 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/3666/])
    HADOOP-9503. Remove sleep between IPC client connect timeouts.  Contributed by Varun Sharma (Revision 1475959)

     Result = SUCCESS
szetszwo : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1475959
Files : 
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ipc/Client.java

                
> Remove sleep between IPC client connect timeouts
> ------------------------------------------------
>
>                 Key: HADOOP-9503
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9503
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ipc
>    Affects Versions: 2.0.5-beta
>            Reporter: Varun Sharma
>            Assignee: Varun Sharma
>            Priority: Minor
>             Fix For: 2.0.5-beta
>
>         Attachments: 9503.patch
>
>
> HADOOP-9106 introduced a configurable retry timeout when there are socket timeouts errors.
> Since the IPC client is used by a wide variety of applications including realtime/online ones (like hbase + hdfs), we sometimes need fast fail timeouts which are < 3 seconds. Achieving such a timeout for connect is very difficult with a 1 second sleep in b/w retries. It would be good to remove this sleep. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira