hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Junping Du (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2302) Refactor TimelineWebServices
Date Sun, 10 Aug 2014 04:39:12 GMT

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

Junping Du commented on YARN-2302:

Latest patch LGTM. +1 pending on Jenkins.

> Refactor TimelineWebServices
> ----------------------------
>                 Key: YARN-2302
>                 URL: https://issues.apache.org/jira/browse/YARN-2302
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Zhijie Shen
>            Assignee: Zhijie Shen
>         Attachments: YARN-2302.1.patch, YARN-2302.2.patch, YARN-2302.3.patch, YARN-2302.4.patch
> Now TimelineWebServices contains non-trivial logic to process the HTTP requests, manipulate
the data, check the access, and interact with the timeline store.
> I propose the move the data-oriented logic to a middle layer (so called TimelineDataManager),
and TimelineWebServices only processes the requests, and call TimelineDataManager to complete
the remaining tasks.
> By doing this, we make the generic history module reuse TimelineDataManager internally
(YARN-2033), invoking the putting/getting methods directly. Otherwise, we have to send the
HTTP requests to TimelineWebServices to query the generic history data, which is not an efficient

This message was sent by Atlassian JIRA

View raw message