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 9F9FF200BB6 for ; Thu, 20 Oct 2016 20:46:03 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 9EA59160ACC; Thu, 20 Oct 2016 18:46:03 +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 EDDB7160AF2 for ; Thu, 20 Oct 2016 20:46:02 +0200 (CEST) Received: (qmail 82981 invoked by uid 500); 20 Oct 2016 18:45:59 -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 82417 invoked by uid 99); 20 Oct 2016 18:45:59 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Oct 2016 18:45:59 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 418C82C2AC1 for ; Thu, 20 Oct 2016 18:45:59 +0000 (UTC) Date: Thu, 20 Oct 2016 18:45:59 +0000 (UTC) From: "Joep Rottinghuis (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-5742) Serve aggregated logs of historical apps from timeline service MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 20 Oct 2016 18:46:03 -0000 [ https://issues.apache.org/jira/browse/YARN-5742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15592635#comment-15592635 ] Joep Rottinghuis commented on YARN-5742: ---------------------------------------- We should really carefully consider whether serving yarn application logs is a timeline service concern. I'd argue that belongs in a separate Yarn service. It would be perfectly acceptable to have that separate service store metadata (about the current log location of tasks, whether that is on local disk, or aggregated to a location such as HDFS) in the timeline service, but I think the serving itself doesn't below here. Providing an api that can read files from HDFS and stream them out would be opening security concerns, would duplicate efforts from services such as WebHDFS/HttpFS and all their concerns. The HttpFS approach of a central pool of nodes serving data from HDFS has been superseded by a distributed WebHDFS approach. Note by the way that WebHDFS as it stands today still has some compatibility challenges with HDFS federation. Both of these general approaches of serving HDFS data have to deal with proxying user requests and correctly limiting visibility of HDFS files to the users with the appropriate access. > Serve aggregated logs of historical apps from timeline service > -------------------------------------------------------------- > > Key: YARN-5742 > URL: https://issues.apache.org/jira/browse/YARN-5742 > Project: Hadoop YARN > Issue Type: Sub-task > Components: timelineserver > Reporter: Varun Saxena > Assignee: Rohith Sharma K S > Attachments: YARN-5742-POC-v0.patch > > -- 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