hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elliott Clark (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-12199) Make TestAtomicOperation and TestEncodedSeekers faster
Date Wed, 08 Oct 2014 15:52:34 GMT

     [ https://issues.apache.org/jira/browse/HBASE-12199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Elliott Clark updated HBASE-12199:
----------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 1.0.0)
                   0.99.1
                   2.0.0
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

Pushed to branch-1+
Thanks

> 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.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)

Mime
View raw message