[
https://issues.apache.org/jira/browse/HDFS-13749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16568813#comment-16568813
]
Plamen Jeliazkov commented on HDFS-13749:
-----------------------------------------
I think eliminating superuser privileges from _getServiceStatus_ actually makes
sense. [~shv], thoughts?
My reasoning:
(1) - _NameNodeRpcServer.setSafeMode_ only requires superuser privileges for
setting SafeMode. Getting SafeMode status does not require superuser.
(2) - _DFSAdmin.report_ does not require superuser privileges despite being an
"*Admin" class.
(3) - I don't see any harm in exposing the NameNode's service status to a
non-superuser.
> Implement a new client protocol method to get NameNode state
> ------------------------------------------------------------
>
> Key: HDFS-13749
> URL: https://issues.apache.org/jira/browse/HDFS-13749
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Chao Sun
> Assignee: Chao Sun
> Priority: Major
> Attachments: HDFS-13749-HDFS-12943.000.patch
>
>
> Currently {{HAServiceProtocol#getServiceStatus}} requires super user
> privilege. Therefore, as a temporary solution, in HDFS-12976 we discover
> NameNode state by calling {{reportBadBlocks}}. Here, we'll properly implement
> this by adding a new method in client protocol to get the NameNode state.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
