hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16115) Missing security context in RegionObserver coprocessor when a compaction/split is triggered manually
Date Wed, 29 Jun 2016 01:02:10 GMT

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

Lars Hofhansl commented on HBASE-16115:

What we've seen is that with a manual compaction the request comes in from the master, so
as a user on the master machine. With this patch it then passes that user through to any action
performed inside the compaction, which is - I think - not correct.

The Phoenix coprocessor is not doing anything special, it uses the HBase tooling to write
some data to another table when the compaction is finished. It shouldn't have to do anything
specific, it should authenticated as the proper user on the local machine, no?

> Missing security context in RegionObserver coprocessor when a compaction/split is triggered
> ----------------------------------------------------------------------------------------------------
>                 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

View raw message