Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 29 Jun 2016 07:03:45 +0000 (UTC)
From: "Rohith Sharma K S (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12981214.1466492032000.1858.1467183825525@Atlassian.JIRA>
In-Reply-To: <JIRA.12981214.1466492032000@Atlassian.JIRA>
References: <JIRA.12981214.1466492032000@Atlassian.JIRA> <JIRA.12981214.1466492032829@arcas>
Subject: [jira] [Commented] (YARN-5276) print more info when event queue is
 blocked
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 29 Jun 2016 07:03:47 -0000


    [ https://issues.apache.org/jira/browse/YARN-5276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15354698#comment-15354698 ] 

Rohith Sharma K S commented on YARN-5276:
-----------------------------------------

Yes, 5K would be better I think. One nit is give space after comma in log message.

> print more info when event queue is blocked
> -------------------------------------------
>
>                 Key: YARN-5276
>                 URL: https://issues.apache.org/jira/browse/YARN-5276
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: sandflee
>            Assignee: sandflee
>         Attachments: YARN-5276.01.patch
>
>
> we now see logs like "Size of event-queue is 498000, Size of event-queue is 499000" and difficult to know which event flood the queue. 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org