[
https://issues.apache.org/jira/browse/HBASE-4803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-4803.
--------------------------
Resolution: Implemented
This patch is no longer relevant. The code it effects has been changed under
it in particular by:
{code}
Author: Lars Hofhansl <[email protected]> 2012-03-22 10:49:32
Committer: Lars Hofhansl <[email protected]> 2012-03-22 10:49:32
Parent: cff5945609e95b06d6e832007da5972dac432702 (HBASE-5328 Small changes to
Master to make it more testable)
Child: 0741c69a9ef833c7c3b4aa87c1355558c10df6a1 (HBASE-5542 Unify
HRegion.mutateRowsWithLocks() and HRegion.processRow() (Scott Chen) part 2)
Branches: 6060_santander, 6060_smallpatch.txt, 6299, 6698, checksums, ram,
ram2, remotes/origin/instant_schema_alter, remotes/origin/trunk, testing, x
Follows:
Precedes:
HBASE-5542 Unify HRegion.mutateRowsWithLocks() and HRegion.processRow()
(Scott Chen)
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1303915
13f79535-47bb-0310-9956-ffa450edef68
{code}
The above commit also seems to catch most of the sentiment behind this patch;
testing exitWorker status in loop tests to see if we should continue or not.
Resolving as Implemented.
> Split log worker should terminate properly when waiting for znode
> -----------------------------------------------------------------
>
> Key: HBASE-4803
> URL: https://issues.apache.org/jira/browse/HBASE-4803
> Project: HBase
> Issue Type: Bug
> Reporter: Nicolas Spiegelberg
> Assignee: Prakash Khemani
> Priority: Minor
> Fix For: 0.96.0
>
> Attachments: HBASE-4803.patch
>
>
> This is an attempt to fix the fact that SplitLogWorker threads were not being
> terminated properly in some multi-master unit tests.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
