accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Newton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1351) document HDFS timeout settings
Date Fri, 26 Apr 2013 14:56:17 GMT

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

Eric Newton commented on ACCUMULO-1351:
---------------------------------------

To test, stop the datanode and the tserver on the same box with SIGSTOP.

After the tserver lock is lost, the master calls recoverLease() on the namenode.  The namenode
tries to talk to the primary node for the pipeline, which is the datanode which is also stopped.
 Without these settings, the request takes a long time.  Eventually, the master calls recoverLease()
again, and that restarts the whole cycle.

There are additional details and analysis in HBASE-8389.

                
> document HDFS timeout settings
> ------------------------------
>
>                 Key: ACCUMULO-1351
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1351
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: docs
>            Reporter: Eric Newton
>            Assignee: Eric Newton
>            Priority: Minor
>             Fix For: 1.5.0
>
>
> Document these settings so that recovery can be responsive:
> {noformat}
> dfs.socket.timeout = 3sec
> dfs.socket.write.timeout = 5sec
> ipc.client.connect.timeout = 1sec
> ipc.client.connect.max.retries.on.timeouts = 2
> {noformat}

--
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

Mime
View raw message