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
The metadata that metasrv manages is vital for the whole cluster management. Like other data, we also need to add the backup and restore API for metasrv:
Add the abstraction for metadata backup and restore: Although we can backup and restore metadata for backend storage of metasrv, it's not the best operation practice. It should be better to handle in the metasrv;
For disaster recovery: If we back up the metadata period, it's easy to recover from a disaster. Actually, we always back up the etcd data scheduled;
Easy to troubleshoot: It will be easy to dump the raw metadata to debug the problem;
Hi @ozewr, thank you for your interest in this good first issue! To get started, you can take a look at this file, which provides some context on how metadata is structured in our system.
The first task involves dumping and restoring the metadata. Additionally, we aim to design a format to store the exported metadata, ensuring its compatibility and flexibility for future use.
Let us know if you have any questions or need further guidance. We're here to help!
What type of enhancement is this?
Refactor
What does the enhancement do?
Background
The metadata that metasrv manages is vital for the whole cluster management. Like other data, we also need to add the backup and restore API for metasrv:
Implementation
We can add
backup
andrestore
API in metasrv admin API.Implementation challenges
No response
The text was updated successfully, but these errors were encountered: