[
https://issues.apache.org/jira/browse/YARN-4835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15300601#comment-15300601
]
Varun Saxena commented on YARN-4835:
------------------------------------
bq. I think we can have an MR jira to handle MR UI work. And in that, we can
have the splitted web service patch related to MR project. But its better this
work happen in same branch eventhough its a different jira (or umbrella jira in
MR project).
Yeah I mean in this branch only. IMO, we can just move this JIRA to MAPREDUCE
and have NM changes also in here only. But if NM changes are required to be
under YARN JIRA, we can keep this JIRA for that and raise a new MR JIRA for
rest of the changes.
Thoughts ?
I was talking about trunk with respect to limiting log file size related
changes(adding size as a query param).
We can decide where to handle it. Maybe raise a separate JIRA and handle it in
YARN-3368 branch itself.
> [YARN-3368] REST API related changes for new Web UI
> ---------------------------------------------------
>
> Key: YARN-4835
> URL: https://issues.apache.org/jira/browse/YARN-4835
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: webapp
> Affects Versions: YARN-3368
> Reporter: Varun Saxena
> Assignee: Varun Saxena
> Attachments: YARN-4835-YARN-3368.01.patch,
> YARN-4835-YARN-3368.02.patch
>
>
> Following things need to be added for AM related web pages.
> 1. Support task state query param in REST URL for fetching tasks.
> 2. Support task attempt state query param in REST URL for fetching task
> attempts.
> 3. A new REST endpoint to fetch counters for each task belonging to a job.
> Also have a query param for counter name.
> i.e. something like :
> {{/jobs/\{jobid\}/taskCounters}}
> 4. A REST endpoint in NM for fetching all log files associated with a
> container. Useful if logs served by NM.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
