ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ranjan Banerjee (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-18502) Logging of ambari agent scheduling activities in debug mode
Date Mon, 10 Oct 2016 23:35:20 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-18502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ranjan Banerjee updated AMBARI-18502:
-------------------------------------
               Labels: ambari-agent  (was: )
        Fix Version/s: trunk
    Affects Version/s: trunk
               Status: Patch Available  (was: Open)

Added debug logging to better understand if a scheduler has missed scheduling the job or there
is a threadpool delay in getting to the required job. Will help in the case of stale alerts

> 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
>
>
> 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)

Mime
View raw message