Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
Reviewed
Description
Currently refreshSuperUserGroupsConfiguration is using client side Configuration.
One of the issues with this is that if the cluster is restarted it will loose the "refreshed' values (unless they are copied to the NameNode/JobTracker machine).
Attachments
Attachments
Issue Links
- blocks
-
HADOOP-6815 refreshSuperUserGroupsConfiguration should use server side configuration for the refresh
- Closed
- is part of
-
HADOOP-6815 refreshSuperUserGroupsConfiguration should use server side configuration for the refresh
- Closed