[
https://issues.apache.org/jira/browse/HDFS-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13277699#comment-13277699
]
Uma Maheswara Rao G commented on HDFS-3392:
-------------------------------------------
IMHO, If there is no BK cluster running, NN should shutdown.
Marking it as Invalid.
@Surendra, If you feel, it should behave differently, feel free to reopen and
provide your expectation.
> 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: Sub-task
> 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
