[
https://issues.apache.org/jira/browse/AMBARI-11501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Wagle updated AMBARI-11501:
-------------------------------------
Summary: AMS HBase does not start after Kerberization in distributed mode
(was: AMS HBase does not start after Kerberization)
> AMS HBase does not start after Kerberization in distributed mode
> ----------------------------------------------------------------
>
> Key: AMBARI-11501
> URL: https://issues.apache.org/jira/browse/AMBARI-11501
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Siddharth Wagle
> Assignee: Siddharth Wagle
> Fix For: 2.1.0
>
> Attachments: AMBARI-11501.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
