[jira] [Updated] (YARN-2997) NM keeps sending already-sent completed containers to RM until containers are removed from context

2015-08-03 Thread Vinod Kumar Vavilapalli (JIRA) 

 [ 
https://issues.apache.org/jira/browse/YARN-2997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinod Kumar Vavilapalli updated YARN-2997:
--
Labels: 2.6.1-candidate  (was: )

> NM keeps sending already-sent completed containers to RM until containers are 
> removed from context
> --
>
> Key: YARN-2997
> URL: https://issues.apache.org/jira/browse/YARN-2997
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: nodemanager
>Affects Versions: 2.6.0
>Reporter: Chengbing Liu
>Assignee: Chengbing Liu
>  Labels: 2.6.1-candidate
> Fix For: 2.7.0
>
> Attachments: YARN-2997.2.patch, YARN-2997.3.patch, YARN-2997.4.patch, 
> YARN-2997.5.patch, YARN-2997.patch
>
>
> We have seen in RM log a lot of
> {quote}
> INFO 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler: 
> Null container completed...
> {quote}
> It is caused by NM sending completed containers repeatedly until the app is 
> finished. On the RM side, the container is already released, hence 
> {{getRMContainer}} returns null.



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

[jira] [Updated] (YARN-2997) NM keeps sending already-sent completed containers to RM until containers are removed from context

2015-08-30 Thread Vinod Kumar Vavilapalli (JIRA) 

 [ 
https://issues.apache.org/jira/browse/YARN-2997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinod Kumar Vavilapalli updated YARN-2997:
--
Fix Version/s: 2.6.1

Pulled this into 2.6.1. Ran compilation and TestNodeStatusUpdater before the 
push. Patch applied cleanly.


> NM keeps sending already-sent completed containers to RM until containers are 
> removed from context
> --
>
> Key: YARN-2997
> URL: https://issues.apache.org/jira/browse/YARN-2997
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: nodemanager
>Affects Versions: 2.6.0
>Reporter: Chengbing Liu
>Assignee: Chengbing Liu
>  Labels: 2.6.1-candidate
> Fix For: 2.7.0, 2.6.1
>
> Attachments: YARN-2997.2.patch, YARN-2997.3.patch, YARN-2997.4.patch, 
> YARN-2997.5.patch, YARN-2997.patch
>
>
> We have seen in RM log a lot of
> {quote}
> INFO 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler: 
> Null container completed...
> {quote}
> It is caused by NM sending completed containers repeatedly until the app is 
> finished. On the RM side, the container is already released, hence 
> {{getRMContainer}} returns null.



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

[jira] [Updated] (YARN-2997) NM keeps sending already-sent completed containers to RM until containers are removed from context

2015-01-08 Thread Jian He (JIRA) 

 [ 
https://issues.apache.org/jira/browse/YARN-2997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jian He updated YARN-2997:
--
Summary: NM keeps sending already-sent completed containers to RM until 
containers are removed from context  (was: NM keeps sending already-sent 
completed containers to RM until containers are acked)

> NM keeps sending already-sent completed containers to RM until containers are 
> removed from context
> --
>
> Key: YARN-2997
> URL: https://issues.apache.org/jira/browse/YARN-2997
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: nodemanager
>Affects Versions: 2.6.0
>Reporter: Chengbing Liu
>Assignee: Chengbing Liu
> Attachments: YARN-2997.2.patch, YARN-2997.3.patch, YARN-2997.4.patch, 
> YARN-2997.5.patch, YARN-2997.patch
>
>
> We have seen in RM log a lot of
> {quote}
> INFO 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler: 
> Null container completed...
> {quote}
> It is caused by NM sending completed containers repeatedly until the app is 
> finished. On the RM side, the container is already released, hence 
> {{getRMContainer}} returns null.



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