[
https://issues.apache.org/jira/browse/HADOOP-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667152#action_12667152
]
Jim Kellerman commented on HADOOP-4379:
---------------------------------------
@Dhruba
I tried applying fsyncConcurrentReaders3.patch to 0.19.0, 0.19 branch (latest),
0.20 branch (latest) and trunk. It did not
apply cleanly to any, but seemed to have less problems with trunk. Building it,
and running the Writer and Reader
programs I attached above, they behaved the same way, i.e., the Reader could
not see any sync'd data until the first
complete block had been written, and then it could only see the data in the
first complete block and none of the data
in the second partial block.
> In HDFS, sync() not yet guarantees data available to the new readers
> --------------------------------------------------------------------
>
> Key: HADOOP-4379
> URL: https://issues.apache.org/jira/browse/HADOOP-4379
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Reporter: Tsz Wo (Nicholas), SZE
> Assignee: dhruba borthakur
> Fix For: 0.19.1
>
> Attachments: 4379_20081010TC3.java, fsyncConcurrentReaders.txt,
> fsyncConcurrentReaders3.patch, Reader.java, Writer.java
>
>
> In the append design doc
> (https://issues.apache.org/jira/secure/attachment/12370562/Appends.doc), it
> says
> * A reader is guaranteed to be able to read data that was 'flushed' before
> the reader opened the file
> However, this feature is not yet implemented. Note that the operation
> 'flushed' is now called "sync".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
