[
https://issues.apache.org/jira/browse/HADOOP-3369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Shvachko updated HADOOP-3369:
----------------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
I just committed this.
> Fast block processing during name-node startup.
> -----------------------------------------------
>
> Key: HADOOP-3369
> URL: https://issues.apache.org/jira/browse/HADOOP-3369
> Project: Hadoop Core
> Issue Type: Improvement
> Components: dfs
> Affects Versions: 0.17.0
> Reporter: Konstantin Shvachko
> Assignee: Konstantin Shvachko
> Fix For: 0.18.0
>
> Attachments: fastBlockReports.patch, fastBlockReports.patch
>
>
> The block report processing during the startup period should be optimized.
> As noted in HADOOP-3022 during cluster startup all blocks are
> under-replicated
> because they have not been reported by name-nodes yet.
> Currently, we routinely move blocks to the neededReplications queue when they
> are first reported and then remove them from the list when other nodes report
> it.
> In ideal situation we end up adding all blocks into neededReplications queue
> first
> only in order to remove all of them in the end.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
