Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Date: Wed, 9 May 2012 05:45:35 +0000 (UTC)
From: "surendra singh lilhore (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: 
 <795895259.42704.1336542335646.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (HDFS-3392) BookKeeper Journal Manager is not
 retrying to connect to BK when BookKeeper is not available for write.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

surendra singh lilhore created HDFS-3392:
--------------------------------------------

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