You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Glen Geng (Jira)" <ji...@apache.org> on 2021/03/24 04:28:00 UTC
[jira] [Resolved] (HDDS-5015) localId is not consistent across SCMs
when setup a multi node SCM HA cluster.
[ https://issues.apache.org/jira/browse/HDDS-5015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Glen Geng resolved HDDS-5015.
-----------------------------
Resolution: Fixed
> localId is not consistent across SCMs when setup a multi node SCM HA cluster.
> -----------------------------------------------------------------------------
>
> Key: HDDS-5015
> URL: https://issues.apache.org/jira/browse/HDDS-5015
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: SCM HA
> Reporter: Xu Shao Hong
> Assignee: Glen Geng
> Priority: Major
> Labels: pull-request-available
>
> We set up the three node SCM HA cluster for test purpose.
> From ozone dbug ldb tool, we found that the localIDs are not same between the three SCM. The reason is due to localID, which is initialized based on each machines own timestamp.
> The ldb result fetch from scm.db on 3 SCMs.
> *scm1*
> 17000 END
> 8000 END
> 105898712280731336 END
> *scm2*
> 17000 END
> 8000 END
> 105898723592162080 END
> *scm3*
> 17000 END
> 8000 END
> 105898724336720504 END
--
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