Fix shard version inconsistent verification
ZuLiangWang opened this issue · comments
Describe this problem
In the current implementation of CeresMeta, the scheduler's verification of shard version inconsistency will result in the shard being closed. However, due to the backward heartbeat information during the table creation process, there is a probability of version inconsistency, which will lead to the shard being unavailable during the table creation process.
Steps to reproduce
Create table multiple times.
Expected behavior
All tables are created normally.
Additional Information
Because the current design cannot solve this problem, we plan to close the verification of version inconsistency first, and solve it after reconstructing the distributed model of CeresMeta.