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] [Updated] (HDFS-3392) BookKeeper Journal Manager is not retrying to connect to BK when BookKeeper is not available for write.
Date Thu, 10 May 2012 17:30:50 GMT

     [ https://issues.apache.org/jira/browse/HDFS-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Uma Maheswara Rao G updated HDFS-3392:
--------------------------------------

    Issue Type: Sub-task  (was: Bug)
        Parent: HDFS-3399
    
> 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

        

Mime
View raw message