You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "stefanlee (JIRA)" <ji...@apache.org> on 2017/12/08 07:21:00 UTC
[jira] [Commented] (YARN-402) Dispatcher warn message is too late
[ https://issues.apache.org/jira/browse/YARN-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16283150#comment-16283150 ]
stefanlee commented on YARN-402:
--------------------------------
thanks [~djp] our cluster will be very busy between 3.00 a.m. and 7.00 a.m. the event-queue size will be 4000 to 5000, so how can i optimize this?
> Dispatcher warn message is too late
> -----------------------------------
>
> Key: YARN-402
> URL: https://issues.apache.org/jira/browse/YARN-402
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Lohit Vijayarenu
> Priority: Minor
>
> AsyncDispatcher throws out Warn when capacity remaining is less than 1000
> {noformat}
> if (remCapacity < 1000) {
> LOG.warn("Very low remaining capacity in the event-queue: "
> + remCapacity);
> }
> {noformat}
> What would be useful is to warn much before that, may be half full instead of when queue is completely full. I see that eventQueue capacity is int value. So, if one warn's queue has only 1000 capacity left, then service definitely has serious problem.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org