[HBASE-16115] Missing security context in RegionObserver coprocessor when a compaction/split is triggered manually

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 0.98.20
• Assignee: Unassigned
• Reporter: Lars Hofhansl
• Created: 26/Jun/16 04:52
• Updated: 12/Dec/16 18:45
• Resolved: 12/Dec/16 18:45

Description

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.

Issue Links

• is related to: PHOENIX-3037 Setup proper security context in compaction/split coprocessor hooks
• is related to: HBASE-16141 Unwind use of UserGroupInformation.doAs() to convey requester identity in coprocessor upcalls