Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E816918801 for ; Wed, 30 Mar 2016 01:06:25 +0000 (UTC) Received: (qmail 1841 invoked by uid 500); 30 Mar 2016 01:06:25 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 1766 invoked by uid 500); 30 Mar 2016 01:06:25 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 1733 invoked by uid 99); 30 Mar 2016 01:06:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Mar 2016 01:06:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 890ED2C1F6C for ; Wed, 30 Mar 2016 01:06:25 +0000 (UTC) Date: Wed, 30 Mar 2016 01:06:25 +0000 (UTC) From: "Sangjin Lee (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-4183) Clarify the behavior of timeline service config properties MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15217183#comment-15217183 ] Sangjin Lee commented on YARN-4183: ----------------------------------- OK, could you do the honors? > Clarify the behavior of timeline service config properties > ---------------------------------------------------------- > > Key: YARN-4183 > URL: https://issues.apache.org/jira/browse/YARN-4183 > Project: Hadoop YARN > Issue Type: Bug > Affects Versions: 2.7.1 > Reporter: Mit Desai > Assignee: Naganarasimha G R > Attachments: YARN-4183.1.patch, YARN-4183.v1.001.patch, YARN-4183.v1.002.patch > > > When enabling just the Generic History Server and not the timeline server, the system metrics publisher will not publish the events to the timeline store as it checks if the timeline server and system metrics publisher are enabled before creating a timeline client. > To make it work, if the timeline service flag is turned on, it will force every yarn application to get a delegation token. > Instead of checking if timeline service is enabled, we should be checking if application history server is enabled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)