[
https://issues.apache.org/jira/browse/HADOOP-10475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13965851#comment-13965851
]
Daryn Sharp commented on HADOOP-10475:
--------------------------------------
No, UGI synchronization is not trustworthy. Calling {{UGI.getCurrentUser()}}
twice will return you two distinct objects which means synchronization is often
worthless. I've contemplated multiple ways to fix this but haven't had time to
devote to the task. In the scope of this jira, you may want to synch on the
Subject which is indeed shared between UGI instances.
> ConcurrentModificationException in
> AbstractDelegationTokenSelector.selectToken()
> --------------------------------------------------------------------------------
>
> Key: HADOOP-10475
> URL: https://issues.apache.org/jira/browse/HADOOP-10475
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 2.4.0
> Reporter: Arpit Gupta
> Assignee: Jing Zhao
> Fix For: 2.5.0
>
> Attachments: HADOOP-10475.000.patch, HADOOP-10475.001.patch,
> HADOOP-10475.002.patch
>
>
> While running a hive job on a HA cluster saw ConcurrentModificationException
> in AbstractDelegationTokenSelector.selectToken()
--
This message was sent by Atlassian JIRA
(v6.2#6252)
