Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id EBC57200BAD for ; Tue, 11 Oct 2016 01:35:21 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id EA076160AEB; Mon, 10 Oct 2016 23:35:21 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 602E3160AE1 for ; Tue, 11 Oct 2016 01:35:21 +0200 (CEST) Received: (qmail 40064 invoked by uid 500); 10 Oct 2016 23:35:20 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 40054 invoked by uid 99); 10 Oct 2016 23:35:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Oct 2016 23:35:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 6B9522C0088 for ; Mon, 10 Oct 2016 23:35:20 +0000 (UTC) Date: Mon, 10 Oct 2016 23:35:20 +0000 (UTC) From: "Ranjan Banerjee (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-18502) Logging of ambari agent scheduling activities in debug mode MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 10 Oct 2016 23:35:22 -0000 [ 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)