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/11/08 18:02:00 UTC
[jira] [Resolved] (HDDS-5062) Add a config to bypass clusterId
validation for bootstrapping SCM
[ https://issues.apache.org/jira/browse/HDDS-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ethan Rose resolved HDDS-5062.
------------------------------
Resolution: Fixed
PR is merged and Jira marked as fixed in 1.2.0, so I'm resolving this. Let me know if this is not correct.
> Add a config to bypass clusterId validation for bootstrapping SCM
> -----------------------------------------------------------------
>
> Key: HDDS-5062
> URL: https://issues.apache.org/jira/browse/HDDS-5062
> Project: Apache Ozone
> Issue Type: Bug
> Components: SCM HA
> Reporter: Shashikant Banerjee
> Assignee: Shashikant Banerjee
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.2.0
>
>
> IN SCM HA, the primary node starts up the ratis server while other bootstrapping nodes will get added to the ratis group. Now, if all the bootstrapping SCM's get stopped, the primary node will now step down from leadership as it will loose majority. If the bootstrapping nodes are now bootstrapped again, the bootsrapping node will try to first validate the cluster id from the leader SCM with the persisted cluster id , but as there is no leader existing, bootstrapping wil keep on failing and retrying until it shuts down.
> The issue can be very easily simulated in kubernetes deployments, where bootstrap and init cmds are run repeatedly on every restart.
> The Jira aims to bypass the cluster id validation if a bootstrapping node already has a cluster id.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org