[
https://issues.apache.org/jira/browse/HDFS-10495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324923#comment-15324923
]
Rushabh S Shah edited comment on HDFS-10495 at 6/10/16 5:39 PM:
----------------------------------------------------------------
{quote}
If that is the case, both fsck and jmx metrics need to be changed. Also
depending on how you interpret it, it seems more like incompatible change than
just bug fix. That will decide if we want to fix it only in trunk.
{quote}
According to this [comment |
https://issues.apache.org/jira/browse/HDFS-8872?focusedCommentId=15317548&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15317548]
by [~mingma], it seems like an incompatible change. We may have to put it
only in trunk.
was (Author: shahrs87):
According to this [comment |
https://issues.apache.org/jira/browse/HDFS-8872?focusedCommentId=15317548&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15317548]
by [~mingma], it seems like an incompatible change. We may have to put it
only in trunk.
> Block should be marked as missing if the all the replicas are on
> Decommissioned nodes.
> --------------------------------------------------------------------------------------
>
> Key: HDFS-10495
> URL: https://issues.apache.org/jira/browse/HDFS-10495
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 2.8.0
> Reporter: Rushabh S Shah
> Assignee: Rushabh S Shah
>
> As discussed on HDFS-8872, we should mark a block as missing if all the
> replicas on decommissioned nodes since we can take the decommissioned nodes
> out of rotation anytime.
> We have seen multiple cases where all the replicas land on decommissioned
> nodes.
> After HDFS-7933, it doesn't mark as missing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
