Skip to content
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

Development Tasks for Log-based Increment Backup, directly on TiKV #29501

Closed
32 of 41 tasks
3pointer opened this issue Nov 5, 2021 · 0 comments · Fixed by #36031, #36197 or #37546
Closed
32 of 41 tasks

Development Tasks for Log-based Increment Backup, directly on TiKV #29501

3pointer opened this issue Nov 5, 2021 · 0 comments · Fixed by #36031, #36197 or #37546
Labels
component/br This issue is related to BR of TiDB. type/feature-request This is a feature requests on the product

Comments

@3pointer
Copy link
Contributor

3pointer commented Nov 5, 2021

Description

We want to have a log-based streaming backup system which

  • can scale up with the cluster
  • native, does not require an external processor, to reduce the number of “moving parts”
  • light-weight, continuous backup in should not affect latency
  • low-level, keeping the details of the original cluster as much as possible, reducing backup and restore complexity
  • support point-in-time recovery

This issue tracks our progress.

Milestone

  • Backup the DML data only to s3 with 10G data size and scheduler paused. due date 12/16/21
  • Restore above DML data from s3.
  • Implement local(nfs) storage. due date 12/16/21
  • Support backup & restore DDL. #34621
  • Support backup only DML data with random scheduler enabled.
  • Support TB level workload (TBD: determine incremental flow in workload).
  • Support 10k tables workload (TBD: determine incremental flow in workload).
  • Support TB level workload with random TiKV crash.
  • Support 10k tables workload with random TiKV crash.

Sub Tasks

Log File Structure

Support Log-based Backup

Support Log-based Restore

Support Checksum

  • Support generate checksum data during Backup.
  • Support valid checksum data during Restore.

Trivia

@3pointer 3pointer added the type/feature-request This is a feature requests on the product label Nov 5, 2021
@kennytm kennytm added the component/br This issue is related to BR of TiDB. label Nov 5, 2021
@3pointer 3pointer changed the title [Draft] Development Task for Log-based Increment Backup, directly on TiKV [Draft] Development Tasks for Log-based Increment Backup, directly on TiKV Nov 5, 2021
@3pointer 3pointer changed the title [Draft] Development Tasks for Log-based Increment Backup, directly on TiKV Development Tasks for Log-based Increment Backup, directly on TiKV Nov 22, 2021
@joccau joccau mentioned this issue May 6, 2022
12 tasks
ti-chi-bot added a commit to tikv/tikv that referenced this issue May 7, 2022
…ter (#12430)

close #12429, ref pingcap/tidb#29501

Added a new component `backup-stream` for TiKV, which allows TiKV listen the change from raftstore and collect them to external storage.

Signed-off-by: Yu Juncen <yujuncen@pingcap.com>

Co-authored-by: 3pointer <luancheng@pingcap.com>
Co-authored-by: Ti Chi Robot <ti-community-prow-bot@tidb.io>
ti-chi-bot pushed a commit that referenced this issue May 12, 2022
ti-chi-bot pushed a commit that referenced this issue Jul 13, 2022
ti-chi-bot pushed a commit that referenced this issue Jul 29, 2022
joccau added a commit to ti-srebot/tidb that referenced this issue Jul 29, 2022
@3pointer 3pointer reopened this Jul 29, 2022
ti-chi-bot pushed a commit that referenced this issue Sep 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment