Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id E5CE7200B32 for ; Tue, 24 May 2016 22:38:14 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id E4B43160A35; Tue, 24 May 2016 20:38:14 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 40731160A37 for ; Tue, 24 May 2016 22:38:14 +0200 (CEST) Received: (qmail 13082 invoked by uid 500); 24 May 2016 20:38:13 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 12891 invoked by uid 99); 24 May 2016 20:38:13 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 May 2016 20:38:13 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 193F72C1F6B for ; Tue, 24 May 2016 20:38:13 +0000 (UTC) Date: Tue, 24 May 2016 20:38:13 +0000 (UTC) From: "Varun Saxena (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-4835) [YARN-3368] REST API related changes for new Web UI MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 24 May 2016 20:38:15 -0000 [ https://issues.apache.org/jira/browse/YARN-4835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15298846#comment-15298846 ] Varun Saxena commented on YARN-4835: ------------------------------------ I have added a few APIs' which are required for WebUI. Primarily for MapReduce AM. Not updated documentation for this because we need to reach a consensus on naming and also whether we make it public or not. Because its primarily for UI. These URLs' are not necessarily following the scheme followed for other REST endpoints. Because we are fetching things like counters for all tasks belonging to a job(if we do this the normal way, will have to fetch all the tasks and then fetch counters for each one of them). The use case for UI is primarily to fetch a particular counter for all tasks belonging to a job. For this I have provided a query param for counter group and counter name. Did not put it as part of path. We can choose either of the 2 approaches. If we go with query param, we can probably extend counter group and name as query param to other counter related REST endpoints as well. > [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 > Reporter: Varun Saxena > Assignee: Varun Saxena > Attachments: YARN-4835-YARN-3368.01.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: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org