hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sangjin Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3984) Rethink event column key issue
Date Wed, 29 Jul 2015 23:54:04 GMT

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

Sangjin Lee commented on YARN-3984:
-----------------------------------

{quote}
In addition to the key composition, I find another significant problem with the event store
schema. If the event doesn't contain any info, it will be ignored then. And we cannot always
guarantee user will put something into info. For example, user may define a KILL event without
any diagnostic msg.
{quote}

Thanks for spotting that issue [~zjshen]. That's definitely a huge issue. We should address
that as part of this JIRA...

> Rethink event column key issue
> ------------------------------
>
>                 Key: YARN-3984
>                 URL: https://issues.apache.org/jira/browse/YARN-3984
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Zhijie Shen
>            Assignee: Vrushali C
>             Fix For: YARN-2928
>
>
> Currently, the event column key is event_id?info_key?timestamp, which is not so friendly
to fetching all the events of an entity and sorting them in a chronologic order. IMHO, timestamp?event_id?info_key
may be a better key schema. I open this jira to continue the discussion about it which was
commented on YARN-3908.



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

Mime
View raw message