ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebastian Toader (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-15158) Resource Manager fails to start: IOException: /ats/active does not exist
Date Wed, 24 Feb 2016 13:32:18 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-15158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sebastian Toader updated AMBARI-15158:
--------------------------------------
    Attachment: yarn-yarn-resourcemanager-host-10-0-0-5.log
                hdp-small-default.bp

> Resource Manager fails to start: IOException: /ats/active does not exist
> ------------------------------------------------------------------------
>
>                 Key: AMBARI-15158
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15158
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.2.1
>            Reporter: Sebastian Toader
>            Assignee: Sebastian Toader
>            Priority: Critical
>             Fix For: 2.2.1
>
>         Attachments: hdp-small-default.bp, yarn-yarn-resourcemanager-host-10-0-0-5.log
>
>
> Resource Manager fails to start when cluster is provisioned with blueprint for the first
time. After RM restart it works so it could be a sync issue. Log and blueprint attached.
> Config recommendation strategy is ONLY_STACK_DEFAULTS_APPLY



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

Mime
View raw message