Mailing-List: contact issues-help@eagle.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@eagle.apache.org
Date: Tue, 3 Jan 2017 02:16:58 +0000 (UTC)
From: "Hao Chen (JIRA)" <jira@apache.org>
To: issues@eagle.apache.org
Message-ID: <JIRA.13031561.1483400955000.625613.1483409818564@Atlassian.JIRA>
In-Reply-To: <JIRA.13031561.1483400955000@Atlassian.JIRA>
References: <JIRA.13031561.1483400955000@Atlassian.JIRA> <JIRA.13031561.1483400955843@arcas>
Subject: [jira] [Updated] (EAGLE-848) eagle should log proper error instead
 of dying
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 03 Jan 2017 02:17:00 -0000


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

Hao Chen updated EAGLE-848:
---------------------------
    Component/s: Alert Engine

> eagle should log proper error instead of dying
> ----------------------------------------------
>
>                 Key: EAGLE-848
>                 URL: https://issues.apache.org/jira/browse/EAGLE-848
>             Project: Eagle
>          Issue Type: Improvement
>          Components: Alert Engine
>    Affects Versions: v0.5.0
>            Reporter: Jayesh
>             Fix For: v0.5.0
>
>
> on several occasions, I found eagle server dies because the exception is not handled, we should gather here such places, and put up proper exception handling to log the error that tells users of why exactly something didnt work.
> here is 1 example to begin with.
> eagle-server died because the topic mentioned to start application didnt exist in zookeeper.
> ! Causing: java.lang.RuntimeException: java.lang.RuntimeException: org.apache.zookeeper.KeeperException$NoNodeException: KeeperErrorCode = NoNode for /brokers/topics/hadoop_jmx_metric/partitions
> it would be even better to provide dropdown list of suggestion to choose topic from.


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