[
https://issues.apache.org/jira/browse/HDFS-13749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16568693#comment-16568693
]
Plamen Jeliazkov commented on HDFS-13749:
-----------------------------------------
Is there a particular reason that superuser privileges are required for getting
the service status?
I can't seem to find one other than that HAAdmin generally requires it.
We could simple re-use _NameNodeRpcServer.getServiceStatus()_ if we can
eliminate the superuser privilege requirement.
Otherwise, if you had to add a new RPC call, another possibility is to reuse
_NameNode.getServiceState()_ which is a fast call and does not require
superuser privileges already.
> 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]
