You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by "zhoukang (Jira)" <ji...@apache.org> on 2019/09/23 11:59:00 UTC

[jira] [Created] (YARN-9851) Make execution type check compatiable

zhoukang created YARN-9851:
------------------------------

             Summary: Make execution type check compatiable
                 Key: YARN-9851
                 URL: https://issues.apache.org/jira/browse/YARN-9851
             Project: Hadoop YARN
          Issue Type: Improvement
            Reporter: zhoukang


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 check here make the upgrade process more tranparently




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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