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-3044) [Event producers] Implement RM writing app lifecycle events to ATS
Date Thu, 26 Mar 2015 17:46:53 GMT

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

Sangjin Lee commented on YARN-3044:
-----------------------------------

{quote}
Well its not the limitation at RM timeline collector which i am trying to mention, but the
writer interface is like
TimelineWriter.write(TimelineEntities)
Writer would not be aware whether client is writing ApplicationEntity or AppAttemptEntity.IIUC
it will just try to write 
the fields of the TimelineEntity to the storage. May be if its just storing entity as an json
object directly to storage it might not be an issue but it will not be the case in hbase column
storage right ?
{quote}

I see. So your point is whether the storage implementation can recognize different entity
types and act accordingly? If so, the answer is yes. The storage implementation can easily
introspect the type of the entity and do the right thing based on the type if needed.

+ [~zjshen]

> [Event producers] Implement RM writing app lifecycle events to ATS
> ------------------------------------------------------------------
>
>                 Key: YARN-3044
>                 URL: https://issues.apache.org/jira/browse/YARN-3044
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Sangjin Lee
>            Assignee: Naganarasimha G R
>         Attachments: YARN-3044.20150325-1.patch
>
>
> Per design in YARN-2928, implement RM writing app lifecycle events to ATS.



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

Mime
View raw message