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 "Harsh J (JIRA)" <ji...@apache.org> on 2013/04/25 12:32:16 UTC

[jira] [Updated] (HADOOP-9503) Allow a configurable sleep between IPC client connect timeouts

     [ https://issues.apache.org/jira/browse/HADOOP-9503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Harsh J updated HADOOP-9503:
----------------------------

    Description: 
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 have a configurable parameter to reduce this sleep. 

  was:
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 have a configurable parameter to reduce this sleep. 

    
> Allow a configurable 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
>            Reporter: Varun Sharma
>            Priority: Minor
>
> 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 have a configurable parameter to reduce 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