[
https://issues.apache.org/jira/browse/YARN-5276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363852#comment-15363852
]
Jun Gong commented on YARN-5276:
--------------------------------
I think it might be enough to add some debug information. When the size of
event queue is increasing, we could set its log level to DEBUG on the fly to
see what is happening.
{code}
---
a/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/event/AsyncDispatcher.java
+++
b/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/event/AsyncDispatcher.java
@@ -235,6 +235,10 @@ public void handle(Event event) {
}
drained = false;
+ if (LOG.isDebugEnabled()) {
+ LOG.debug("Add new event " + event.toString());
+ }
+
/* all this method does is enqueue all the events onto the queue */
int qSize = eventQueue.size();
if (qSize != 0 && qSize % 1000 == 0
{code}
> 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, YARN-5276.02.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: [email protected]
For additional commands, e-mail: [email protected]
