[
https://issues.apache.org/jira/browse/HDFS-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280418#comment-13280418
]
Konstantin Shvachko commented on HDFS-3368:
-------------------------------------------
I incorporated Nicholas's comments.
Double checking on the configuration parameter before changing it.
Aaron, sounds like you would generally prefer configuration parameters to
constants. But this is not always a good approach. There were many discussions
in the past about it. People are getting confused if you give them too many
parameters that they have to understand in order to change. This one is hardly
to be ever changed by anybody.
So I am asking whether you feel strong about making it an undocumented config
parameter.
> Missing blocks due to bad DataNodes comming up and down.
> --------------------------------------------------------
>
> Key: HDFS-3368
> URL: https://issues.apache.org/jira/browse/HDFS-3368
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.22.0, 1.0.0, 2.0.0, 3.0.0
> Reporter: Konstantin Shvachko
> Assignee: Konstantin Shvachko
> Attachments: blockDeletePolicy-0.22.patch,
> blockDeletePolicy-trunk.patch, blockDeletePolicy.patch
>
>
> All replicas of a block can be removed if bad DataNodes come up and down
> during cluster restart resulting in data loss.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
