Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 11 Aug 2015 22:17:45 +0000 (UTC)
From: "Nick Dimiduk (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12703844.1395872618000.38101.1439331465727@Atlassian.JIRA>
In-Reply-To: <JIRA.12703844.1395872618000@Atlassian.JIRA>
References: <JIRA.12703844.1395872618000@Atlassian.JIRA>
 <JIRA.12703844.1395872618525@arcas>
Subject: [jira] [Commented] (HBASE-10844) Coprocessor failure during
 batchmutation leaves the memstore datastructs in an inconsistent state
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-10844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14692366#comment-14692366 ] 

Nick Dimiduk commented on HBASE-10844:
--------------------------------------

I should say -- replaces the WARN with an abort(), which is what the assert would do anyway.

FWIW, we were seeing this WARN triggered during region close.

> 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
>
>
> 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)