hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4593) Deadlock in AbstractService.getConfig()
Date Mon, 29 Feb 2016 21:37:18 GMT

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

Steve Loughran commented on YARN-4593:
--------------------------------------

No tests. I'd have to think of a way to recreate the deadlock then make sure it was gone.
someone will need to look at the code instead

> Deadlock in AbstractService.getConfig()
> ---------------------------------------
>
>                 Key: YARN-4593
>                 URL: https://issues.apache.org/jira/browse/YARN-4593
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: yarn
>    Affects Versions: 2.7.2
>         Environment: AM restarting on kerberized cluster
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>         Attachments: YARN-4593-001.patch
>
>
> SLIDER-1052 has found a deadlock which can arise in it during AM restart. Looking at
the thread trace, one of the blockages is actually {{AbstractService.getConfig()}} —this
is synchronized and so blocked.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message