[
https://issues.apache.org/jira/browse/HDDS-5015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-5015:
----------------------------
Description:
We set up the three SCM cluster to test HA.
>From ozone dbug ldb tool, we found that the sequenceIDs are not same between
>three SCM. The reason is due to localID, which is initialized based on 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
was:
We set up the three SCM cluster to test HA.
>From ozone dbug ldb tool, we found that the sequenceIDs are not same between
>three SCM. The reason is due to localID, which is initialized based on own
>timestamp.
## END is delimiter i added to divide the records
1.
17000 END
8000 END
105898712280731336 END
2.
17000 END
8000 END
105898723592162080 END
3.
17000 END
8000 END
105898724336720504 END
> SequenceID is not consistent 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
>
> We set up the three SCM cluster to test HA.
> From ozone dbug ldb tool, we found that the sequenceIDs are not same between
> three SCM. The reason is due to localID, which is initialized based on 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: [email protected]
For additional commands, e-mail: [email protected]
