[
https://issues.apache.org/jira/browse/AMBARI-13954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15013721#comment-15013721
]
Hadoop QA commented on AMBARI-13954:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12773249/ok.png
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/4343//console
This message is automatically generated.
> Enable auto-start with alerting for AMS
> ---------------------------------------
>
> Key: AMBARI-13954
> URL: https://issues.apache.org/jira/browse/AMBARI-13954
> Project: Ambari
> Issue Type: Task
> Components: alerts, ambari-agent, ambari-metrics
> Affects Versions: 2.1.3
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13954-trunk.patch, critical.png, ok.png, warn.png
>
>
> - In 2.1.3 we have the watch dog script that will shutdown the API if HBase
> is unresponsive for sometime.
> - We also have the ability to auto-start per service / component
> - The two should work in conjunction for AMS
> - User needs to be alerted if Restarts are too frequent
> Alternative approach is for watch to act as a monitor and be responsible for
> restarting HBase.
> This should still be a alert hook but in that case the alert can be
> customized for AMS only.
> To turn on AMS auto-start append ambari.properties with
> {code}
> recovery.type=AUTO_START
> recovery.enabled_components=METRICS_COLLECTOR
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
