[AMBARI-11501] AMS HBase does not start after Kerberization in distributed mode

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1.0
• Fix Version/s: 2.1.0
• Component/s: ambari-server
• Assignee: Siddharth Wagle
• Reporter: Siddharth Wagle
• Created: 28/May/15 19:01
• Updated: 03/Jun/15 08:08
• Resolved: 28/May/15 22:46

Description

AMS on distributed creates this directory with user AMS at startup
In Ambari Metrics Server Stack the staging directory is hard coded params.py:hbase_staging_dir = "/apps/hbase/staging”
And created at startup of AMS-hbase,
if params.is_hbase_distributed:

params.HdfsDirectory(params.hbase_staging_dir,
action="create_delayed",
owner=params.hbase_user,
mode=0711
)

Which means there is a staging directory /apps/hbase/staging with owner ams (should be owner hbase )
This does not seem to matter before Kerberization but after kerberization Hbase Regionservers check the directory owner and fails at startup.