-
Notifications
You must be signed in to change notification settings - Fork 495
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EBS BR support to multiple k8s cluster TiDB #5003
Labels
Comments
/assign @WangLe1321 @BornChanger @YuJuncen @csuzhangxc |
Please don't include internal google doc link, please upload the design doc to github |
Sure. |
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Request
Is your feature request related to a problem? Please describe:
TiDB operator already supports deployment in multiple k8s clusters, but AWS EBS snapshot based Backup/Restore doesn't support the deployment yet.
Describe the feature you'd like:
AWS EBS snapshot based BR needs to support TiDB cluster deployed in multiple k8s clusters. We would like to use the kubenetes federation solution, where federation operators in control plane cooperate tidb-operators in the data plane by Kubernetes API server. See #5004 for details
Describe alternatives you've considered:
Teachability, Documentation, Adoption, Migration Strategy:
check-wal-only
strategy (#5621) #5636)operator pause-gc-and-schedulers
command tidb#43562)operator-paused-gc-and-scheduler
. tidb#43687)recover_region
while there are TiKV restarts tidb#45361)raftstore: check stale peer on leader missing (#16038) tikv/tikv#16044, raftstore: update apply state even if peer is removed (#16060) tikv/tikv#16081)
PrepareBackup
RPC for snapshot backup kvproto#1204, snapshot_backup: enhanced prepare stage tikv/tikv#15946 and backup: advacned prepare implementation tidb#48439)ebs br: new snapshot tagging tidb#50548)
The text was updated successfully, but these errors were encountered: