You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 6, 2024. It is now read-only.
Describe this problem
After the cluster runs for a long time, the ShardVersion of some CeresDB nodes is inconsistent with the ShardVersion of CeresMeta.
Steps to reproduce
The cluster runs for a long time, and it is not clear how to reproduce it.
Expected behavior
The Shard version of CeresDB and CeresMeta are consistent.
This problem results from that shard version is determined by ceresmeta, but it should be decided by ceresdb. And my proposal is to upgrade the protocol of meta_event_service to support ceresdb to decide the shard version.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe this problem
After the cluster runs for a long time, the ShardVersion of some CeresDB nodes is inconsistent with the ShardVersion of CeresMeta.
Steps to reproduce
The cluster runs for a long time, and it is not clear how to reproduce it.
Expected behavior
The Shard version of CeresDB and CeresMeta are consistent.
Additional Information
The text was updated successfully, but these errors were encountered: