ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-11501) AMS HBase does not start after Kerberization in distributed mode
Date Thu, 28 May 2015 23:30:17 GMT

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

Hadoop QA commented on AMBARI-11501:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12735954/AMBARI-11501.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/2912//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/2912//console

This message is automatically generated.

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

Mime
View raw message