[
https://issues.apache.org/jira/browse/YARN-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wangda Tan updated YARN-2826:
-----------------------------
Attachment: YARN-2826-1.patch
Thanks for [~sidharta-s] for reporting this issue.
Attached a fix for this.
Offline discussed with [~xgong], he pointed me what happened, thanks to Xuan!
What really happened is
{{Groups.getUserToGroupsMappingServiceWithLoadedConfiguration(this.conf)}}
overwrites the Groups initialized in doSecureLogin. So we should make sure
doSecureLogin happens after
{{getUserToGroupsMappingServiceWithLoadedConfiguration}}.
And also, HA configuration initialization should happen after configuration
initialization, also put it to correct position as well.
> User-Group mappings not updated by RM when a user is removed from a group.
> --------------------------------------------------------------------------
>
> Key: YARN-2826
> URL: https://issues.apache.org/jira/browse/YARN-2826
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: sidharta seethana
> Assignee: Wangda Tan
> Priority: Critical
> Attachments: YARN-2826-1.patch
>
>
> Removing a user from a group isn't reflected in getGroups even after a
> refresh. The following sequence fails in step 7.
> 1) add test_user to a machine with group1
> 2) add test_user to group2 on the machine
> 3) yarn rmadmin -refreshUserToGroupsMappings (expected to refresh user to
> group mappings)
> 4) yarn rmadmin -getGroups test_user (and ensure that user is in group2)
> 5) remove user from group2 on the machine
> 6) yarn rmadmin -refreshUserToGroupsMappings (expected to refresh user to
> group mappings)
> 7) yarn rmadmin -getGroups test_user (and ensure that user NOT in group2)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
