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

["Steve Loughran (JIRA)" <ji...@apache.org>]

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

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

Reviewing this, the problem is still present in 0.22 

# It is simple enough to add this as a new configuration parameter. Proposed: {{ipc.client.connect.timeout}}, keep 20000 as the default
# Testing: try to connect to a host whose hostname resolves, but doesn't have a live endpoint, with a timeout of 0. The obvious target is "localhost". Then look at the test time.

The trouble with that test is that a localhost connect will probable fail with a connection refused exception, which may not stress the timeout. What we really want is a hostname that resolve (e.g. example.org) but which isn't running a live server, but nor is it rejecting connection requests outright.

Thoughts?



> 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
>            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.
-
You can reply to this email to add a comment to the issue online.