Long time fail over when using QJM

2013-08-29 Thread Mickey
Hi, all I tried to test the QJM HA and it always works good. But, yestoday I met an quite long time fail over with QJM. The test is base on the CDH4.3.0. The attachment is the standby namenode and the journalnode 's logs. The network cable on active namenode(also a datanode) was pulled out at

Build failed in Jenkins: Hadoop-Hdfs-0.23-Build #714

2013-08-29 Thread Apache Jenkins Server
See https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/714/changes Changes: [tgraves] YARN-1101. Active nodes can be decremented below 0 (Robert Parker via tgraves) -- [...truncated 7673 lines...] [ERROR] location: package com.google.protobuf [ERROR]

Hadoop-Hdfs-0.23-Build - Build # 714 - Still Failing

2013-08-29 Thread Apache Jenkins Server
See https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/714/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 7866 lines...] [ERROR]

Re: Long time fail over when using QJM

2013-08-29 Thread Todd Lipcon
If you're seeing those log messages, the SBN was already active at that time. It only logs that message when successfully writing transactions. So, the failover must have already completed before the logs you're looking at. -Todd On Thu, Aug 29, 2013 at 1:18 AM, Mickey huanfeng...@gmail.com

[jira] [Resolved] (HDFS-5142) Namenode crashes with NPE in ReplicationMonitor

2013-08-29 Thread Kihwal Lee (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-5142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee resolved HDFS-5142. -- Resolution: Duplicate Ahhh. I thought it looked familiar. I did even commented on HDFS-4482.

[jira] [Created] (HDFS-5144) Document time unit to NameNodeMetrics.java

2013-08-29 Thread Akira AJISAKA (JIRA)
Akira AJISAKA created HDFS-5144: --- Summary: Document time unit to NameNodeMetrics.java Key: HDFS-5144 URL: https://issues.apache.org/jira/browse/HDFS-5144 Project: Hadoop HDFS Issue Type:

Re: Long time fail over when using QJM

2013-08-29 Thread Mickey
2013/8/30 Todd Lipcon t...@cloudera.com If you're seeing those log messages, the SBN was already active at that time. It only logs that message when successfully writing transactions. So, the failover must have already completed before the logs you're looking at. -Todd On Thu, Aug 29, 2013