[
https://issues.apache.org/jira/browse/HBASE-10844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated HBASE-10844:
---------------------------------
Attachment: HBASE-10844.02-0.98.patch
HBASE-10844.02-branch-1.0.patch
HBASE-10844.02.patch
Cleaned up patch for master. HBASE-10844.02.patch compiles for master,
branch-1, branch-1.2, branch-1.1. Patch from master does not cherry-pick
cleanly any further back, so branches branch-1.0 and 0.98 get their own
patches. Just accounting for minor fuzz in the assert line.
> Coprocessor failure during batchmutation leaves the memstore datastructs in
> an inconsistent state
> -------------------------------------------------------------------------------------------------
>
> Key: HBASE-10844
> URL: https://issues.apache.org/jira/browse/HBASE-10844
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Reporter: Devaraj Das
> Assignee: Devaraj Das
> Attachments: 10844-1-0.98.txt, 10844-1.txt, 10844-v2.patch,
> HBASE-10844.02-0.98.patch, HBASE-10844.02-branch-1.0.patch,
> HBASE-10844.02.patch
>
>
> Observed this in the testing with Phoenix. The test in Phoenix -
> MutableIndexFailureIT deliberately fails the batchmutation call via the
> installed coprocessor. But the update is not rolled back. That leaves the
> memstore inconsistent. In particular, I observed that getFlushableSize is
> updated before the coprocessor was called but the update is not rolled back.
> When the region is being closed at some later point, the assert introduced in
> HBASE-10514 in the HRegion.doClose() causes the RegionServer to shutdown
> abnormally.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
