[
https://issues.apache.org/jira/browse/HBASE-12199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14162788#comment-14162788
]
Manukranth Kolloju commented on HBASE-12199:
--------------------------------------------
[~stack], I should have bunched the first 2(TestEncodedSeekers,
TestCacheOnWrite) together. The third one(TestAtomicOperation) didn't belong to
the first 2 patches because it was slightly unclear. When I fixed
TestCacheOnWrite(and put up the jira) and ran the tests, I found
TestEncodedSeekers and TestAtomicOperation as hanging tests. So, I fixed them
and put up jiras for them. I would have put all of them up if they all
manifested together in the first go. Or I could have been more patient, my bad
:)
> 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
>
> Attachments: 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)
