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

Andrew Purtell commented on HBASE-16115:
----------------------------------------

I'm glad you guys figured out the interesting detail was use of the UI, because 
I was still at a loss after staring at the code for a while yesterday 
afternoon. 

It's plausable the contexts set up by Jetty when serving UI requests might not 
be logged in (we're not using authentication filters which would do that, 
albeit with the client credentials), and if so this was bound to cause problems 
sooner or later. We see it here because for the first time something is trying 
to issue a remote RPC when servicing the compaction request. 

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

Reply via email to