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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.98.14, 1.0.2, 1.2.0, 1.1.2, 1.3.0, 2.0.0
• Component/s: regionserver
• Hadoop Flags: Reviewed
• Release Note: Promotes an -ea assert to logged FATAL and RS abort when memstore is found to be in an inconsistent state.
• Assignee: Nick Dimiduk
• Reporter: Devaraj Das
• Created: 26/Mar/14 22:23
• Updated: 31/Aug/15 22:39
• Resolved: 14/Aug/15 23:07

Description

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.