You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Raghu Angadi (JIRA)" <ji...@apache.org> on 2007/09/13 03:19:32 UTC

[jira] Commented: (HADOOP-1708) make files visible in the namespace as soon as they are created

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

Raghu Angadi commented on HADOOP-1708:
--------------------------------------

There is another more immediate issue with the patch. If a file is started but is not closed, when NameNode is restarted, it appears as a directory while loading the fsimage. Currently if number of blocks is zero, then it is treated as a directory in while loading fsimage.  Should we file another jira for it?

I was working with patch for HADOOP-1298 which has directory specific fields, I saw for the first time an EOF error while loading the fsimage.


> make files visible in the namespace as soon as they are created
> ---------------------------------------------------------------
>
>                 Key: HADOOP-1708
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1708
>             Project: Hadoop
>          Issue Type: Bug
>          Components: dfs
>            Reporter: dhruba borthakur
>            Assignee: dhruba borthakur
>             Fix For: 0.15.0
>
>         Attachments: 1708-20070820a.patch, atomicCreation2.patch
>
>
> In the current DFS implementation, a file appears in the namespace only when the creator closes the file. Also, if the namenode or the client dies before closing the file, the file never appears in the namespace.
> This issue will make files appear in the namespace as soon as it is created. Also, it will continue to remain in the namespace even if the creator dies before closing the file.
> This is related to HADOOP-89. It is different from HADOOP-89 because it does not attempt to make data visible as soon as it is written. 

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