[
https://issues.apache.org/jira/browse/AMBARI-10126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14368059#comment-14368059
]
Hudson commented on AMBARI-10126:
---------------------------------
ABORTED: Integrated in Ambari-trunk-Commit #2072 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2072/])
AMBARI-10126 - Alert Scheduler Is Double Scheduling Jobs (jonathanhurley)
(jhurley:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=68468feeeeb35ca9edd4899ea8b1abafb7c2742a)
* ambari-agent/src/main/python/ambari_agent/Controller.py
> Alert Scheduler Is Double Scheduling Jobs
> -----------------------------------------
>
> Key: AMBARI-10126
> URL: https://issues.apache.org/jira/browse/AMBARI-10126
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
> Affects Versions: 2.0.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-10126.patch
>
>
> When the Ambari agent starts, the alerts scheduler loads all definitions from
> the cache definitions.json but doesn't start the scheduler. When the first
> heartbeat arrives, the jobs are re-added and the scheduler is started.
> However, job reconciliation doesn't happen until after the schedule is
> started, so there are duplicates of every job scheduled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)