hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandy Ryza (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5379) Include FS delegation token ID in job conf
Date Wed, 10 Jul 2013 17:35:49 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13704793#comment-13704793
] 

Sandy Ryza commented on MAPREDUCE-5379:
---------------------------------------

[~revans2], TokenCache already has logic for traversing the FS hierarchy and getting all the
delegation tokens.  Could we not do something like this?

[~daryn], I was thinking of token ID as the token identifier.  HDFS-4680 seeks to audit-log
token identifiers with FS operations.  If an MR job were to expose its token identifiers as
well, then we would be able to associate the FS operations it performed with it.  Right?
                
> Include FS delegation token ID in job conf
> ------------------------------------------
>
>                 Key: MAPREDUCE-5379
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5379
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: job submission, security
>    Affects Versions: 2.1.0-beta
>            Reporter: Sandy Ryza
>            Assignee: Sandy Ryza
>
> Making a job's FS delegation token ID accessible will allow external services to associate
it with the file system operations it performs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message