hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-1838) Files created with an pre-0.15 gets blocksize as zero, causing performance degradation
Date Wed, 05 Sep 2007 21:07:33 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

dhruba borthakur updated HADOOP-1838:
-------------------------------------

    Attachment: blockSizeZero.patch

Use the default-block-size to be the block size for a file that has only one block.

> Files created with an pre-0.15 gets blocksize as zero, causing performance degradation
> --------------------------------------------------------------------------------------
>
>                 Key: HADOOP-1838
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1838
>             Project: Hadoop
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.15.0
>            Reporter: dhruba borthakur
>            Assignee: dhruba borthakur
>            Priority: Blocker
>             Fix For: 0.15.0
>
>         Attachments: blockSizeZero.patch
>
>
> 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!

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


Mime
View raw message