You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Ranjan Banerjee (JIRA)" <ji...@apache.org> on 2016/09/30 01:01:20 UTC
[jira] [Created] (AMBARI-18502) Logging of ambari agent scheduling
activities in debug mode
Ranjan Banerjee created AMBARI-18502:
----------------------------------------
Summary: 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
Reporter: Ranjan Banerjee
Priority: Minor
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)