hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uma Maheswara Rao G (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3392) BookKeeper Journal Manager is not retrying to connect to BK when BookKeeper is not available for write.
Date Wed, 09 May 2012 06:28:00 GMT

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

Uma Maheswara Rao G commented on HDFS-3392:
-------------------------------------------

Since all BKs stopped, client will throw the exception. Here expectation is, at least quoram
of servers will be available in cluster. Otherwise shutting down is fine.I don't think retrying
silently from BKJM layer is correct. If other servers available in cluster still your write
can suceed with other servers by reforming ensemble.
                
> BookKeeper Journal Manager is not retrying to connect to BK when BookKeeper is not available
for write.
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-3392
>                 URL: https://issues.apache.org/jira/browse/HDFS-3392
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: surendra singh lilhore
>
> Scenario:
> 1. Start 3 bookKeeper and 3 zookeeper.
> 2. Start one NN as active & second NN as standby.
> 3. Write some file.
> 4. Stop all BookKeepers.
> Issue:
> Bookkeeper Journal Manager is not retrying to connect to BK when Bookkeeper is not available
for write and Active namenode is shutdown.

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

        

Mime
View raw message