You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Manukranth Kolloju (JIRA)" <ji...@apache.org> on 2014/10/08 01:20:35 UTC
[jira] [Updated] (HBASE-12199) Make TestAtomicOperation faster
[ https://issues.apache.org/jira/browse/HBASE-12199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manukranth Kolloju updated HBASE-12199:
---------------------------------------
Status: Patch Available (was: Open)
> Make TestAtomicOperation 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: 1.0.0
>
>
> 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)