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 3C96B18FE3 for ; Fri, 11 Sep 2015 18:59:46 +0000 (UTC) Received: (qmail 31763 invoked by uid 500); 11 Sep 2015 18:59:46 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 31719 invoked by uid 500); 11 Sep 2015 18:59:45 -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 31704 invoked by uid 99); 11 Sep 2015 18:59:45 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Sep 2015 18:59:45 +0000 Date: Fri, 11 Sep 2015 18:59:45 +0000 (UTC) From: "Yu Li (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-14411) Fix UT failures when using multiwal as default provider 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-14411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Li updated HBASE-14411: -------------------------- Description: If we set hbase.wal.provider to multiwal in hbase-server/src/test/resources/hbase-site.xml which allows us to use BoundedRegionGroupingProvider in UT, we will observe below failures in current code base: {noformat} Failed tests: TestHLogRecordReader>TestWALRecordReader.testPartialRead:164 expected:<1> but was:<2> TestHLogRecordReader>TestWALRecordReader.testWALRecordReader:216 expected:<2> but was:<3> TestWALRecordReader.testPartialRead:164 expected:<1> but was:<2> TestWALRecordReader.testWALRecordReader:216 expected:<2> but was:<3> TestDistributedLogSplitting.testRecoveredEdits:276 edits dir should have more than a single file in it. instead has 1 TestAtomicOperation.testMultiRowMutationMultiThreads:499 expected:<0> but was:<1> TestHRegionServerBulkLoad.testAtomicBulkLoad:307 Expected: is but: was TestLogRolling.testCompactionRecordDoesntBlockRolling:611 Should have WAL; one table is not flushed expected:<1> but was:<0> TestLogRolling.testLogRollOnDatanodeDeath:359 null TestLogRolling.testLogRollOnPipelineRestart:472 Missing datanode should've triggered a log roll TestReplicationSourceManager.testLogRoll:237 expected:<6> but was:<7> TestReplicationWALReaderManager.test:155 null TestReplicationWALReaderManager.test:155 null TestReplicationWALReaderManager.test:155 null TestReplicationWALReaderManager.test:155 null TestReplicationWALReaderManager.test:155 null TestReplicationWALReaderManager.test:155 null TestReplicationWALReaderManager.test:155 null TestReplicationWALReaderManager.test:155 null TestWALSplit.testCorruptedLogFilesSkipErrorsFalseDoesNotTouchLogs:594 if skip.errors is false all files should remain in place expected:<11> but was:<12> TestWALSplit.testLogsGetArchivedAfterSplit:649 wrong number of files in the archive log expected:<11> but was:<12> TestWALSplit.testMovedWALDuringRecovery:810->retryOverHdfsProblem:793 expected:<11> but was:<12> TestWALSplit.testRetryOpenDuringRecovery:838->retryOverHdfsProblem:793 expected:<11> but was:<12> TestWALSplitCompressed>TestWALSplit.testCorruptedLogFilesSkipErrorsFalseDoesNotTouchLogs:594 if skip.errors is false all files should remain in place expected:<11> but was:<12> TestWALSplitCompressed>TestWALSplit.testLogsGetArchivedAfterSplit:649 wrong number of files in the archive log expected:<11> but was:<12> TestWALSplitCompressed>TestWALSplit.testMovedWALDuringRecovery:810->TestWALSplit.retryOverHdfsProblem:793 expected:<11> but was:<12> TestWALSplitCompressed>TestWALSplit.testRetryOpenDuringRecovery:838->TestWALSplit.retryOverHdfsProblem:793 expected:<11> but was:<12> {noformat} While patch for HBASE-14306 could resolve failures of TestHLogRecordReader, TestReplicationSourceManager and TestReplicationWALReaderManager, this JIRA will focus on resolving the others was: If we set hbase.wal.provider to multiwal in hbase-server/src/test/resources/hbase-site.xml which allows us to use BoundedRegionGroupingProvider in UT, we will observe below failures in current code base: {noformat} Failed tests: TestHLogRecordReader>TestWALRecordReader.testPartialRead:164 expected:<1> but was:<2> TestHLogRecordReader>TestWALRecordReader.testWALRecordReader:216 expected:<2> but was:<3> TestWALRecordReader.testPartialRead:164 expected:<1> but was:<2> TestWALRecordReader.testWALRecordReader:216 expected:<2> but was:<3> TestDistributedLogSplitting.testRecoveredEdits:276 edits dir should have more than a single file in it. instead has 1 TestAtomicOperation.testMultiRowMutationMultiThreads:499 expected:<0> but was:<1> TestHRegionServerBulkLoad.testAtomicBulkLoad:307 Expected: is but: was TestLogRolling.testCompactionRecordDoesntBlockRolling:611 Should have WAL; one table is not flushed expected:<1> but was:<0> TestLogRolling.testLogRollOnDatanodeDeath:359 null TestLogRolling.testLogRollOnPipelineRestart:472 Missing datanode should've triggered a log roll TestReplicationSourceManager.testLogRoll:237 expected:<6> but was:<7> TestReplicationWALReaderManager.test:155 null TestReplicationWALReaderManager.test:155 null TestReplicationWALReaderManager.test:155 null TestReplicationWALReaderManager.test:155 null TestReplicationWALReaderManager.test:155 null TestReplicationWALReaderManager.test:155 null TestReplicationWALReaderManager.test:155 null TestReplicationWALReaderManager.test:155 null TestWALSplit.testCorruptedLogFilesSkipErrorsFalseDoesNotTouchLogs:594 if skip.errors is false all files should remain in place expected:<11> but was:<12> TestWALSplit.testLogsGetArchivedAfterSplit:649 wrong number of files in the archive log expected:<11> but was:<12> TestWALSplit.testMovedWALDuringRecovery:810->retryOverHdfsProblem:793 expected:<11> but was:<12> TestWALSplit.testRetryOpenDuringRecovery:838->retryOverHdfsProblem:793 expected:<11> but was:<12> TestWALSplitCompressed>TestWALSplit.testCorruptedLogFilesSkipErrorsFalseDoesNotTouchLogs:594 if skip.errors is false all files should remain in place expected:<11> but was:<12> TestWALSplitCompressed>TestWALSplit.testLogsGetArchivedAfterSplit:649 wrong number of files in the archive log expected:<11> but was:<12> TestWALSplitCompressed>TestWALSplit.testMovedWALDuringRecovery:810->TestWALSplit.retryOverHdfsProblem:793 expected:<11> but was:<12> TestWALSplitCompressed>TestWALSplit.testRetryOpenDuringRecovery:838->TestWALSplit.retryOverHdfsProblem:793 expected:<11> but was:<12> {noformat} While patch for HBASE-14306 could resolve failures of TestHLogRecordReader, TestReplicationSourceManager and TestReplicationWALReaderManager, this JIRA will focus of resolving the others > Fix UT failures when using multiwal as default provider > ------------------------------------------------------- > > Key: HBASE-14411 > URL: https://issues.apache.org/jira/browse/HBASE-14411 > Project: HBase > Issue Type: Bug > Reporter: Yu Li > Assignee: Yu Li > Fix For: 2.0.0 > > > If we set hbase.wal.provider to multiwal in hbase-server/src/test/resources/hbase-site.xml which allows us to use BoundedRegionGroupingProvider in UT, we will observe below failures in current code base: > {noformat} > Failed tests: > TestHLogRecordReader>TestWALRecordReader.testPartialRead:164 expected:<1> but was:<2> > TestHLogRecordReader>TestWALRecordReader.testWALRecordReader:216 expected:<2> but was:<3> > TestWALRecordReader.testPartialRead:164 expected:<1> but was:<2> > TestWALRecordReader.testWALRecordReader:216 expected:<2> but was:<3> > TestDistributedLogSplitting.testRecoveredEdits:276 edits dir should have more than a single file in it. instead has 1 > TestAtomicOperation.testMultiRowMutationMultiThreads:499 expected:<0> but was:<1> > TestHRegionServerBulkLoad.testAtomicBulkLoad:307 > Expected: is > but: was > TestLogRolling.testCompactionRecordDoesntBlockRolling:611 Should have WAL; one table is not flushed expected:<1> but was:<0> > TestLogRolling.testLogRollOnDatanodeDeath:359 null > TestLogRolling.testLogRollOnPipelineRestart:472 Missing datanode should've triggered a log roll > TestReplicationSourceManager.testLogRoll:237 expected:<6> but was:<7> > TestReplicationWALReaderManager.test:155 null > TestReplicationWALReaderManager.test:155 null > TestReplicationWALReaderManager.test:155 null > TestReplicationWALReaderManager.test:155 null > TestReplicationWALReaderManager.test:155 null > TestReplicationWALReaderManager.test:155 null > TestReplicationWALReaderManager.test:155 null > TestReplicationWALReaderManager.test:155 null > TestWALSplit.testCorruptedLogFilesSkipErrorsFalseDoesNotTouchLogs:594 if skip.errors is false all files should remain in place expected:<11> but was:<12> > TestWALSplit.testLogsGetArchivedAfterSplit:649 wrong number of files in the archive log expected:<11> but was:<12> > TestWALSplit.testMovedWALDuringRecovery:810->retryOverHdfsProblem:793 expected:<11> but was:<12> > TestWALSplit.testRetryOpenDuringRecovery:838->retryOverHdfsProblem:793 expected:<11> but was:<12> > TestWALSplitCompressed>TestWALSplit.testCorruptedLogFilesSkipErrorsFalseDoesNotTouchLogs:594 if skip.errors is false all files should remain in place expected:<11> but was:<12> > TestWALSplitCompressed>TestWALSplit.testLogsGetArchivedAfterSplit:649 wrong number of files in the archive log expected:<11> but was:<12> > TestWALSplitCompressed>TestWALSplit.testMovedWALDuringRecovery:810->TestWALSplit.retryOverHdfsProblem:793 expected:<11> but was:<12> > TestWALSplitCompressed>TestWALSplit.testRetryOpenDuringRecovery:838->TestWALSplit.retryOverHdfsProblem:793 expected:<11> but was:<12> > {noformat} > While patch for HBASE-14306 could resolve failures of TestHLogRecordReader, TestReplicationSourceManager and TestReplicationWALReaderManager, this JIRA will focus on resolving the others -- This message was sent by Atlassian JIRA (v6.3.4#6332)