2013-04-05 19:14:09,345 INFO org.apache.hadoop.yarn.server.nodemanager.NodeStatusUpdaterImpl: Sending out status for container: container_id {, app_attempt_id {, application_id {, id: 1, cluster_timestamp: 1365187402863, }, attemptId: 1, }, id: 57, }, state: C_RUNNING, diagnostics: "", exit_status: -1000, 2013-04-05 19:14:09,345 INFO org.apache.hadoop.yarn.server.nodemanager.NodeStatusUpdaterImpl: Sending out status for container: container_id {, app_attempt_id {, application_id {, id: 1, cluster_timestamp: 1365187402863, }, attemptId: 1, }, id: 58, }, state: C_RUNNING, diagnostics: "", exit_status: -1000, 2013-04-05 19:14:09,345 INFO org.apache.hadoop.yarn.server.nodemanager.NodeStatusUpdaterImpl: Sending out status for container: container_id {, app_attempt_id {, application_id {, id: 1, cluster_timestamp: 1365187402863, }, attemptId: 1, }, id: 60, }, state: C_RUNNING, diagnostics: "", exit_status: -1000, Looked at the interface org.apache.hadoop.yarn.api.records.ContainerStatus and there was a comment about the getExitStatus() method:
* Get the exit status for the container.
*
* Note: This is valid only for completed containers i.e.
* containers with state {@link ContainerState#COMPLETE}.
* Otherwise, it returns an invalid exit code equal
* to {@literal -1000};
Seems the status is quit normal. Just wonder why Yarn does not change it to a more meaningful output or simply suppress this log.
