[
https://issues.apache.org/jira/browse/YARN-5792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15654321#comment-15654321
]
Varun Saxena commented on YARN-5792:
------------------------------------
The patch does the following.
# Uses inverse of container start time to publish id prefix for container
entities. As container start time is not stored in NM state store, added
support to add it as well.
# Uses inverse of task start time to publish id prefix for task entities.
# Uses inverse of task attempt start time to publish id prefix for task attempt
entities.
# Uses inverse of DS container start time to publish id prefix for distributed
shell container entities.
# Uses inverse of attempt start time to publish id prefix for app attempt
entities. We can potentially use inverse of attempt id bit of
ApplicationAttemptId as well here. Also app registered time can be used.
# Uses inverse of DS attempt start time to publish id prefix for DS attempt
entities. We can potentially use inverse of attempt id bit of
ApplicationAttemptId as well here.
# Uses inverse of id bit of job id to publish id prefix for job entities. We
can potentially use job start time here.
Last 3 points we can reach a consensus on as to what to use.
> adopt the id prefix for YARN, MR, and DS entities
> -------------------------------------------------
>
> Key: YARN-5792
> URL: https://issues.apache.org/jira/browse/YARN-5792
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Affects Versions: YARN-5355
> Reporter: Sangjin Lee
> Assignee: Varun Saxena
> Attachments: YARN-5792-YARN-5355.01.patch
>
>
> We introduced the entity id prefix to support flexible entity sorting
> (YARN-5715). We should adopt the id prefix for YARN entities, MR entities,
> and DS entities to take advantage of the id prefix.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
