[ https://issues.apache.org/jira/browse/HDFS-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976156#action_12976156 ]
Konstantin Shvachko commented on HDFS-925: ------------------------------------------ Is this still a problem? Could you please provide a test case for the failure condition. In the patch I didn't like that you effectively pass a message via the Exception variable. > Make it harder to accidentally close a shared DFSClient > ------------------------------------------------------- > > Key: HDFS-925 > URL: https://issues.apache.org/jira/browse/HDFS-925 > Project: Hadoop HDFS > Issue Type: Improvement > Components: hdfs client > Affects Versions: 0.21.0 > Reporter: Steve Loughran > Assignee: Steve Loughran > Priority: Minor > Fix For: 0.22.0 > > Attachments: HADOOP-5933.patch, HADOOP-5933.patch, HDFS-925.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 trace. > 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.