Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Message-ID: <16848480.166761278043491398.JavaMail.jira@thor>
Date: Fri, 2 Jul 2010 00:04:51 -0400 (EDT)
From: "Todd Lipcon (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Subject: [jira] Resolved: (HDFS-796) 4-thread Deadlock in DFS Client
In-Reply-To: <1898438478.1259621600687.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HDFS-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Todd Lipcon resolved HDFS-796.
------------------------------

    Resolution: Duplicate

Never saw this come back, I think its dup of HDFS-723

> 4-thread Deadlock in DFS Client
> -------------------------------
>
>                 Key: HDFS-796
>                 URL: https://issues.apache.org/jira/browse/HDFS-796
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs client
>            Reporter: Todd Lipcon
>         Attachments: deadlock.txt
>
>
> Managed to get this deadlock running TestHDFSCLI this afternoon. It seems to be related to a signal, though I don't recall hitting ^C. The one thing I did that might help trigger this was reduce the Thread.sleep(1000) in LeaseChecker down to a shorter interval.
> "SIGTERM handler":
>   waiting to lock monitor 0x0000000041f3bd18 (object 0x00007fa43c132328, a java.lang.Class),
>   which is held by "SIGINT handler"
> "SIGINT handler":
>   waiting to lock monitor 0x000000004230b410 (object 0x00007fa441603030, a org.apache.hadoop.fs.FileSystem$Cache$ClientFinalizer),
>   which is held by "Thread-3"
> "Thread-3":
>   waiting to lock monitor 0x00007fa4341fe3f0 (object 0x00007fa441d3b150, a org.apache.hadoop.hdfs.DFSClient$DFSOutputStream),
>   which is held by "main"
> "main":
>   waiting to lock monitor 0x0000000042b1ec80 (object 0x00007fa44167eff8, a org.apache.hadoop.hdfs.DFSClient$LeaseChecker),
>   which is held by "Thread-3"

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