v1.2.0

Upgrade Guide

NOTE: this guide is only used for upgrading CeresMeta v1.1.0 to CeresMeta v1.2.0, and ignore it if you want to deploy a brand new CeresMeta cluster with v1.2.0.

1. We have modified the default data root directory of ETCD, so if you want to be compatible with the previous data, you need to manually specify the path of the ETCD root directory, which is consistent with the previous version. Specifically:

• Add the config section to your config file

  storage-root-path = "/rootPath"
  

Major Features

• Support the new mechanism of failover and load balancing.
  • #706 #853 implements the distributed locks for shard based on ETCD, and opening and closing of shards is only allowed with the shard lock held, and after that, data corruption caused by multiple shard leaders will be avoided completely;
  • Support automatic failover of CeresDB nodes, that is to say, the service recovery can be handled automatically without any manual intervention;
  • Support automatic load balance based on consistent hashing, which can ensure that shards are evenly distributed on each node of the cluster when the number of the cluster nodes increases or decreases;

What's Changed

• refactor: refactor cluster by @ZuLiangWang in #157
• refactor: refactor shard version check by @ZuLiangWang in #158
• feat: add health check api by @mrrtree in #159
• fix: fix update cluster view when shardinfos is empty by @ZuLiangWang in #160
• feat: add rebalanced shard scheduler by @ZuLiangWang in #162
• feat: add deploy mode by @ZuLiangWang in #163
• fix: fix get table of shards. by @ZuLiangWang in #164
• refactor: avoid frequent update of clusterVersion by @ZuLiangWang in #166
• fix: fix drop partition table by @ZuLiangWang in #167
• refactor: add schedule type by @ZuLiangWang in #168
• fix: fix compare result by @ZuLiangWang in #169
• fix: fix register node by @ZuLiangWang in #170

New Contributors

• @mrrtree made their first contribution in #159

Full Changelog: v1.1.0...v1.2.0