Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sun, 26 Jun 2016 05:46:51 +0000 (UTC)
From: "Lars Hofhansl (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12983200.1466916742000.2064.1466920011306@Atlassian.JIRA>
In-Reply-To: <JIRA.12983200.1466916742000@Atlassian.JIRA>
References: <JIRA.12983200.1466916742000@Atlassian.JIRA> <JIRA.12983200.1466916742277@arcas>
Subject: [jira] [Commented] (HBASE-16115) Missing security context in
 RegionObserver coprocessor when a compaction is triggered through the UI
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sun, 26 Jun 2016 05:46:53 -0000


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

Lars Hofhansl commented on HBASE-16115:
---------------------------------------

Note, in this we managed to trigger the compaction, but the coprocessor hook triggered by the compaction has no credentials to access other HBase table (when triggered through the UI)

> Missing security context in RegionObserver coprocessor when a compaction is triggered through the UI
> ----------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-16115
>                 URL: https://issues.apache.org/jira/browse/HBASE-16115
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.98.20
>            Reporter: Lars Hofhansl
>
> We ran into an interesting phenomenon which can easily render a cluster unusable.
> We loaded some tests data into a test table and forced a manual compaction through the UI. We have some compaction hooks implemented in a region observer, which writes back to another HBase table when the compaction finishes. We noticed that this coprocessor is not setup correctly, it seems the security context is missing.
> The interesting part is that this _only_ happens when the compaction is triggere through the UI. Automatic compactions (major or minor) or when triggered via the HBase shell (folling a kinit) work fine. Only the UI-triggered compactions cause this issues and lead to essentially neverending compactions, immovable regions, etc.
> Not sure what exactly the issue is, but I wanted to make sure I capture this.
> [~apurtell], [~ghelmling], FYI.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)