Return-Path: X-Original-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3699E17EB2 for ; Wed, 5 Nov 2014 22:09:35 +0000 (UTC) Received: (qmail 7321 invoked by uid 500); 5 Nov 2014 22:09:34 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 7223 invoked by uid 500); 5 Nov 2014 22:09:34 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-dev@hadoop.apache.org Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 7164 invoked by uid 99); 5 Nov 2014 22:09:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Nov 2014 22:09:34 +0000 Date: Wed, 5 Nov 2014 22:09:34 +0000 (UTC) From: "Eric Payne (JIRA)" To: hdfs-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HDFS-7362) Proxy user refresh won't modify or remove existing groups or hosts from super user list MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Eric Payne created HDFS-7362: -------------------------------- Summary: Proxy user refresh won't modify or remove existing groups or hosts from super user list Key: HDFS-7362 URL: https://issues.apache.org/jira/browse/HDFS-7362 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 2.5.0 Reporter: Eric Payne Assignee: Eric Payne 2.x added a new DefaultImpersonationProvider class for reading the superuser configuration. In this class, once the host and group properties for a proxyuser are defined, they cannot be removed or modified without bouncing the daemon. As long as the config is updated correctly the first time, this problem won't manifest itself. Once defined, these properties don't tend to change. However, if the properties are mis-entered the first time, restarting the NN/RM/JHS/etc will be necessary to correctly re-read the config. An admin refresh won't do it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)