[
https://issues.apache.org/jira/browse/HADOOP-8050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207239#comment-13207239
]
Luke Lu commented on HADOOP-8050:
---------------------------------
static analysis is hopeless for this case, as the compiler needs to know all
the possible dynamic bindings of metrics source before hand. I recall that Todd
ran jcarder (dynamic deadlock finder) on metrics2 in trunk and didn't find the
issue, probably due to a lack of test coverage in the jmx metrics serving
(there are some tests but we need to make sure snapshot thread happens in the
tests as well), or the fact that metrics sources can be created via annotations.
> Deadlock in metrics
> -------------------
>
> Key: HADOOP-8050
> URL: https://issues.apache.org/jira/browse/HADOOP-8050
> Project: Hadoop Common
> Issue Type: Bug
> Components: metrics
> Affects Versions: 0.20.204.0, 0.20.205.0, 0.23.0, 1.0.0
> Reporter: Kihwal Lee
> Assignee: Kihwal Lee
> Fix For: 1.1.0, 1.0.1
>
> Attachments: hadoop-8050-branch-1.patch.txt,
> hadoop-8050-branch-1.patch.txt, hadoop-8050-branch-1.patch.txt,
> hadoop-8050-branch-1.patch.txt, hadoop-8050-trunk.patch.txt,
> hadoop-8050-trunk.patch.txt, hadoop-8050-trunk.patch.txt,
> hadoop-8050.patch.txt
>
>
> The metrics serving thread and the periodic snapshot thread can deadlock.
> It happened a few times on one of namenodes we have. When it happens RPC
> works but the web ui and hftp stop working. I haven't look at the trunk too
> closely, but it might happen there too.
--
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
