Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-dev@hadoop.apache.org
Date: Thu, 30 Oct 2014 21:57:34 +0000 (UTC)
From: "Vinod Kumar Vavilapalli (JIRA)" <jira@apache.org>
To: yarn-dev@hadoop.apache.org
Message-ID: <JIRA.12751764.1414696213000.376918.1414706254380@Atlassian.JIRA>
In-Reply-To: <JIRA.12751764.1414696213000@Atlassian.JIRA>
References: <JIRA.12751764.1414696213000@Atlassian.JIRA>
 <JIRA.12751764.1414696213177@arcas>
Subject: [jira] [Resolved] (YARN-2779) SystemMetricsPublisher needs to renew
 and cancel timeline DT too
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/YARN-2779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod Kumar Vavilapalli resolved YARN-2779.
-------------------------------------------
    Resolution: Invalid

This doesn't make any sense.

RM can simply use kerberos based auth to talk to Timeline service. It doesn't need tokens at all.

Closing this as invalid, reopen if you disagree.

> SystemMetricsPublisher needs to renew and cancel timeline DT too
> ----------------------------------------------------------------
>
>                 Key: YARN-2779
>                 URL: https://issues.apache.org/jira/browse/YARN-2779
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager, timelineserver
>    Affects Versions: 2.6.0
>            Reporter: Zhijie Shen
>            Assignee: Zhijie Shen
>            Priority: Critical
>
> SystemMetricsPublisher is going to grab a timeline DT in secure mode as well. The timeline DT will expiry after 24h. No DT renewer will handle renewing work for SystemMetricsPublisher, but this has to been handled by itself. In addition, SystemMetricsPublisher should cancel the timeline DT when it is stopped, too.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)