[
https://issues.apache.org/jira/browse/YARN-5792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15658522#comment-15658522
]
Sangjin Lee commented on YARN-5792:
-----------------------------------
[~varun_saxena], thanks for the update!
Your points are acknowledged about the MR task id as well as the container id.
If using the id part takes extra assumptions and unnatural handling, then I
don't think we need to force it. My original concern about using the created
time is that that information may not always be available on all update cases.
If we can guarantee the created time is made always available for all kinds of
update scenarios, then I'm fine with using the created time. What do you think?
> 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,
> YARN-5792-YARN-5355.02.patch, YARN-5792-YARN-5355.03.patch,
> YARN-5792-YARN-5355.04.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: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
