[ https://issues.apache.org/jira/browse/HDFS-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096247#comment-13096247 ]
Suresh Srinivas commented on HDFS-200: -------------------------------------- +1 for the patch. > In HDFS, sync() not yet guarantees data available to the new readers > -------------------------------------------------------------------- > > Key: HDFS-200 > URL: https://issues.apache.org/jira/browse/HDFS-200 > Project: Hadoop HDFS > Issue Type: New Feature > Affects Versions: 0.20-append > Reporter: Tsz Wo (Nicholas), SZE > Assignee: dhruba borthakur > Priority: Blocker > Fix For: 0.20-append > > Attachments: 4379_20081010TC3.java, HDFS-200.20-security.1.patch, > Reader.java, Reader.java, ReopenProblem.java, Writer.java, Writer.java, > checkLeases-fix-1.txt, checkLeases-fix-unit-test-1.txt, > fsyncConcurrentReaders.txt, fsyncConcurrentReaders11_20.txt, > fsyncConcurrentReaders12_20.txt, fsyncConcurrentReaders13_20.txt, > fsyncConcurrentReaders14_20.txt, fsyncConcurrentReaders15_20.txt, > fsyncConcurrentReaders16_20.txt, fsyncConcurrentReaders3.patch, > fsyncConcurrentReaders4.patch, fsyncConcurrentReaders5.txt, > fsyncConcurrentReaders6.patch, fsyncConcurrentReaders9.patch, > hadoop-stack-namenode-aa0-000-12.u.powerset.com.log.gz, > hdfs-200-ryan-existing-file-fail.txt, hypertable-namenode.log.gz, > namenode.log, namenode.log, reopen_test.sh > > > 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. For more information on JIRA, see: http://www.atlassian.com/software/jira