hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhijie Shen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-2302) Refactor TimelineWebServices
Date Thu, 17 Jul 2014 03:10:04 GMT

     [ https://issues.apache.org/jira/browse/YARN-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Zhijie Shen updated YARN-2302:

    Attachment: YARN-2302.1.patch

Upload the patch of the code refactoring. The logic for the web services is kept same. I passed
the timeline service test cases locally, and verified the timeline server with a single node
cluster, where it worked fine.

> 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
> 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