hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7964) Deadlock in class init.
Date Tue, 10 Jan 2012 21:37:39 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-7964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13183596#comment-13183596
] 

Suresh Srinivas commented on HADOOP-7964:
-----------------------------------------

Daryn, patch looks good. A minor comment:
# Add @VisibleForTesting to SecurityUtil#useIpForTokenService and SecurityUtil#hostResolver.
Consider just adding accessor for useIpForTokenService.

                
> Deadlock in class init.
> -----------------------
>
>                 Key: HADOOP-7964
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7964
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security, util
>    Affects Versions: 0.20.205.0, 0.24.0, 0.23.1, 1.0.0, 1.1.0
>            Reporter: Kihwal Lee
>            Assignee: Daryn Sharp
>            Priority: Blocker
>         Attachments: HADOOP-7964.patch
>
>
> After HADOOP-7808, client-side commands hang occasionally. There are cyclic dependencies
in NetUtils and SecurityUtil class initialization. Upon initial look at the stack trace, two
threads deadlock when they hit the either of class init the same time.

--
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

        

Mime
View raw message