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 283DE4865 for ; Wed, 29 Jun 2011 04:44:24 +0000 (UTC) Received: (qmail 11220 invoked by uid 500); 29 Jun 2011 04:44:19 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 11051 invoked by uid 500); 29 Jun 2011 04:44:02 -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 11020 invoked by uid 99); 29 Jun 2011 04:43:51 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Jun 2011 04:43:51 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Jun 2011 04:43:48 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 629F84380EA for ; Wed, 29 Jun 2011 04:43:28 +0000 (UTC) Date: Wed, 29 Jun 2011 04:43:28 +0000 (UTC) From: "stack (JIRA)" To: issues@hbase.apache.org Message-ID: <421210141.1134.1309322608385.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Created] (HBASE-4042) TestDistributedLogSplitting broke on trunk MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 TestDistributedLogSplitting broke on trunk ------------------------------------------ Key: HBASE-4042 URL: https://issues.apache.org/jira/browse/HBASE-4042 Project: HBase Issue Type: Bug Reporter: stack There's a couple of issues going on here. Its taken me a while to figure whats up and am still not done. Here's what I found so far: + The last test testWorkerAbort has been hanging because there is no one to process the log split the final assert is expecting completed; we've killed the lone RS that this test put up. This test passes most of the time for me locally; luck has the log processed before the RS with its splitLogWorker processes the log before we go out. Putting up a new RS with a splitLogWorker makes this test pass for me most of the time now but I've seen an error in testing so need to dig in still. + The first test, testThreeRSAbort is a good test. Its turning up a issue that has nothing to do w/ log splitting. If .META. is on one of the RSs that goes down -- we launch w/ 6 RSs -- then we get stuck in catalog tracker waiting on meta to be up again (though it deploys fin -- we don't notice its deploy in master). I'm on this one at mo. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira