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 794EE18C00 for ; Sat, 14 Nov 2015 11:32:11 +0000 (UTC) Received: (qmail 83142 invoked by uid 500); 14 Nov 2015 11:32:11 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 83090 invoked by uid 500); 14 Nov 2015 11:32:11 -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 83073 invoked by uid 99); 14 Nov 2015 11:32:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 14 Nov 2015 11:32:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 173AD2C1F69 for ; Sat, 14 Nov 2015 11:32:11 +0000 (UTC) Date: Sat, 14 Nov 2015 11:32:11 +0000 (UTC) From: "Varun Saxena (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-4183) Enabling generic application history forces every job to get a timeline service delegation token 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=15005342#comment-15005342 ] Varun Saxena commented on YARN-4183: ------------------------------------ bq. i feel yarn.resourcemanager.system-metrics-publisher.enabled is sufficient to be configured. Agree. Enabling system metrics publisher should be considered to be enough to publish events from RM. bq. As far as i view it "yarn.timeline-service.enabled"* name is misleading, it should be more to signify client requires the timeline service's delegation token. Maybe we can use the version config to decide if we have to fetch a token or not (in addition with timeline service enabled config ?). > Enabling generic application history forces every job to get a timeline service delegation token > ------------------------------------------------------------------------------------------------ > > 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: Mit Desai > Attachments: YARN-4183.1.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)