You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Siddhant Sangwan (Jira)" <ji...@apache.org> on 2025/10/09 10:12:00 UTC
[jira] [Assigned] (HDDS-13762) Mis replication bug when there is a dead maintenance node
[ https://issues.apache.org/jira/browse/HDDS-13762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Siddhant Sangwan reassigned HDDS-13762:
---------------------------------------
Assignee: Siddhant Sangwan
> Mis replication bug when there is a dead maintenance node
> ---------------------------------------------------------
>
> Key: HDDS-13762
> URL: https://issues.apache.org/jira/browse/HDDS-13762
> Project: Apache Ozone
> Issue Type: Bug
> Components: SCM
> Reporter: Siddhant Sangwan
> Assignee: Siddhant Sangwan
> Priority: Major
>
> Please read [https://github.com/apache/ozone/pull/8934#issue-3312911733] for context.
> This jira specifically fixes the following part of the problem:
> Since the dead maintenance node is removed from topology, checking its containers for mis replication will fail, again because the node is removed from topology. I haven't reprod this, I just got this from reading the logic in validateContainerPlacement. HDFS gets around this by using node's network location that is held in memory in the node's object instead of using the network topology. I think we could do something similar in ozone.
> Also consider the suggestion given here as a fix (second point): [https://github.com/apache/ozone/pull/8934#issuecomment-3189172581]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org