[
https://issues.apache.org/jira/browse/AMBARI-23012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16367280#comment-16367280
]
Hudson commented on AMBARI-23012:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8744 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8744/])
AMBARI-23012. "Stale Alerts" alert appears on cluster after some time
(aonishuk:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=30e179fba6e8c5f38a917ec128e6ed58fe3556fb])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/agent/HeartBeatHandler.java
> "Stale Alerts" alert appears on cluster after some time
> -------------------------------------------------------
>
> Key: AMBARI-23012
> URL: https://issues.apache.org/jira/browse/AMBARI-23012
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: AMBARI-23012.patch, AMBARI-23012.patch
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Previously. Every x seconds any alert was updated with information from agent.
> Even if nothing changed.
> Due to perf reasons this behavior was changed so that agent reports alerts
> only when their status changes.
> Due this change, "stale alerts" alert started appearing on clusters, showing
> that alerts were not updated for a long time.
> We should consider alert up-to-date to the point of last heartbeat. Which
> shows that the connection between server and agent is okay due to
> last_hb_timestamp, and so agent could send alert updates.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
