[
https://issues.apache.org/jira/browse/HDFS-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107470#comment-13107470
]
Steve Loughran commented on HDFS-925:
-------------------------------------
Given that in 0.20.x there's a hack to get a private client and there's a
proper API for this in 0.21+, I am going to propose closing this as a WONTFIX.
Instead move services like the JT and everything in the Mini clusters to using
private instances that are closed when the in-VM clusters are terminated.
> 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
> Attachments: HADOOP-5933.patch, HADOOP-5933.patch, HDFS-925.patch,
> HDFS-925.patch, HDFS-925.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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
