You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "Devaraj Das (JIRA)" <ji...@apache.org> on 2014/03/26 23:24:22 UTC

[jira] [Created] (HBASE-10844) Coprocessor failure during batchmutation leaves the memstore datastructs in an inconsistent state

Devaraj Das created HBASE-10844:
-----------------------------------

             Summary: 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
             Fix For: 0.98.2


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.2#6252)