You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2013/05/28 19:02:21 UTC
[jira] [Commented] (HDFS-4859) Add timeout in FileJournalManager
[ https://issues.apache.org/jira/browse/HDFS-4859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13668447#comment-13668447 ]
Todd Lipcon commented on HDFS-4859:
-----------------------------------
Hey Kihwal. Are you planning on using NFS based HA? I'd highly recommend using QJM instead -- it has timeout features and has been much more reliable for us in production clusters.
> Add timeout in FileJournalManager
> ---------------------------------
>
> Key: HDFS-4859
> URL: https://issues.apache.org/jira/browse/HDFS-4859
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: ha, namenode
> Affects Versions: 2.0.4-alpha
> Reporter: Kihwal Lee
>
> Due to absence of explicit timeout in FileJournalManager, error conditions that incur long delay (usually until driver timeout) can make namenode unresponsive for long time. This directly affects NN's failure detection latency, which is critical in HA.
--
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