You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Daryn Sharp (Created) (JIRA)" <ji...@apache.org> on 2011/11/23 19:13:43 UTC
[jira] [Created] (HADOOP-7854) UGI getCurrentUser is not
synchronized
UGI getCurrentUser is not synchronized
--------------------------------------
Key: HADOOP-7854
URL: https://issues.apache.org/jira/browse/HADOOP-7854
Project: Hadoop Common
Issue Type: Bug
Components: security
Affects Versions: 0.20.205.1
Reporter: Daryn Sharp
Assignee: Daryn Sharp
Priority: Critical
Sporadic {{ConcurrentModificationExceptions}} are originating from {{UGI.getCurrentUser}} when it needs to create a new instance. The problem was specifically observed in a JT under heavy load when a post-job cleanup is accessing the UGI while a new job is being processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7854) UGI getCurrentUser is not
synchronized
Posted by "Jitendra Nath Pandey (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jitendra Nath Pandey updated HADOOP-7854:
-----------------------------------------
Target Version/s: 0.24.0, 1.0.0 (was: 1.0.0, 0.24.0)
Status: Patch Available (was: Reopened)
> UGI getCurrentUser is not synchronized
> --------------------------------------
>
> Key: HADOOP-7854
> URL: https://issues.apache.org/jira/browse/HADOOP-7854
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 1.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Fix For: 1.0.0
>
> Attachments: HADOOP-7854-trunk.patch, HADOOP-7854.patch
>
>
> Sporadic {{ConcurrentModificationExceptions}} are originating from {{UGI.getCurrentUser}} when it needs to create a new instance. The problem was specifically observed in a JT under heavy load when a post-job cleanup is accessing the UGI while a new job is being processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7854) UGI getCurrentUser is not
synchronized
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160572#comment-13160572 ]
Hudson commented on HADOOP-7854:
--------------------------------
Integrated in Hadoop-Mapreduce-0.23-Commit #248 (See [https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Commit/248/])
Merged r1208926 from trunk for HADOOP-7854.
jitendra : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1208929
Files :
* /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/UserGroupInformation.java
> UGI getCurrentUser is not synchronized
> --------------------------------------
>
> Key: HADOOP-7854
> URL: https://issues.apache.org/jira/browse/HADOOP-7854
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 1.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Fix For: 1.0.0
>
> Attachments: HADOOP-7854-trunk.patch, HADOOP-7854.patch
>
>
> Sporadic {{ConcurrentModificationExceptions}} are originating from {{UGI.getCurrentUser}} when it needs to create a new instance. The problem was specifically observed in a JT under heavy load when a post-job cleanup is accessing the UGI while a new job is being processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7854) UGI getCurrentUser is not
synchronized
Posted by "Daryn Sharp (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daryn Sharp updated HADOOP-7854:
--------------------------------
Status: Patch Available (was: Open)
> UGI getCurrentUser is not synchronized
> --------------------------------------
>
> Key: HADOOP-7854
> URL: https://issues.apache.org/jira/browse/HADOOP-7854
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 0.20.205.1
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Attachments: HADOOP-7854.patch
>
>
> Sporadic {{ConcurrentModificationExceptions}} are originating from {{UGI.getCurrentUser}} when it needs to create a new instance. The problem was specifically observed in a JT under heavy load when a post-job cleanup is accessing the UGI while a new job is being processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7854) UGI getCurrentUser is not
synchronized
Posted by "Daryn Sharp (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daryn Sharp updated HADOOP-7854:
--------------------------------
Attachment: HADOOP-7854.patch
Simply added synchronized keyword. I'm not sure how I can write a unit test...
> UGI getCurrentUser is not synchronized
> --------------------------------------
>
> Key: HADOOP-7854
> URL: https://issues.apache.org/jira/browse/HADOOP-7854
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 0.20.205.1
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Attachments: HADOOP-7854.patch
>
>
> Sporadic {{ConcurrentModificationExceptions}} are originating from {{UGI.getCurrentUser}} when it needs to create a new instance. The problem was specifically observed in a JT under heavy load when a post-job cleanup is accessing the UGI while a new job is being processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7854) UGI getCurrentUser is not
synchronized
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160869#comment-13160869 ]
Hudson commented on HADOOP-7854:
--------------------------------
Integrated in Hadoop-Hdfs-HAbranch-build #2 (See [https://builds.apache.org/job/Hadoop-Hdfs-HAbranch-build/2/])
Merged r1208926 from trunk for HADOOP-7854.
jitendra : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1208929
Files :
* /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/UserGroupInformation.java
> UGI getCurrentUser is not synchronized
> --------------------------------------
>
> Key: HADOOP-7854
> URL: https://issues.apache.org/jira/browse/HADOOP-7854
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 1.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Fix For: 0.23.1, 1.0.0
>
> Attachments: HADOOP-7854-trunk.patch, HADOOP-7854.patch
>
>
> Sporadic {{ConcurrentModificationExceptions}} are originating from {{UGI.getCurrentUser}} when it needs to create a new instance. The problem was specifically observed in a JT under heavy load when a post-job cleanup is accessing the UGI while a new job is being processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7854) UGI getCurrentUser is not
synchronized
Posted by "Kihwal Lee (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156052#comment-13156052 ]
Kihwal Lee commented on HADOOP-7854:
------------------------------------
I think TRUNK has the same issue.
> UGI getCurrentUser is not synchronized
> --------------------------------------
>
> Key: HADOOP-7854
> URL: https://issues.apache.org/jira/browse/HADOOP-7854
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 0.20.205.1
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Attachments: HADOOP-7854.patch
>
>
> Sporadic {{ConcurrentModificationExceptions}} are originating from {{UGI.getCurrentUser}} when it needs to create a new instance. The problem was specifically observed in a JT under heavy load when a post-job cleanup is accessing the UGI while a new job is being processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7854) UGI getCurrentUser is not
synchronized
Posted by "Matt Foley (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Foley updated HADOOP-7854:
-------------------------------
Target Version/s: 0.23.1, 1.0.0 (was: 1.0.0, 0.24.0)
Fix Version/s: 0.23.1
Corrected Fix Versions and Target Versions to correspond to actual commits.
> UGI getCurrentUser is not synchronized
> --------------------------------------
>
> Key: HADOOP-7854
> URL: https://issues.apache.org/jira/browse/HADOOP-7854
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 1.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Fix For: 0.23.1, 1.0.0
>
> Attachments: HADOOP-7854-trunk.patch, HADOOP-7854.patch
>
>
> Sporadic {{ConcurrentModificationExceptions}} are originating from {{UGI.getCurrentUser}} when it needs to create a new instance. The problem was specifically observed in a JT under heavy load when a post-job cleanup is accessing the UGI while a new job is being processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7854) UGI getCurrentUser is not
synchronized
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160863#comment-13160863 ]
Hudson commented on HADOOP-7854:
--------------------------------
Integrated in Hadoop-Hdfs-0.23-Build #94 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/94/])
Merged r1208926 from trunk for HADOOP-7854.
jitendra : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1208929
Files :
* /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/UserGroupInformation.java
> UGI getCurrentUser is not synchronized
> --------------------------------------
>
> Key: HADOOP-7854
> URL: https://issues.apache.org/jira/browse/HADOOP-7854
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 1.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Fix For: 0.23.1, 1.0.0
>
> Attachments: HADOOP-7854-trunk.patch, HADOOP-7854.patch
>
>
> Sporadic {{ConcurrentModificationExceptions}} are originating from {{UGI.getCurrentUser}} when it needs to create a new instance. The problem was specifically observed in a JT under heavy load when a post-job cleanup is accessing the UGI while a new job is being processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7854) UGI getCurrentUser is not
synchronized
Posted by "Daryn Sharp (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156307#comment-13156307 ]
Daryn Sharp commented on HADOOP-7854:
-------------------------------------
Per Kihwal's comment, the exception occurs when two unsynchronized callers attempt to use the {{Subject}} from the current context.
> UGI getCurrentUser is not synchronized
> --------------------------------------
>
> Key: HADOOP-7854
> URL: https://issues.apache.org/jira/browse/HADOOP-7854
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 0.20.205.1
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Attachments: HADOOP-7854.patch
>
>
> Sporadic {{ConcurrentModificationExceptions}} are originating from {{UGI.getCurrentUser}} when it needs to create a new instance. The problem was specifically observed in a JT under heavy load when a post-job cleanup is accessing the UGI while a new job is being processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7854) UGI getCurrentUser is not
synchronized
Posted by "Jitendra Nath Pandey (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156468#comment-13156468 ]
Jitendra Nath Pandey commented on HADOOP-7854:
----------------------------------------------
I think we should commit it. +1
> UGI getCurrentUser is not synchronized
> --------------------------------------
>
> Key: HADOOP-7854
> URL: https://issues.apache.org/jira/browse/HADOOP-7854
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 0.20.205.1
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Attachments: HADOOP-7854.patch
>
>
> Sporadic {{ConcurrentModificationExceptions}} are originating from {{UGI.getCurrentUser}} when it needs to create a new instance. The problem was specifically observed in a JT under heavy load when a post-job cleanup is accessing the UGI while a new job is being processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7854) UGI getCurrentUser is not
synchronized
Posted by "Mahadev konar (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160483#comment-13160483 ]
Mahadev konar commented on HADOOP-7854:
---------------------------------------
Can this be checked into 0.23 branch as well?
> UGI getCurrentUser is not synchronized
> --------------------------------------
>
> Key: HADOOP-7854
> URL: https://issues.apache.org/jira/browse/HADOOP-7854
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 1.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Fix For: 1.0.0
>
> Attachments: HADOOP-7854-trunk.patch, HADOOP-7854.patch
>
>
> Sporadic {{ConcurrentModificationExceptions}} are originating from {{UGI.getCurrentUser}} when it needs to create a new instance. The problem was specifically observed in a JT under heavy load when a post-job cleanup is accessing the UGI while a new job is being processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7854) UGI getCurrentUser is not
synchronized
Posted by "Hadoop QA (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156027#comment-13156027 ]
Hadoop QA commented on HADOOP-7854:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12504902/HADOOP-7854.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
-1 patch. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/399//console
This message is automatically generated.
> UGI getCurrentUser is not synchronized
> --------------------------------------
>
> Key: HADOOP-7854
> URL: https://issues.apache.org/jira/browse/HADOOP-7854
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 0.20.205.1
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Attachments: HADOOP-7854.patch
>
>
> Sporadic {{ConcurrentModificationExceptions}} are originating from {{UGI.getCurrentUser}} when it needs to create a new instance. The problem was specifically observed in a JT under heavy load when a post-job cleanup is accessing the UGI while a new job is being processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7854) UGI getCurrentUser is not
synchronized
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160568#comment-13160568 ]
Hudson commented on HADOOP-7854:
--------------------------------
Integrated in Hadoop-Mapreduce-trunk-Commit #1372 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/1372/])
HADOOP-7854. UGI getCurrentUser is not synchronized. Contributed by Daryn Sharp.
jitendra : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1208926
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/UserGroupInformation.java
> UGI getCurrentUser is not synchronized
> --------------------------------------
>
> Key: HADOOP-7854
> URL: https://issues.apache.org/jira/browse/HADOOP-7854
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 1.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Fix For: 1.0.0
>
> Attachments: HADOOP-7854-trunk.patch, HADOOP-7854.patch
>
>
> Sporadic {{ConcurrentModificationExceptions}} are originating from {{UGI.getCurrentUser}} when it needs to create a new instance. The problem was specifically observed in a JT under heavy load when a post-job cleanup is accessing the UGI while a new job is being processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7854) UGI getCurrentUser is not
synchronized
Posted by "Todd Lipcon (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156314#comment-13156314 ]
Todd Lipcon commented on HADOOP-7854:
-------------------------------------
Should we also be reporting this as a JDK bug? Seems like it should be up to the JDK to synchronize this.
> UGI getCurrentUser is not synchronized
> --------------------------------------
>
> Key: HADOOP-7854
> URL: https://issues.apache.org/jira/browse/HADOOP-7854
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 0.20.205.1
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Attachments: HADOOP-7854.patch
>
>
> Sporadic {{ConcurrentModificationExceptions}} are originating from {{UGI.getCurrentUser}} when it needs to create a new instance. The problem was specifically observed in a JT under heavy load when a post-job cleanup is accessing the UGI while a new job is being processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7854) UGI getCurrentUser is not
synchronized
Posted by "Matt Foley (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Foley updated HADOOP-7854:
-------------------------------
Resolution: Fixed
Fix Version/s: 1.0.0
Status: Resolved (was: Patch Available)
Marking this fixed in 1.0.0 (0.20.205.1), because this patch will prevent the problem from recurring.
If further disposition is required (such as opening bug against JDK), please do so.
Should this be merged to trunk?
> UGI getCurrentUser is not synchronized
> --------------------------------------
>
> Key: HADOOP-7854
> URL: https://issues.apache.org/jira/browse/HADOOP-7854
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 1.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Fix For: 1.0.0
>
> Attachments: HADOOP-7854.patch
>
>
> Sporadic {{ConcurrentModificationExceptions}} are originating from {{UGI.getCurrentUser}} when it needs to create a new instance. The problem was specifically observed in a JT under heavy load when a post-job cleanup is accessing the UGI while a new job is being processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7854) UGI getCurrentUser is not
synchronized
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160908#comment-13160908 ]
Hudson commented on HADOOP-7854:
--------------------------------
Integrated in Hadoop-Mapreduce-trunk #914 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/914/])
HADOOP-7854. UGI getCurrentUser is not synchronized. Contributed by Daryn Sharp.
jitendra : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1208926
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/UserGroupInformation.java
> UGI getCurrentUser is not synchronized
> --------------------------------------
>
> Key: HADOOP-7854
> URL: https://issues.apache.org/jira/browse/HADOOP-7854
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 1.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Fix For: 0.23.1, 1.0.0
>
> Attachments: HADOOP-7854-trunk.patch, HADOOP-7854.patch
>
>
> Sporadic {{ConcurrentModificationExceptions}} are originating from {{UGI.getCurrentUser}} when it needs to create a new instance. The problem was specifically observed in a JT under heavy load when a post-job cleanup is accessing the UGI while a new job is being processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7854) UGI getCurrentUser is not
synchronized
Posted by "Kihwal Lee (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156219#comment-13156219 ]
Kihwal Lee commented on HADOOP-7854:
------------------------------------
See HADOOP-7831 for the actual exception.
> UGI getCurrentUser is not synchronized
> --------------------------------------
>
> Key: HADOOP-7854
> URL: https://issues.apache.org/jira/browse/HADOOP-7854
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 0.20.205.1
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Attachments: HADOOP-7854.patch
>
>
> Sporadic {{ConcurrentModificationExceptions}} are originating from {{UGI.getCurrentUser}} when it needs to create a new instance. The problem was specifically observed in a JT under heavy load when a post-job cleanup is accessing the UGI while a new job is being processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7854) UGI getCurrentUser is not
synchronized
Posted by "Todd Lipcon (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156206#comment-13156206 ]
Todd Lipcon commented on HADOOP-7854:
-------------------------------------
I'm confused - what's throwing the CME? It's a static method and it doesn't touch any class variables...
> UGI getCurrentUser is not synchronized
> --------------------------------------
>
> Key: HADOOP-7854
> URL: https://issues.apache.org/jira/browse/HADOOP-7854
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 0.20.205.1
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Attachments: HADOOP-7854.patch
>
>
> Sporadic {{ConcurrentModificationExceptions}} are originating from {{UGI.getCurrentUser}} when it needs to create a new instance. The problem was specifically observed in a JT under heavy load when a post-job cleanup is accessing the UGI while a new job is being processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7854) UGI getCurrentUser is not
synchronized
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160878#comment-13160878 ]
Hudson commented on HADOOP-7854:
--------------------------------
Integrated in Hadoop-Hdfs-trunk #881 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/881/])
HADOOP-7854. UGI getCurrentUser is not synchronized. Contributed by Daryn Sharp.
jitendra : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1208926
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/UserGroupInformation.java
> UGI getCurrentUser is not synchronized
> --------------------------------------
>
> Key: HADOOP-7854
> URL: https://issues.apache.org/jira/browse/HADOOP-7854
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 1.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Fix For: 0.23.1, 1.0.0
>
> Attachments: HADOOP-7854-trunk.patch, HADOOP-7854.patch
>
>
> Sporadic {{ConcurrentModificationExceptions}} are originating from {{UGI.getCurrentUser}} when it needs to create a new instance. The problem was specifically observed in a JT under heavy load when a post-job cleanup is accessing the UGI while a new job is being processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7854) UGI getCurrentUser is not
synchronized
Posted by "Daryn Sharp (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daryn Sharp updated HADOOP-7854:
--------------------------------
Attachment: HADOOP-7854-trunk.patch
> UGI getCurrentUser is not synchronized
> --------------------------------------
>
> Key: HADOOP-7854
> URL: https://issues.apache.org/jira/browse/HADOOP-7854
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 1.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Fix For: 1.0.0
>
> Attachments: HADOOP-7854-trunk.patch, HADOOP-7854.patch
>
>
> Sporadic {{ConcurrentModificationExceptions}} are originating from {{UGI.getCurrentUser}} when it needs to create a new instance. The problem was specifically observed in a JT under heavy load when a post-job cleanup is accessing the UGI while a new job is being processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7854) UGI getCurrentUser is not
synchronized
Posted by "Daryn Sharp (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156372#comment-13156372 ]
Daryn Sharp commented on HADOOP-7854:
-------------------------------------
Stack trace is in the bug Kihwal mentioned: HADOOP-7831
> UGI getCurrentUser is not synchronized
> --------------------------------------
>
> Key: HADOOP-7854
> URL: https://issues.apache.org/jira/browse/HADOOP-7854
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 0.20.205.1
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Attachments: HADOOP-7854.patch
>
>
> Sporadic {{ConcurrentModificationExceptions}} are originating from {{UGI.getCurrentUser}} when it needs to create a new instance. The problem was specifically observed in a JT under heavy load when a post-job cleanup is accessing the UGI while a new job is being processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7854) UGI getCurrentUser is not
synchronized
Posted by "Jitendra Nath Pandey (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jitendra Nath Pandey updated HADOOP-7854:
-----------------------------------------
Resolution: Fixed
Target Version/s: 0.24.0, 1.0.0 (was: 1.0.0, 0.24.0)
Status: Resolved (was: Patch Available)
Committed to trunk and 23 as well. Thanks to Daryn.
> UGI getCurrentUser is not synchronized
> --------------------------------------
>
> Key: HADOOP-7854
> URL: https://issues.apache.org/jira/browse/HADOOP-7854
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 1.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Fix For: 1.0.0
>
> Attachments: HADOOP-7854-trunk.patch, HADOOP-7854.patch
>
>
> Sporadic {{ConcurrentModificationExceptions}} are originating from {{UGI.getCurrentUser}} when it needs to create a new instance. The problem was specifically observed in a JT under heavy load when a post-job cleanup is accessing the UGI while a new job is being processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7854) UGI getCurrentUser is not
synchronized
Posted by "Hadoop QA (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160471#comment-13160471 ]
Hadoop QA commented on HADOOP-7854:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12505679/HADOOP-7854-trunk.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
-1 javadoc. The javadoc tool appears to have generated 15 warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed unit tests in .
+1 contrib tests. The patch passed contrib unit tests.
Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/417//testReport/
Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/417//console
This message is automatically generated.
> UGI getCurrentUser is not synchronized
> --------------------------------------
>
> Key: HADOOP-7854
> URL: https://issues.apache.org/jira/browse/HADOOP-7854
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 1.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Fix For: 1.0.0
>
> Attachments: HADOOP-7854-trunk.patch, HADOOP-7854.patch
>
>
> Sporadic {{ConcurrentModificationExceptions}} are originating from {{UGI.getCurrentUser}} when it needs to create a new instance. The problem was specifically observed in a JT under heavy load when a post-job cleanup is accessing the UGI while a new job is being processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7854) UGI getCurrentUser is not
synchronized
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160556#comment-13160556 ]
Hudson commented on HADOOP-7854:
--------------------------------
Integrated in Hadoop-Hdfs-0.23-Commit #236 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Commit/236/])
Merged r1208926 from trunk for HADOOP-7854.
jitendra : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1208929
Files :
* /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/UserGroupInformation.java
> UGI getCurrentUser is not synchronized
> --------------------------------------
>
> Key: HADOOP-7854
> URL: https://issues.apache.org/jira/browse/HADOOP-7854
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 1.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Fix For: 1.0.0
>
> Attachments: HADOOP-7854-trunk.patch, HADOOP-7854.patch
>
>
> Sporadic {{ConcurrentModificationExceptions}} are originating from {{UGI.getCurrentUser}} when it needs to create a new instance. The problem was specifically observed in a JT under heavy load when a post-job cleanup is accessing the UGI while a new job is being processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (HADOOP-7854) UGI getCurrentUser is not
synchronized
Posted by "Jitendra Nath Pandey (Reopened) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jitendra Nath Pandey reopened HADOOP-7854:
------------------------------------------
> UGI getCurrentUser is not synchronized
> --------------------------------------
>
> Key: HADOOP-7854
> URL: https://issues.apache.org/jira/browse/HADOOP-7854
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 1.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Fix For: 1.0.0
>
> Attachments: HADOOP-7854-trunk.patch, HADOOP-7854.patch
>
>
> Sporadic {{ConcurrentModificationExceptions}} are originating from {{UGI.getCurrentUser}} when it needs to create a new instance. The problem was specifically observed in a JT under heavy load when a post-job cleanup is accessing the UGI while a new job is being processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7854) UGI getCurrentUser is not
synchronized
Posted by "Mahadev konar (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158122#comment-13158122 ]
Mahadev konar commented on HADOOP-7854:
---------------------------------------
Yes, please merge this to trunk as well.
> UGI getCurrentUser is not synchronized
> --------------------------------------
>
> Key: HADOOP-7854
> URL: https://issues.apache.org/jira/browse/HADOOP-7854
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 1.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Fix For: 1.0.0
>
> Attachments: HADOOP-7854.patch
>
>
> Sporadic {{ConcurrentModificationExceptions}} are originating from {{UGI.getCurrentUser}} when it needs to create a new instance. The problem was specifically observed in a JT under heavy load when a post-job cleanup is accessing the UGI while a new job is being processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7854) UGI getCurrentUser is not
synchronized
Posted by "Daryn Sharp (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156371#comment-13156371 ]
Daryn Sharp commented on HADOOP-7854:
-------------------------------------
Good question. The {{Subject} class appears to generally be thread-safe. It's internally synchronizing and using instances such as {{Collections.synchronizedSet}}. The problem is due to iterators becoming very grumpy when their collection is modified, and {{Subject}} is full of collections that can be accessed directly. I can't find any documentation about whether {{Subject}} is even supposed to be thread-safe. I suspect it is once you lock it down as read-only, but we don't do that.
> UGI getCurrentUser is not synchronized
> --------------------------------------
>
> Key: HADOOP-7854
> URL: https://issues.apache.org/jira/browse/HADOOP-7854
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 0.20.205.1
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Attachments: HADOOP-7854.patch
>
>
> Sporadic {{ConcurrentModificationExceptions}} are originating from {{UGI.getCurrentUser}} when it needs to create a new instance. The problem was specifically observed in a JT under heavy load when a post-job cleanup is accessing the UGI while a new job is being processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7854) UGI getCurrentUser is not
synchronized
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160557#comment-13160557 ]
Hudson commented on HADOOP-7854:
--------------------------------
Integrated in Hadoop-Common-0.23-Commit #238 (See [https://builds.apache.org/job/Hadoop-Common-0.23-Commit/238/])
Merged r1208926 from trunk for HADOOP-7854.
jitendra : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1208929
Files :
* /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/UserGroupInformation.java
> UGI getCurrentUser is not synchronized
> --------------------------------------
>
> Key: HADOOP-7854
> URL: https://issues.apache.org/jira/browse/HADOOP-7854
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 1.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Fix For: 1.0.0
>
> Attachments: HADOOP-7854-trunk.patch, HADOOP-7854.patch
>
>
> Sporadic {{ConcurrentModificationExceptions}} are originating from {{UGI.getCurrentUser}} when it needs to create a new instance. The problem was specifically observed in a JT under heavy load when a post-job cleanup is accessing the UGI while a new job is being processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7854) UGI getCurrentUser is not
synchronized
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160550#comment-13160550 ]
Hudson commented on HADOOP-7854:
--------------------------------
Integrated in Hadoop-Hdfs-trunk-Commit #1422 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/1422/])
HADOOP-7854. UGI getCurrentUser is not synchronized. Contributed by Daryn Sharp.
jitendra : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1208926
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/UserGroupInformation.java
> UGI getCurrentUser is not synchronized
> --------------------------------------
>
> Key: HADOOP-7854
> URL: https://issues.apache.org/jira/browse/HADOOP-7854
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 1.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Fix For: 1.0.0
>
> Attachments: HADOOP-7854-trunk.patch, HADOOP-7854.patch
>
>
> Sporadic {{ConcurrentModificationExceptions}} are originating from {{UGI.getCurrentUser}} when it needs to create a new instance. The problem was specifically observed in a JT under heavy load when a post-job cleanup is accessing the UGI while a new job is being processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7854) UGI getCurrentUser is not
synchronized
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160560#comment-13160560 ]
Hudson commented on HADOOP-7854:
--------------------------------
Integrated in Hadoop-Mapreduce-0.23-Build #111 (See [https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Build/111/])
Merged r1208926 from trunk for HADOOP-7854.
jitendra : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1208929
Files :
* /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/UserGroupInformation.java
> UGI getCurrentUser is not synchronized
> --------------------------------------
>
> Key: HADOOP-7854
> URL: https://issues.apache.org/jira/browse/HADOOP-7854
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 1.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Fix For: 1.0.0
>
> Attachments: HADOOP-7854-trunk.patch, HADOOP-7854.patch
>
>
> Sporadic {{ConcurrentModificationExceptions}} are originating from {{UGI.getCurrentUser}} when it needs to create a new instance. The problem was specifically observed in a JT under heavy load when a post-job cleanup is accessing the UGI while a new job is being processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7854) UGI getCurrentUser is not
synchronized
Posted by "Jitendra Nath Pandey (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156364#comment-13156364 ]
Jitendra Nath Pandey commented on HADOOP-7854:
----------------------------------------------
It does seem like a JDK issue, do you have a stack trace for the CME?
> UGI getCurrentUser is not synchronized
> --------------------------------------
>
> Key: HADOOP-7854
> URL: https://issues.apache.org/jira/browse/HADOOP-7854
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 0.20.205.1
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Attachments: HADOOP-7854.patch
>
>
> Sporadic {{ConcurrentModificationExceptions}} are originating from {{UGI.getCurrentUser}} when it needs to create a new instance. The problem was specifically observed in a JT under heavy load when a post-job cleanup is accessing the UGI while a new job is being processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7854) UGI getCurrentUser is not
synchronized
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160553#comment-13160553 ]
Hudson commented on HADOOP-7854:
--------------------------------
Integrated in Hadoop-Common-trunk-Commit #1349 (See [https://builds.apache.org/job/Hadoop-Common-trunk-Commit/1349/])
HADOOP-7854. UGI getCurrentUser is not synchronized. Contributed by Daryn Sharp.
jitendra : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1208926
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/UserGroupInformation.java
> UGI getCurrentUser is not synchronized
> --------------------------------------
>
> Key: HADOOP-7854
> URL: https://issues.apache.org/jira/browse/HADOOP-7854
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 1.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Fix For: 1.0.0
>
> Attachments: HADOOP-7854-trunk.patch, HADOOP-7854.patch
>
>
> Sporadic {{ConcurrentModificationExceptions}} are originating from {{UGI.getCurrentUser}} when it needs to create a new instance. The problem was specifically observed in a JT under heavy load when a post-job cleanup is accessing the UGI while a new job is being processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7854) UGI getCurrentUser is not
synchronized
Posted by "Jitendra Nath Pandey (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jitendra Nath Pandey updated HADOOP-7854:
-----------------------------------------
Target Version/s: 0.24.0, 1.0.0 (was: 1.0.0)
> UGI getCurrentUser is not synchronized
> --------------------------------------
>
> Key: HADOOP-7854
> URL: https://issues.apache.org/jira/browse/HADOOP-7854
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 1.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Fix For: 1.0.0
>
> Attachments: HADOOP-7854-trunk.patch, HADOOP-7854.patch
>
>
> Sporadic {{ConcurrentModificationExceptions}} are originating from {{UGI.getCurrentUser}} when it needs to create a new instance. The problem was specifically observed in a JT under heavy load when a post-job cleanup is accessing the UGI while a new job is being processed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira