[
https://issues.apache.org/jira/browse/FLUME-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114173#comment-13114173
]
RenHaojie edited comment on FLUME-171 at 9/25/11 8:22 AM:
----------------------------------------------------------
Just change the order of a line can solve the deadlock.
Although the status of some logical nodes could be wrong while mapping physical
node and logical node.
Anyway,it will be correct afer mapping.
This is acceptable,isn't it?
was (Author: eskimoooo):
Just change the order of a line can solve the deadlock.
Althougth the status of some logical nodes could be wrong while mapping
physical node and logical node.
Anyway,it will be correct afer mapping.
This is acceptable,isn't it?
> Potential deadlock between StatusManager and TranslatingConfigurationManager
> ----------------------------------------------------------------------------
>
> Key: FLUME-171
> URL: https://issues.apache.org/jira/browse/FLUME-171
> Project: Flume
> Issue Type: Bug
> Components: Master
> Affects Versions: v0.9.1
> Reporter: Jonathan Hsieh
> Priority: Critical
> Fix For: v0.9.5
>
> Attachments: jstack.master, master_deadlock_on_map.patch
>
>
> JCarder detected this lock acquisition cycle.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
