hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hong Tang (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5933) Make it harder to accidentally close a shared DFSClient
Date Thu, 28 May 2009 18:09:45 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714095#action_12714095

Hong Tang commented on HADOOP-5933:

I am not sure if it would be a good idea to alter code execution paths based on logging levels
- this could lead to harder-to-maintain-or-test code, and harder to understand logging messages
(without reading the code, a user would expect debug level logging a superset of info/warn

> Make it harder to accidentally close a shared DFSClient
> -------------------------------------------------------
>                 Key: HADOOP-5933
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5933
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: fs
>    Affects Versions: 0.21.0
>            Reporter: Steve Loughran
>            Priority: Minor
>         Attachments: HADOOP-5933.patch
> Every so often I get stack traces telling me that DFSClient is closed, usually in {{org.apache.hadoop.hdfs.DFSClient.checkOpen()
}} . The root cause of this is usually that one thread has closed a shared fsclient while
another thread still has a reference to it. If the other thread then asks for a new client
it will get one -and the cache repopulated- but if has one already, then I get to see a stack
> It's effectively a race condition between clients in different threads. 

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

View raw message