[ 
https://issues.apache.org/jira/browse/YARN-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15551786#comment-15551786
 ] 

Rohith Sharma K S commented on YARN-5699:
-----------------------------------------

bq. Is this intentional ?
yes, because the same information also published by RM. So I think we can keep 
at one place.
{code}
[
  {
    "events": [
      {
        "id": "YARN_RM_CONTAINER_FINISHED",
        "timestamp": 1475469588288,
        "info": {
          "YARN_CONTAINER_STATE": "COMPLETE",
          "YARN_CONTAINER_EXIT_STATUS": 0,
          "YARN_CONTAINER_DIAGNOSTICS_INFO": ""
        }
      },
      {
        "id": "YARN_RM_CONTAINER_CREATED",
        "timestamp": 1475469570721,
        "info": {
          "YARN_CONTAINER_ALLOCATED_PORT": 25006,
          "YARN_CONTAINER_ALLOCATED_MEMORY": 1024,
          "YARN_CONTAINER_ALLOCATED_PRIORITY": 0,
          "YARN_CONTAINER_ALLOCATED_HOST_HTTP_ADDRESS": 
"http://ctr-e29-1471411959733-0412-01-000004.hwx.site:25008";,
          "YARN_CONTAINER_ALLOCATED_HOST": 
"ctr-e29-1471411959733-0412-01-000004.hwx.site",
          "YARN_CONTAINER_ALLOCATED_VCORE": 1
        }
      },
      {
        "id": "YARN_CONTAINER_CREATED",
        "timestamp": -1,
        "info": {}
      },
      {
        "id": "YARN_CONTAINER_FINISHED",
        "timestamp": -1,
        "info": {
          "YARN_CONTAINER_STATE": "RUNNING",
          "YARN_CONTAINER_EXIT_STATUS": 0,
          "YARN_CONTAINER_DIAGNOSTICS_INFO": ""
        }
      },
      {
        "id": "YARN_NM_CONTAINER_LOCALIZATION_FINISHED",
        "timestamp": -1,
        "info": {}
      },
      {
        "id": "YARN_NM_CONTAINER_LOCALIZATION_STARTED",
        "timestamp": -1,
        "info": {}
      }
    ],
    "type": "YARN_CONTAINER",
    "id": "container_e09_1475277121920_0010_01_000001",
    "createdtime": -1,
    "info": {
      "YARN_CONTAINER_ALLOCATED_PORT": 25006,
      "UID": 
"yarn-cluster!application_1475277121920_0010!YARN_CONTAINER!container_e09_1475277121920_0010_01_000001",
      "YARN_CONTAINER_ALLOCATED_MEMORY": 1024,
      "SYSTEM_INFO_PARENT_ENTITY": {
        "type": "YARN_APPLICATION_ATTEMPT",
        "id": "appattempt_1475277121920_0010_000001"
      },
      "YARN_CONTAINER_ALLOCATED_PRIORITY": "0",
      "YARN_CONTAINER_ALLOCATED_HOST": 
"ctr-e29-1471411959733-0412-01-000004.hwx.site",
      "YARN_CONTAINER_ALLOCATED_HOST_HTTP_ADDRESS": 
"ctr-e29-1471411959733-0412-01-000004.hwx.site:0",
      "YARN_CONTAINER_ALLOCATED_VCORE": 1
    },
    "configs": {},
    "isrelatedto": {},
    "relatesto": {}
  }
]
{code}

bq. Container event publishing from RM is optional.
I see. But I think we should make it mandatory to publish from RM since some 
information always get from RM like container_state. Otherwise we miss the this 
information else container_state info should be published from NM. YARN-5156 
removes from NM publisher.

> Retrospect yarn entity fields which are publishing in events info fields.
> -------------------------------------------------------------------------
>
>                 Key: YARN-5699
>                 URL: https://issues.apache.org/jira/browse/YARN-5699
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Rohith Sharma K S
>            Assignee: Rohith Sharma K S
>         Attachments: 0001-YARN-5699.YARN-5355.patch, 0001-YARN-5699.patch
>
>
> Currently, all the container information are published at 2 places. Some of 
> them are at entity info(top-level) and some are  at event info. 
> For containers, some of the event info should be published at container info 
> level. For example : container exist status, container state, createdTime, 
> finished time. These are general information to container required for 
> container-report. So it is better to publish at top level info field. 



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

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to