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

Enis Soztutar commented on HBASE-16115:
---------------------------------------

bq. When I talked about the issue we earlier faced, the way we fixed was to 
simply run everything in the compaction as the login user (which is hbase 
regionserver user), but we somehow thought that HBASE-14655 would fix it in the 
long run, but let me check that hypothesis...
Good catch. I think HBASE-14655 is the right fix in HBase because the 
coprocessor should run with the user context (for security). In Phoenix (or any 
other coprocessor) that wants to do RPC to another region server though, that 
has to be performed as the login user context. So we need a fix in Phoenix to 
switch back to the login context? 

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

Reply via email to