[
https://issues.apache.org/jira/browse/HDFS-14418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16815234#comment-16815234
]
Adam Antal commented on HDFS-14418:
-----------------------------------
Digged down a bit to check whether there was some discussion earlier about that
double {{checkSuperuserPrivilage()}}.
Well, not really...
It has been committed in HDFS-6386, where the EZ got introduced. To sum up the
thread: as they have decided to creating an EZ should be a su-operation, they
added the double checks, and following reviews did not pay attention.
Anyways, later in HDFS-7529, they detected this danger that they should
minimize these operations while holding lock.
> Remove redundant super user priveledge checks from namenode.
> ------------------------------------------------------------
>
> Key: HDFS-14418
> URL: https://issues.apache.org/jira/browse/HDFS-14418
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Ayush Saxena
> Assignee: Ayush Saxena
> Priority: Major
> Attachments: HDFS-14418-01.patch, HDFS-14418-02.patch
>
>
> There are couple of methods that unnecessarily double checks super user
> privileged at namenode, which can reduced to single.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
