[HADOOP-1838] Files created with an pre-0.15 gets blocksize as zero, causing performance degradation

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 0.15.0
• Fix Version/s: 0.15.0
• Assignee: Dhruba Borthakur
• Reporter: Dhruba Borthakur
• Created: 05/Sep/07 06:45
• Updated: 08/Jul/09 16:42
• Resolved: 07/Sep/07 00:05

Description

HADOOP-1656 introduced the support for storing block size persistently as inode metadata. Previously, if the file has only one block then it was not possible to accurately determine the blocksize that the application has requested at file-creation time.

The upgrade of an older layout to the new layout kept the blocksize as zero for single-block files that were upgraded to the new layout. This was done to indicate the DFS really does not know the "true" blocksize of this file. This caused map-reduce to determine that a split is 1 byte in length!

Issue Links

• is related to: HADOOP-1656 HDFS does not record the blocksize for a file