hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Patrick McCabe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2249) Group changes cause FUSE-DFS I/O error
Date Wed, 03 Oct 2012 19:50:07 GMT

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

Colin Patrick McCabe commented on HDFS-2249:

I agree that this is not fuse-dfs specific.

I looked at Groups.java, and it seems that we expire the groups cache after a certain length
of time.  The timeout is configurable as {{hadoop.security.groups.cache.secs}}, which defaults
to 5 minutes.  I don't think anyone is planning on changing this behavior, so should we close
this JIRA?
> Group changes cause FUSE-DFS I/O error
> --------------------------------------
>                 Key: HDFS-2249
>                 URL: https://issues.apache.org/jira/browse/HDFS-2249
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: fuse-dfs
>            Reporter: Brian Bockelman
>            Assignee: Pete Wyckoff
> If a user utilizes the FUSE mount, then has a group change, they will be unable to write
into FUSE using the new group information.
> To duplicate (assuming user brian starts only in group brian):
> 1) Write file into FUSE (or do any other action)
> 2) Add user brian to group brian2
> 3) chown anything brian owns to brian:brian2.  The error message that gets passed along
> [brian@red ~]$ chown brian:brian2 /mnt/hadoop/user/brian/test_group_perms2
> chown: changing ownership of `/mnt/hadoop/user/brian/test_group_perms2': Input/output
> I believe this is due to the fact that group information is only looked up at NN connection
> If you then remount the FUSE mount, the chown command succeeds.

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

View raw message