Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 10 Jul 2012 00:34:34 +0000 (UTC)
From: "Aaron T. Myers (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <1743439498.26084.1341880474886.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <295909511.17645.1341624095143.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (HDFS-3608) fuse_dfs: use inotify to detect
 changes in UID ticket cache
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Aaron T. Myers commented on HDFS-3608:
--------------------------------------

I wasn't saying that we definitely shouldn't use inotify, just that using inotify is not the goal of the JIRA. The goal of the JIRA is to make fuse_dfs not cache Filesystem instances longer than it should. One potential implementation is to use inotify. Thus, we should update the summary/description of the JIRA.
                
> fuse_dfs: use inotify to detect changes in UID ticket cache
> -----------------------------------------------------------
>
>                 Key: HDFS-3608
>                 URL: https://issues.apache.org/jira/browse/HDFS-3608
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 2.0.1-alpha
>            Reporter: Colin Patrick McCabe
>            Assignee: Colin Patrick McCabe
>            Priority: Minor
>
> Currently in fuse_dfs, if one kinits as some principal "foo" and then does some operation on fuse_dfs, then kdestroy and kinit as some principal "bar", subsequent operations done via fuse_dfs will still use cached credentials for "foo". The reason for this is that fuse_dfs caches Filesystem instances using the UID of the user running the command as the key into the cache.  This is a very uncommon scenario, since it's pretty uncommon for a single user to want to use credentials for several different principals on the same box.
> However, we can use inotify to detect changes in the Kerberos ticket cache file and force the next operation to create a new FileSystem instance in that case.  This will also require a reference counting mechanism in fuse_dfs so that we can free the FileSystem classes when they refer to previous Kerberos ticket caches.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira