[jira] [Created] (HDFS-5835) Add a new option for starting standby NN when rolling upgrade is in progress

2014-01-26 Thread Tsz Wo (Nicholas), SZE (JIRA)
Tsz Wo (Nicholas), SZE created HDFS-5835:


 Summary: Add a new option for starting standby NN when rolling 
upgrade is in progress
 Key: HDFS-5835
 URL: https://issues.apache.org/jira/browse/HDFS-5835
 Project: Hadoop HDFS
  Issue Type: Sub-task
  Components: namenode
Reporter: Tsz Wo (Nicholas), SZE
Assignee: Tsz Wo (Nicholas), SZE


When rolling upgrade is already in-progress and the standby NN is not yet 
started up, a new startup option is needed for the standby NN to initialize the 
upgrade status.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)


[jira] [Created] (HDFS-5834) TestCheckpoint#testCheckpoint may fail due to Bad value assertion

2014-01-26 Thread Ted Yu (JIRA)
Ted Yu created HDFS-5834:


 Summary: TestCheckpoint#testCheckpoint may fail due to Bad value 
assertion
 Key: HDFS-5834
 URL: https://issues.apache.org/jira/browse/HDFS-5834
 Project: Hadoop HDFS
  Issue Type: Test
Reporter: Ted Yu
Priority: Minor


I saw the following when running test suite on Linux:
{code}
testCheckpoint(org.apache.hadoop.hdfs.server.namenode.TestCheckpoint)  Time 
elapsed: 3.058 sec  <<< FAILURE!
java.lang.AssertionError: Bad value for metric GetImageNumOps
Expected: gt(0)
 got: <0L>

at org.junit.Assert.assertThat(Assert.java:780)
at 
org.apache.hadoop.test.MetricsAsserts.assertCounterGt(MetricsAsserts.java:318)
at 
org.apache.hadoop.hdfs.server.namenode.TestCheckpoint.testCheckpoint(TestCheckpoint.java:1058)
{code}



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)


[jira] [Created] (HDFS-5833) SecondaryNameNode have a incorrect java doc

2014-01-26 Thread Bangtao Zhou (JIRA)
Bangtao Zhou created HDFS-5833:
--

 Summary: SecondaryNameNode have a incorrect java doc
 Key: HDFS-5833
 URL: https://issues.apache.org/jira/browse/HDFS-5833
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: namenode
Affects Versions: trunk-win
Reporter: Bangtao Zhou
Priority: Trivial


SecondaryNameNode has a incorrect java doc, actually the SecondaryNameNode uses 
the *NamenodeProtocol* to talk to the primary NameNode, not the *ClientProtocol*



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)