hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Patrick McCabe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4859) Add timeout in FileJournalManager
Date Thu, 30 May 2013 00:48:20 GMT

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

Colin Patrick McCabe commented on HDFS-4859:
--------------------------------------------

I just don't think it's worth adding a lot of complexity to FJM, to handle something that's
better handled by HA.  Surely that's a reasonable position?

It's also kind of weird to hear the argument "HA is too new to deploy, therefore we need to
develop a bunch of new code to work around not having it."  Wha?

But I've talked enough, I'll let other people chime in with their opinions.
                
> 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

Mime
View raw message