You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "Owen O'Malley (JIRA)" <ji...@apache.org> on 2010/10/11 07:51:33 UTC

[jira] Resolved: (HDFS-1192) refreshSuperUserGroupsConfiguration should use server side configuration for the refresh (for HADOOP-6815)

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

Owen O'Malley resolved HDFS-1192.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 0.22.0
     Hadoop Flags: [Reviewed]

This jira wasn't closed when the code was committed.

> refreshSuperUserGroupsConfiguration should use server side configuration for the refresh (for HADOOP-6815)
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-1192
>                 URL: https://issues.apache.org/jira/browse/HDFS-1192
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Boris Shkolnik
>            Assignee: Boris Shkolnik
>             Fix For: 0.22.0
>
>         Attachments: HDFS-1192-1.patch, HDFS-1192-10.patch, HDFS-1192-9.patch
>
>
> Currently refreshSuperUserGroupsConfiguration is using client side Configuration.
> One of the issues with this is that if the cluster is restarted it will loose the "refreshed' values (unless they are copied to the NameNode/JobTracker machine).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.