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

[Feature] Support restoring from a cluster snapshot for shared-data (part 1) #53861

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

xiangguangyxg
Copy link
Contributor

@xiangguangyxg xiangguangyxg commented Dec 12, 2024

Why I'm doing:

To support disaster recovery for shared-data

What I'm doing:

Introduce a config file restore_snapshot.yaml for FE.
Put the image file of a snapshot in fe/meta/image and clear the fe/meta/bdb,
than use ./bin/start_fe.sh --restore_snapshot --daemon to start to restore from the snapshot.

What type of PR is this:

  • BugFix
  • Feature
  • Enhancement
  • Refactor
  • UT
  • Doc
  • Tool

Does this PR entail a change in behavior?

  • Yes, this PR will result in a change in behavior.
  • No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

  • Interface/UI changes: syntax, type conversion, expression evaluation, display information
  • Parameter changes: default values, similar parameters but with different default values
  • Policy changes: use new policy to replace old one, functionality automatically enabled
  • Feature removed
  • Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

  • I have added test cases for my bug fix or my new feature
  • This pr needs user documentation (for new or modified features or behaviors)
    • I have added documentation for my new feature or new function
  • This is a backport pr

Bugfix cherry-pick branch check:

  • I have checked the version labels which the pr will be auto-backported to the target branch
    • 3.4
    • 3.3
    • 3.2
    • 3.1
    • 3.0

@xiangguangyxg xiangguangyxg requested a review from a team as a code owner December 12, 2024 06:44
conf/restore_snapshot.yaml Outdated Show resolved Hide resolved
@xiangguangyxg xiangguangyxg force-pushed the restore_snapshot_yaml branch 2 times, most recently from cc323ba to 3573838 Compare December 12, 2024 07:12
@andyziye andyziye linked an issue Dec 12, 2024 that may be closed by this pull request
Copy link

sonarcloud bot commented Dec 13, 2024

Copy link

[BE Incremental Coverage Report]

pass : 0 / 0 (0%)

Copy link

[Java-Extensions Incremental Coverage Report]

pass : 0 / 0 (0%)

Copy link

[FE Incremental Coverage Report]

pass : 109 / 126 (86.51%)

file detail

path covered_line new_line coverage not_covered_line_detail
🔵 com/starrocks/StarRocksFE.java 0 3 00.00% [123, 187, 229]
🔵 com/starrocks/server/RestoreSnapshotMgr.java 42 49 85.71% [67, 76, 77, 78, 99, 100, 102]
🔵 com/starrocks/common/RestoreSnapshotConfig.java 66 73 90.41% [55, 148, 167, 168, 261, 262, 263]
🔵 com/starrocks/system/SystemInfoService.java 1 1 100.00% []


import java.util.List;

public class RestoreSnapshotMgr {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we use RestoreClouldNativeSnapshotMgr?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Never been named like this before, usually distinguished by namespace.
In addition, this class is common to shared data and shared nothing?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

shared data support backup restore though automated snapshot
2 participants