hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Kanter (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5933) Enable MR AM to post history events to the timeline server
Date Fri, 03 Oct 2014 00:28:34 GMT

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

Robert Kanter commented on MAPREDUCE-5933:
------------------------------------------

{quote}1. It seems that we have associated all the events to a single MR job entity, which
doesn't reflect the nested structure: a MR job contains multiple map/reduce tasks. IMHO, we
should have two level of entities: 1) MR job entity and 2) MR task entity with two type: Map
and Reduce. The job events are added to the job entity while the task attempts are added to
the particular task entity.{quote}
When I do this, should I add the task entities as related entities to the job entity (and/or
the other way around)?  Otherwise, they won't be connected because the entities cannot be
nested.  Also, does being a related entity _do_ anything?

> Enable MR AM to post history events to the timeline server
> ----------------------------------------------------------
>
>                 Key: MAPREDUCE-5933
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5933
>             Project: Hadoop Map/Reduce
>          Issue Type: Sub-task
>          Components: mr-am
>            Reporter: Zhijie Shen
>            Assignee: Robert Kanter
>         Attachments: MAPREDUCE-5933.patch, MAPREDUCE-5933.patch, MAPREDUCE-5933.patch,
MAPREDUCE-5933.patch, mr_timelineserver_response.txt
>
>
> Nowadays, MR AM collects the history events and writes it to HDFS for JHS to source.
With the timeline server, MR AM can put these events there.



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

Mime
View raw message