[
https://issues.apache.org/jira/browse/HDFS-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13081285#comment-13081285
]
Todd Lipcon commented on HDFS-2229:
-----------------------------------
jcarder will detect if a lock order is inverted regardless of which threads are
running - ie it can't tell if lock order A>B is used before a thread's started
and B>A is used only after it's started. So, it might be a false positive, but
if it's possible to make the ordering always consistent, it would be better, no?
I'm running against trunk from last Thurs or Fri - haven't updated yet today.
> Deadlock in NameNode
> --------------------
>
> Key: HDFS-2229
> URL: https://issues.apache.org/jira/browse/HDFS-2229
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs client
> Affects Versions: 0.23.0
> Reporter: Vinod Kumar Vavilapalli
> Priority: Blocker
> Attachments: cycle1.png, cycle2.png, h2229_20110807.patch
>
>
> Either I am doing something incredibly stupid, or something about my
> environment is completely weird, or may be it really is a valid bug. I am
> running a NameNode deadlock consistently with 0.23 HDFS. I could never start
> NN successfully.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
