Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Tue, 2 Feb 2016 20:01:39 +0000 (UTC)
From: "Matt Sharp (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12936077.1454443262000.280356.1454443299791@Atlassian.JIRA>
In-Reply-To: <JIRA.12936077.1454443262000@Atlassian.JIRA>
References: <JIRA.12936077.1454443262000@Atlassian.JIRA>
 <JIRA.12936077.1454443262058@arcas>
Subject: [jira] [Created] (AMBARI-14883) Express Upgrade - All Service
 Checks Failure - Queue State
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Matt Sharp created AMBARI-14883:
-----------------------------------

             Summary: Express Upgrade - All Service Checks Failure - Queue State
                 Key: AMBARI-14883
                 URL: https://issues.apache.org/jira/browse/AMBARI-14883
             Project: Ambari
          Issue Type: Bug
          Components: ambari-upgrade
    Affects Versions: 2.2.0
            Reporter: Matt Sharp
            Priority: Minor


At the beginning of an Ambari 2.2.0 express upgrade, Ambari prompts you to manually stop all Yarn queues.  At the end of the upgrade it does not prompt you to manually start all Yarn queues again.  This results in the following error during the All Service Checks phase:

org.apache.hadoop.security.AccessControlException: Queue default is STOPPED.  Cannot accept submission of application: application_1454357083355_0002

A prompt either needs to be added to update the queue state, or ideally handled by Ambari entirely (especially since the cluster is stopped with express upgrade path).


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