Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
Reviewed
Description
On container finished, we're reporting "YARN_CONTAINER_STATE: "RUNNING"". Do we design this deliberately or it's a bug?
{ metrics: [ ], events: [ { id: "YARN_CONTAINER_FINISHED", timestamp: 1464213765890, info: { YARN_CONTAINER_EXIT_STATUS: 0, YARN_CONTAINER_STATE: "RUNNING", YARN_CONTAINER_DIAGNOSTICS_INFO: "" } }, { id: "YARN_NM_CONTAINER_LOCALIZATION_FINISHED", timestamp: 1464213761133, info: { } }, { id: "YARN_CONTAINER_CREATED", timestamp: 1464213761132, info: { } }, { id: "YARN_NM_CONTAINER_LOCALIZATION_STARTED", timestamp: 1464213761132, info: { } } ], id: "container_e15_1464213707405_0001_01_000018", type: "YARN_CONTAINER", createdtime: 1464213761132, info: { YARN_CONTAINER_ALLOCATED_PRIORITY: "20", YARN_CONTAINER_ALLOCATED_VCORE: 1, YARN_CONTAINER_ALLOCATED_HOST_HTTP_ADDRESS: "10.22.16.164:0", UID: "yarn_cluster!application_1464213707405_0001!YARN_CONTAINER!container_e15_1464213707405_0001_01_000018", YARN_CONTAINER_ALLOCATED_HOST: "10.22.16.164", YARN_CONTAINER_ALLOCATED_MEMORY: 1024, SYSTEM_INFO_PARENT_ENTITY: { type: "YARN_APPLICATION_ATTEMPT", id: "appattempt_1464213707405_0001_000001" }, YARN_CONTAINER_ALLOCATED_PORT: 64694 }, configs: { }, isrelatedto: { }, relatesto: { } }