You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2015/12/12 06:47:46 UTC

[jira] [Commented] (AMBARI-14350) AMS does not start up after cluster redeploy because of invalid ownership of its directories.

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

Hadoop QA commented on AMBARI-14350:
------------------------------------

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

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

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified test files.

    {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/4576//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/4576//console

This message is automatically generated.

> AMS does not start up after cluster redeploy because of invalid ownership of its directories.
> ---------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-14350
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14350
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.2.0
>            Reporter: Aravindan Vijayan
>            Assignee: Aravindan Vijayan
>            Priority: Critical
>             Fix For: 2.2.0
>
>         Attachments: AMBARI-14350.patch
>
>
> PROBLEM
> Steps:
> Deployed cluster via blueprints.
> Reset cluster (reset ambari-server, host cleanup).
> Deployed cluster via UI.
> Result: Ambari Metrics Service go down.
> BUG
> AMS scripts do not change the ownership of certain directories to AMS user if they exist already.
> FIX
> Adding an explicit chown to take ownership of the required directories (collector conf, collector checkpoint, HBase tmp, HBase conf, HBase root)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)