Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Tue, 8 Oct 2013 19:06:43 +0000 (UTC)
From: "Sandy Ryza (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12659948.1374801082521.33787.1381259203068@arcas>
In-Reply-To: <JIRA.12659948.1374801082521@arcas>
References: <JIRA.12659948.1374801082521@arcas>
Subject: [jira] [Resolved] (HADOOP-9775) Add tracking IDs to FS tokens to
 allow tracing FS operations back to job
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Sandy Ryza resolved HADOOP-9775.
--------------------------------

    Resolution: Duplicate

> Add tracking IDs to FS tokens to allow tracing FS operations back to job
> ------------------------------------------------------------------------
>
>                 Key: HADOOP-9775
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9775
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: security
>    Affects Versions: 2.1.0-beta
>            Reporter: Sandy Ryza
>            Assignee: Sandy Ryza
>
> It would be helpful for auditing to allow tracing of file system operations to the higher-level operations that encompass them (e.g. MR jobs).
> Approaches to achieving this by logging delegation token sequence numbers at job start were discussed on MAPREDUCE-5379, but rejected because delegation token identifiers are meant to be opaque.
> Per discussion between Tucu and Daryn, a better way to do this would be to include a tracking ID with delegation tokens.  When requesting a delegation token, a job would be able to pass its job ID along to be included with the token.  


--
This message was sent by Atlassian JIRA
(v6.1#6144)