[
https://issues.apache.org/jira/browse/HBASE-16115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357673#comment-15357673
]
Enis Soztutar commented on HBASE-16115:
---------------------------------------
So the plan is to have PHOENIX-3037 as a short term solution, and do
HBASE-16141 for long term? Sounds logical.
bq. I think that using an alternate mechanism for conveying that caller context
would avoid conflicting with the current user and possibly be more consistent
with the RpcCallContext.
The problem of RpcCallContext based user passing and authorization is that, as
can be seen from HBASE-14475, we get the compaction / split request from RPC
threads, add the request to the queue, and only call preCompact() from the
background thread which executes the compaction. There is no more
RpcCallContext there. As of now, since AC is a coprocessor and not a core
concept, the only way to enforce proper authorization and pass the information
about the User context is doAs().
> Missing security context in RegionObserver coprocessor when a
> compaction/split is triggered manually
> ----------------------------------------------------------------------------------------------------
>
> 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)
