You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by GitBox <gi...@apache.org> on 2019/09/23 12:40:28 UTC

[GitHub] [hadoop] caneGuy opened a new pull request #1502: YARN-9851: Make execution type check compatiable

caneGuy opened a new pull request #1502: YARN-9851: Make execution type check compatiable
URL: https://github.com/apache/hadoop/pull/1502
 
 
   
   During upgrade from 2.6 to 3.1, we encountered a problem:
   
   {code:java}
   2019-09-23,19:29:05,303 WARN org.apache.hadoop.yarn.server.resourcemanager.rmnode.RMNodeImpl: Lost container container_e35_1568719110875_6460_08_000001, status: RUNNING, execution type: null
   2019-09-23,19:29:05,303 WARN org.apache.hadoop.yarn.server.resourcemanager.rmnode.RMNodeImpl: Lost container container_e35_1568886618758_11172_01_000062, status: RUNNING, execution type: null
   2019-09-23,19:29:05,303 WARN org.apache.hadoop.yarn.server.resourcemanager.rmnode.RMNodeImpl: Lost container container_e35_1568886618758_11172_01_000063, status: RUNNING, execution type: null
   2019-09-23,19:29:05,303 WARN org.apache.hadoop.yarn.server.resourcemanager.rmnode.RMNodeImpl: Lost container container_e35_1568886618758_11172_01_000064, status: RUNNING, execution type: null
   2019-09-23,19:29:05,303 WARN org.apache.hadoop.yarn.server.resourcemanager.rmnode.RMNodeImpl: Lost container container_e35_1568886618758_30617_01_000006, status: RUNNING, execution type: null
   
   for (ContainerStatus remoteContainer : containerStatuses) {
     if (remoteContainer.getState() == ContainerState.RUNNING
         && remoteContainer.getExecutionType() == ExecutionType.GUARANTEED) {
       nodeContainers.add(remoteContainer.getContainerId());
     } else {
       LOG.warn("Lost container " + remoteContainer.getContainerId()
               + ", status: " + remoteContainer.getState()
               + ", execution type: " + remoteContainer.getExecutionType());
     }
   }​
   
   {code}
   The cause is that we has nm with version 2.6, which do not have executionType for container status.
   We should make the check more compatiable.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

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