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

Vinod Kumar Vavilapalli commented on YARN-5082:
-----------------------------------------------

bq. CS has similar issue. (Linked)
Pitching in late. Haven't looked at the patch / commit. Can this not be fixed 
in a unified way between the schedulers?

> Limit ContainerId increase in fair scheduler if the num of  node app reserved 
> reached the limit
> -----------------------------------------------------------------------------------------------
>
>                 Key: YARN-5082
>                 URL: https://issues.apache.org/jira/browse/YARN-5082
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: sandflee
>            Assignee: sandflee
>             Fix For: 2.9.0
>
>         Attachments: YARN-5082.01.patch, YARN-5082.02.patch, 
> YARN-5082.03.patch, YARN-5082.04.patch, YARN-5082.addendum.patch
>
>
> see many logs like 
> {quote}
> 16/05/14 01:07:58 DEBUG fair.FSAppAttempt: Not creating reservation as 
> container container_1463159225729_0002_01_000003 is not reservable
> 16/05/14 01:07:58 DEBUG fair.FSAppAttempt: Not creating reservation as 
> container container_1463159225729_0002_01_000004 is not reservable
> 16/05/14 01:07:58 DEBUG fair.FSAppAttempt: Not creating reservation as 
> container container_1463159225729_0002_01_000005 is not reservable
> 16/05/14 01:07:58 DEBUG fair.FSAppAttempt: Not creating reservation as 
> container container_1463159225729_0002_01_000006 is not reservable
> 16/05/14 01:07:58 DEBUG fair.FSAppAttempt: Not creating reservation as 
> container container_1463159225729_0002_01_000007 is not reservable
> {quote}



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

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

Reply via email to