chunshao.rcs

Results 32 issues of chunshao.rcs

## Rationale ## Detailed Changes ## Test Plan

**Description** Merge the implementation of the procedure storage with the storage storage implementation to prevent cases where the etcd key is not prefixed with the root path. **Proposal** Support persisting...

enhancement

**Description** After #273 , EnableSchedule is not persisted in cluster options in meta storage(currently implementation is etcd). After the `ceresmeta-server` restarts, the `EnableSchedule` will not take effect. **Proposal** Persist `EnableSchedule`...

enhancement

**Describe this problem** Commit id: f561cd63b197e4153ce9771c6628294d11851448 Encounter the following error ``` 2023-11-10T10:55:45.699+0800 error transferleader/transfer_leader.go:146 shard leader node not match {"requestOldLeaderNodeName": "xx.160:8831", "actualOldLeaderNodeName": "xx.198:8831"} github.com/[Cere](https://github.com/CeresDB/ceresmeta/issues/new?assignees=&labels=bug&projects=&template=bug_report.md#)[sDB](https://github.com/CeresDB/ceresmeta/issues/new?assignees=&labels=bug&projects=&template=bug_report.md#)/ceresmeta/server/coordinator/procedure/operation/transferleader.validateClusterTopology /ceresmeta/server/coordinator/procedure/operation/transferleader/transfer_leader.go:146 github.com/CeresDB/ceresmeta/server/coordinator/procedure/operation/transferleader.NewProcedure /ceresmeta/server/coordinator/procedure/operation/transferleader/transfer_leader.go:89 github.com/CeresDB/ceresmeta/server/coordinator.(*Factory).CreateTransferLeaderProcedure /ceresmeta/server/coordinator/factory.go:233 github.com/CeresDB/ceresmeta/server/coordinator/scheduler/rebalanced.(*schedulerImpl).Schedule...

bug

**Description** During dynamic scheduling, querying table routing will return empty routing information, which is easy to cause confusion. **Proposal** During dynamic scheduling, return error? **Additional context**

enhancement

**Description** Do not return an error when dropping a table that exists in ceresmeta but does not exist in ceresdb. **Proposal** * `handle_drop_table_on_shard` in meta_event service support `if exists`. **Additional...

enhancement

**Describe this problem** Occurs data race in CI ``` ================== WARNING: DATA RACE Write at 0x00c00033f4d0 by goroutine 115: github.com/CeresDB/ceresmeta/server/member.TestWatchLeaderSingle() /home/runner/work/ceresmeta/ceresmeta/server/member/watch_leader_test.go:56 +0x572 testing.tRunner() /opt/hostedtoolcache/go/1.19.3/x64/src/testing/testing.go:1446 +0x216 testing.(*T).Run.func1() /opt/hostedtoolcache/go/1.19.3/x64/src/testing/testing.go:1493 +0x47 Previous read...

bug

**Description** With the addition of the cluster scheduling module, the current cluster metadata management is somewhat confusing. **Proposal** - [x] Define the memory data structure corresponding to pb. - [x]...

enhancement

**Description** Start and stop the cluster manager when the leader changes. **Proposal** - [x] When the leader changes, the cluster manage is needed to be started or stopped. - [...

enhancement

**Describe this problem** `Create table` and `Drop table` need to use routing. But the current logic is using the management addr to create table. **Steps to reproduce** **Expected behavior** **Additional...

bug