[
https://issues.apache.org/jira/browse/HBASE-10844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698102#comment-14698102
]
Hudson commented on HBASE-10844:
--------------------------------
FAILURE: Integrated in HBase-1.2 #112 (See
[https://builds.apache.org/job/HBase-1.2/112/])
HBASE-10844 Coprocessor failure during batchmutation leaves the memstore
datastructs in an inconsistent state (apurtell: rev
adcb905a0d30bdd27aa7439e336e0cf95f6dbae9)
* hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
> 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: Nick Dimiduk
> Fix For: 2.0.0, 0.98.14, 1.0.2, 1.2.0, 1.3.0, 1.1.3
>
> 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)
