hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] Moved: (HDFS-925) Make it harder to accidentally close a shared DFSClient
Date Tue, 26 Jan 2010 13:32:34 GMT

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

Steve Loughran moved HADOOP-5933 to HDFS-925:
---------------------------------------------

          Component/s:     (was: fs)
                       hdfs client
        Fix Version/s:     (was: 0.22.0)
                       0.22.0
    Affects Version/s:     (was: 0.21.0)
                       0.21.0
                  Key: HDFS-925  (was: HADOOP-5933)
              Project: Hadoop HDFS  (was: Hadoop Common)

> 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
>            Priority: Minor
>             Fix For: 0.22.0
>
>         Attachments: HADOOP-5933.patch, 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
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.


Mime
View raw message