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 "Steve Loughran (Commented) (JIRA)" <ji...@apache.org> on 2012/02/18 22:29:59 UTC

[jira] [Commented] (HADOOP-3456) IPC.Client connect timeout should be configurable

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

Steve Loughran commented on HADOOP-3456:
----------------------------------------

marking as duplicate of HADOOP-7397 -that issue has code, so wins
                
> IPC.Client connect timeout should be configurable
> -------------------------------------------------
>
>                 Key: HADOOP-3456
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3456
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ipc
>    Affects Versions: 0.18.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Minor
>
> In ipc.Client.setupIOStreams, the connect timeout is hard-coded to 20 seconds
>             // connection time out is 20s
>             this.socket.connect(remoteId.getAddress(), 20000);
> This could be made configurable for deployments where a longer connect time is desired, or where a shorter connect time would detect failure faster.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira