You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Jitendra Nath Pandey (Jira)" <ji...@apache.org> on 2020/06/03 07:19:00 UTC
[jira] [Resolved] (HDDS-3081) Replication manager should detect and
correct containers which don't meet the replication policy
[ https://issues.apache.org/jira/browse/HDDS-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jitendra Nath Pandey resolved HDDS-3081.
----------------------------------------
Resolution: Fixed
The pull request is merged, this can be resolved.
> Replication manager should detect and correct containers which don't meet the replication policy
> ------------------------------------------------------------------------------------------------
>
> Key: HDDS-3081
> URL: https://issues.apache.org/jira/browse/HDDS-3081
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Components: SCM
> Affects Versions: 0.6.0
> Reporter: Stephen O'Donnell
> Assignee: Stephen O'Donnell
> Priority: Major
> Labels: pull-request-available
>
> In the current implementation, replication manager does not consider the container placement when checking if a container is healthy. Only the number of replicas are checked.
> Now we have network topology available, we should consider whether replication manager should detect and correct mis-replicated containers.
> In HDFS, the namenode will not automatically correct mis-replicated containers automatically, except at startup when all blocks are checked.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org