You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Ethan Rose (Jira)" <ji...@apache.org> on 2021/03/23 20:48:00 UTC
[jira] [Updated] (HDDS-4992) SCM should not use pipelines with
HEALTHY_READONLY datanodes
[ https://issues.apache.org/jira/browse/HDDS-4992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ethan Rose updated HDDS-4992:
-----------------------------
Description: During upgrade testing for HDDS-4181, it was noticed that datanodes were incorrectly using the newest metadata layout version when pre-finalized. However, SCM still came out of safe mode counting these pipelines as healthy, even though the datanodes' MLV was ahead of SCM's. This Jira will make SCM not use pipelines involving HEATLHY_READONLY datanodes. (was: During upgrade testing for HDDS-4181, it was noticed that datanodes were incorrectly using the newest metadata layout version when pre-finalized. However, SCM still came out of safe mode counting these pipelines as healthy, even though the datanodes' MLV was ahead of SCM's. This Jira will first make SCM not use pipelines involving HEATLHY_READONLY datanodes. After this is validated using the current state of HDDS-4181, the issue with datanodes always using the newest MLV will be fixed.)
> SCM should not use pipelines with HEALTHY_READONLY datanodes
> ------------------------------------------------------------
>
> Key: HDDS-4992
> URL: https://issues.apache.org/jira/browse/HDDS-4992
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Ethan Rose
> Assignee: Ethan Rose
> Priority: Major
>
> During upgrade testing for HDDS-4181, it was noticed that datanodes were incorrectly using the newest metadata layout version when pre-finalized. However, SCM still came out of safe mode counting these pipelines as healthy, even though the datanodes' MLV was ahead of SCM's. This Jira will make SCM not use pipelines involving HEATLHY_READONLY datanodes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org