Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <5819347.6761277258751807.JavaMail.jira@thor>
Date: Tue, 22 Jun 2010 22:05:51 -0400 (EDT)
From: "Hudson (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Subject: [jira] Commented: (HDFS-1192) refreshSuperUserGroupsConfiguration
 should use server side configuration for the refresh (for HADOOP-6815)
In-Reply-To: <25024683.11921275944750755.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hudson commented on HDFS-1192:
------------------------------

Integrated in Hadoop-Hdfs-trunk-Commit #317 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-Hdfs-trunk-Commit/317/])
    HDFS-1192. refreshSuperUserGroupsConfiguration should use server side configuration for the refresh (for HADOOP-6815)


> 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
>         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.