-
Notifications
You must be signed in to change notification settings - Fork 8.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HDFS-17452 : DfsRouterAdmin RefreshCallQueue fails when authorization is enabled #6982
base: trunk
Are you sure you want to change the base?
Conversation
💔 -1 overall
This message was automatically generated. |
Configuration conf = getConf(); | ||
conf.set(CommonConfigurationKeys.HADOOP_SECURITY_SERVICE_USER_NAME_KEY, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why i did not found HADOOP_SECURITY_SERVICE_USER_NAME_KEY in CommonConfigurationKeys?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is set when the refreshcallqueue is executed. For reference in DFSAdmin we handle it this way
hadoop/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/tools/DFSAdmin.java
Line 1875 in b5f8899
conf.set(CommonConfigurationKeys.HADOOP_SECURITY_SERVICE_USER_NAME_KEY, |
Also the key is defined in
Line 668 in b5f8899
public static final String HADOOP_SECURITY_SERVICE_USER_NAME_KEY = |
Description of PR
Adding the kerberos principal key for Router refreshCallQueue command
How was this patch tested?
On a federated hadoop cluster kerberos was enabled and the command failed. After locally making the change and testing with hadoop jar the command was successful.