Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Mon, 26 Dec 2016 16:21:58 +0000 (UTC)
From: "Andrew Onischuk (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13030605.1482769299000.595797.1482769318475@Atlassian.JIRA>
In-Reply-To: <JIRA.13030605.1482769299000@Atlassian.JIRA>
References: <JIRA.13030605.1482769299000@Atlassian.JIRA> <JIRA.13030605.1482769299898@arcas>
Subject: [jira] [Updated] (AMBARI-19298) If Oozie load balancer is stopped
 the error is not informative
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 26 Dec 2016 16:22:00 -0000


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

Andrew Onischuk updated AMBARI-19298:
-------------------------------------
    Attachment: AMBARI-19298.patch

> If Oozie load balancer is stopped the error is not informative
> --------------------------------------------------------------
>
>                 Key: AMBARI-19298
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19298
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 3.0.0
>
>         Attachments: AMBARI-19298.patch
>
>
> During uploading sharelib any exception are hidden by this informative
> message:
>     
>     Code is non-zero or output is empty. Code: 1
> So I had to debug the code. Just to later discover that load balancer was just
> not running and being the reason for failure.  
> We have to come up with something more informative in case our users hit this
> due to misconfiguration of load balancer


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