[HDFS-5478] File size reports as zero after writing and calling FSDataOutputStream#hsync()

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.0.0-alpha

Environment

RHEL/OEL 6u3

• Assignee: Unassigned
• Reporter: Brett Randall
• Created: 08/Nov/13 05:17
• Updated: 11/Nov/13 02:29
• Resolved: 11/Nov/13 02:29

Description

Using a Java client to write to a FSDataOutputStream. After some data is written and hsync() is called, hdfs dfs -get /path/to/file gets a file containing the data written so-far, all good.

hdfs dfs -ls /path/to/file however reports a zero-byte file, presumably until the stream is closed (it then shows the correct size). Hue File Browser (running CDH4) also shows zero bytes until the stream is closed.

See also http://grokbase.com/t/hadoop/hdfs-user/113j63nrce/zero-file-size-after-hsync which discusses the same problem.

After the buffer is flushed it would be good if the reported file size was updated.

Issue Links

• duplicates: HDFS-4213 When the client calls hsync, allows the client to update the file length in the NameNode
• relates to: HDFS-4213 When the client calls hsync, allows the client to update the file length in the NameNode