[
https://issues.apache.org/jira/browse/AMBARI-18502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranjan Banerjee updated AMBARI-18502:
-------------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Patch is submitted
> Logging of ambari agent scheduling activities in debug mode
> -----------------------------------------------------------
>
> Key: AMBARI-18502
> URL: https://issues.apache.org/jira/browse/AMBARI-18502
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
> Affects Versions: trunk
> Reporter: Ranjan Banerjee
> Priority: Minor
> Labels: ambari-agent
> Fix For: trunk
>
> Attachments: AMBARI-18502.patch, AMBARI-18502.patch
>
>
> We find lots of stale alerts in Ambari. On digging deeper from the
> Ambari-agent logs it is found that there were many services that missed the
> triggering window, but no insight as to why it is missed. The aim of this is
> to add some debug logs on two steps primarily:
> 1)When the scheduler iterates through the jobstore and decides it is time to
> schedule the job.
> 2)The threadpool, being forked and executing the callback function
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
