[ https://issues.apache.org/jira/browse/HBASE-12199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14164206#comment-14164206 ]
Hudson commented on HBASE-12199: -------------------------------- FAILURE: Integrated in HBase-0.98-on-Hadoop-1.1 #554 (See [https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/554/]) HBASE-12199 Make TestAtomicOperation and TestEncodedSeekers faster (apurtell: rev be64e4892f1b59da96be2c556200bf974d797b60) * hbase-server/src/test/java/org/apache/hadoop/hbase/io/encoding/TestEncodedSeekers.java * hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestAtomicOperation.java > Make TestAtomicOperation and TestEncodedSeekers faster > ------------------------------------------------------ > > Key: HBASE-12199 > URL: https://issues.apache.org/jira/browse/HBASE-12199 > Project: HBase > Issue Type: Bug > Components: test > Affects Versions: 1.0.0 > Reporter: Manukranth Kolloju > Assignee: Manukranth Kolloju > Priority: Trivial > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: 0001-Fix-TestAtomicOperation.patch, > 0001-INTERNAL-Fix-TestAtomicOperation.patch > > > TestAtomicOperation has a bunch of tests which spawn a bunch of tests that do > puts, appends, deletes, inc and then does gets to make sure that things > happened. It uses TEST_UTIL.getLocalHRegion() to obtain an HRegion object. > So, in essence the test doesn't need to sync to disk to make sure the edits > have persisted. There is no regionserver/master to take care of wal replay or > any failure for that matter. So, converting all the Durability settings for > the edits to ASYNC_WAL seems like the right thing to do here to make the test > run faster. -- This message was sent by Atlassian JIRA (v6.3.4#6332)