Tracking issue: metasrv maintenance

[drmingdrmer]

Backward compatible upgrade:

• feature: metasrv has to be compatible with 20220413-34e89c99e4e35632718e9227f6549b3090eb0fb9 #4901
• Transaction API. High prio #4918
• Compatibility test: download an old binary, run a sample workload, check state. #4949
• API: Add version number field to metasrv API. Client provides its version and the server provides its compatbile version. #4948
• databend-meta --join <addr> should ignore the address of itself when joining a cluster #7189
• Add version to the store on local disk. #4950
• Offline upgrade: when startup with a new version binary, convert old data in the store to the latest format. #4952

Maintenance

There are already APIs providing cluster config info such as leader and member.
Needs more load metrics

• metrics API providing requests/sec, active watchers, outstanding(uncommitted) raft logs, number of raft logs, state machine size etc. #4938
• Use metactl to remove a node from a cluster. #4988

Doc:

• Document for databend-metasrv #4920

[drmingdrmer]

@lichuang @ariesdevil any suggetions? 🤔

[ariesdevil]

Logical backup that @BohuTANG mentioned

[lichuang]

add Compatibility data unit test into daily CI, every time upgrade the format, MUST add corresponding unit test.

[drmingdrmer]

Logical backup that @BohuTANG mentioned

Backup has been implemented with metactl. Did you mean something else?