hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Li Lu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3047) [Data Serving] Set up ATS reader with basic request serving structure and lifecycle
Date Fri, 27 Mar 2015 18:57:56 GMT

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

Li Lu commented on YARN-3047:
-----------------------------

I tried the latest (006) patch on my machine. There were some hunk fails with .cmd file:
{code}
patching file hadoop-yarn-project/hadoop-yarn/bin/yarn
patching file hadoop-yarn-project/hadoop-yarn/bin/yarn.cmd
Hunk #1 FAILED at 151.
Hunk #2 FAILED at 242.
Hunk #3 FAILED at 317.
3 out of 3 hunks FAILED -- saving rejects to file hadoop-yarn-project/hadoop-yarn/bin/yarn.cmd.rej
{code}

BTW, why TimelineEvents.java is still here?

For the documentation, I know what a thread pool is but my point is maybe we don't need to
reach into the HttpServer2 level for now. We may also want to focus on building the whole
thing up rather than deciding the best parameters for performance tuning. 

> [Data Serving] Set up ATS reader with basic request serving structure and lifecycle
> -----------------------------------------------------------------------------------
>
>                 Key: YARN-3047
>                 URL: https://issues.apache.org/jira/browse/YARN-3047
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Sangjin Lee
>            Assignee: Varun Saxena
>         Attachments: Timeline_Reader(draft).pdf, YARN-3047.001.patch, YARN-3047.003.patch,
YARN-3047.005.patch, YARN-3047.006.patch, YARN-3047.02.patch, YARN-3047.04.patch
>
>
> Per design in YARN-2938, set up the ATS reader as a service and implement the basic structure
as a service. It includes lifecycle management, request serving, and so on.



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

Mime
View raw message