Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1DBE1DD9E for ; Tue, 19 Mar 2013 03:51:21 +0000 (UTC) Received: (qmail 58498 invoked by uid 500); 19 Mar 2013 03:51:17 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 58065 invoked by uid 500); 19 Mar 2013 03:51:16 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 58034 invoked by uid 99); 19 Mar 2013 03:51:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Mar 2013 03:51:16 +0000 Date: Tue, 19 Mar 2013 03:51:16 +0000 (UTC) From: "Hadoop QA (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-8142) Sporadic TestZKProcedureControllers failures on trunk MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-8142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13606019#comment-13606019 ] Hadoop QA commented on HBASE-8142: ---------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12574296/hase-8142_v1.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. {color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop 2.0 profile. {color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 1.3.9) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 lineLengths{color}. The patch does not introduce lines longer than 100 {color:red}-1 site{color}. The patch appears to cause mvn site goal to fail. {color:green}+1 core tests{color}. The patch passed unit tests in . Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/4882//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/4882//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/4882//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/4882//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/4882//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/4882//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/4882//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/4882//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/4882//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/4882//console This message is automatically generated. > Sporadic TestZKProcedureControllers failures on trunk > ----------------------------------------------------- > > Key: HBASE-8142 > URL: https://issues.apache.org/jira/browse/HBASE-8142 > Project: HBase > Issue Type: Bug > Reporter: stack > Assignee: Jeffrey Zhong > Fix For: 0.95.0, 0.98.0 > > Attachments: hase-8142_v1.patch > > > See https://builds.apache.org/job/PreCommit-HBASE-Build/4865//artifact/trunk/hbase-server/target/surefire-reports/org.apache.hadoop.hbase.procedure.TestZKProcedureControllers.txt and > https://builds.apache.org/job/PreCommit-HBASE-Build/4865//artifact/trunk/hbase-server/target/surefire-reports/org.apache.hadoop.hbase.procedure.TestZKProcedureControllers-output.txt > I see this in the output: > {code} > 2013-03-18 17:30:46,672 DEBUG [Thread-2-EventThread] zookeeper.ZKUtil(1682): testing utility-0x13d7e8da7590000 Retrieved 0 byte(s) of data from znode /hbase/testSimple/acquired/instanceTest; data=empty > 2013-03-18 17:30:46,672 DEBUG [Thread-2-EventThread] procedure.ZKProcedureMemberRpcs(206): start proc data length is 0 > 2013-03-18 17:30:46,672 ERROR [Thread-2-EventThread] procedure.ZKProcedureMemberRpcs(210): Data in for starting procuedure instanceTest is illegally formatted. Killing the procedure. > 2013-03-18 17:30:46,673 ERROR [Thread-2-EventThread] procedure.ZKProcedureMemberRpcs(218): Illegal argument exception > java.lang.IllegalArgumentException: Data in for starting procuedure instanceTest is illegally formatted. Killing the procedure. > at org.apache.hadoop.hbase.procedure.ZKProcedureMemberRpcs.startNewSubprocedure(ZKProcedureMemberRpcs.java:211) > at org.apache.hadoop.hbase.procedure.ZKProcedureMemberRpcs.waitForNewProcedures(ZKProcedureMemberRpcs.java:175) > at org.apache.hadoop.hbase.procedure.ZKProcedureMemberRpcs.access$100(ZKProcedureMemberRpcs.java:56) > at org.apache.hadoop.hbase.procedure.ZKProcedureMemberRpcs$1.nodeChildrenChanged(ZKProcedureMemberRpcs.java:109) > at org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher.process(ZooKeeperWatcher.java:312) > at org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:519) > at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:495) > 2013-03-18 17:30:46,675 ERROR [Thread-2-EventThread] procedure.ZKProcedureMemberRpcs(281): Failed due to null subprocedure > java.lang.IllegalArgumentException via expected:java.lang.IllegalArgumentException: Data in for starting procuedure instanceTest is illegally formatted. Killing the procedure. > at org.apache.hadoop.hbase.procedure.ZKProcedureMemberRpcs.startNewSubprocedure(ZKProcedureMemberRpcs.java:219) > at org.apache.hadoop.hbase.procedure.ZKProcedureMemberRpcs.waitForNewProcedures(ZKProcedureMemberRpcs.java:175) > at org.apache.hadoop.hbase.procedure.ZKProcedureMemberRpcs.access$100(ZKProcedureMemberRpcs.java:56) > at org.apache.hadoop.hbase.procedure.ZKProcedureMemberRpcs$1.nodeChildrenChanged(ZKProcedureMemberRpcs.java:109) > at org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher.process(ZooKeeperWatcher.java:312) > at org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:519) > at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:495) > Caused by: java.lang.IllegalArgumentException: Data in for starting procuedure instanceTest is illegally formatted. Killing the procedure. > at org.apache.hadoop.hbase.procedure.ZKProcedureMemberRpcs.startNewSubprocedure(ZKProcedureMemberRpcs.java:211) > ... 6 more > {code} > The znode has zero data (Usually it has 7 bytes when test runs fine). Is the latch being triggered on node create before data is written? Pointers appreciated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira