hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Li Lu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4178) [storage implementation] app id as string can cause incorrect ordering
Date Thu, 17 Sep 2015 20:29:04 GMT

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

Li Lu commented on YARN-4178:
-----------------------------

We can rely on ApplicationId class in YARN api to fix this, right? As encapsulated in {{TimelineCollectorContext}},
shall we change the appID part into an ApplicationId typed object, and have an internal method
to convert an ApplicationId to bytes for HBase storage? I suspect this is a whole flow change
if we want to use ApplicationId in TimelineCollectorContext. Let's try not to break ongoing
patches for this change. 

> [storage implementation] app id as string can cause incorrect ordering
> ----------------------------------------------------------------------
>
>                 Key: YARN-4178
>                 URL: https://issues.apache.org/jira/browse/YARN-4178
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>    Affects Versions: YARN-2928
>            Reporter: Sangjin Lee
>            Assignee: Varun Saxena
>
> Currently the app id is used in various places as part of row keys and in column names.
However, they are treated as strings for the most part. This will cause a problem with ordering
when the id portion of the app id rolls over to the next digit.
> For example, "app_1234567890_100" will be considered *earlier* than "app_1234567890_99".
We should correct this.



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

Mime
View raw message