hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-864) Potential deadlock rolling edit logs
Date Mon, 04 Jan 2010 20:59:54 GMT

    [ https://issues.apache.org/jira/browse/HDFS-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796353#action_12796353

Todd Lipcon commented on HDFS-864:

Yea, from what I read on that wiki page you wrote, JSure sounds like it would help with this.
I found these deadlocks using jcarder, which works at runtime to detect lock order inversions
with a bit of overhead. I had to make a few changes to jcarder ( http://github.com/toddlipcon/jcarder/tree/cloudera
) but at this point it's very effective for this and doesn't require any extra development
effort. Once those changes get incorporated into a jcarder release, I hope to get it integrated
into the Hudson test-patch.

> Potential deadlock rolling edit logs
> ------------------------------------
>                 Key: HDFS-864
>                 URL: https://issues.apache.org/jira/browse/HDFS-864
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 0.22.0
>            Reporter: Todd Lipcon
>         Attachments: cycle.png
> FSEditLog.rollEditLog locks the log, then the FSImage. FSImage.close locks the image,
then the log.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message