hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7973) DistributedFileSystem close has severe consequences
Date Fri, 20 Jan 2012 14:38:40 GMT

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

Daryn Sharp commented on HADOOP-7973:
-------------------------------------

With unbalanced closes, the filesystem will essentially never be closed unless {{closeAll}}
or {{closeAllForUGI}} is called.  Open files & their leases will remain open.  It's a
more complicated change that will alter the behavior of 205 with possibly unforeseen consequences.
 I'm attempting to only restore 204 behavior with this jira.

I know the private conf value is a bit of a hack, but I see no other way to allow unique filesystems
-- and in this case, a secondary cache just for MR framework -- without changing the public
api of {{FileSystem}}.  Is this implementation unacceptable?  If so, are there simple alternatives
other than ref counts?
                
> DistributedFileSystem close has severe consequences
> ---------------------------------------------------
>
>                 Key: HADOOP-7973
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7973
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 1.0.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>            Priority: Blocker
>         Attachments: HADOOP-7973-2.patch, HADOOP-7973-3.patch, HADOOP-7973-4.patch, HADOOP-7973.patch
>
>
> The way {{FileSystem#close}} works is very problematic.  Since the {{FileSystems}} are
cached, any {{close}} by any caller will cause problems for every other reference to it. 
Will add more detail in the comments.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message