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 mode (part 1) #53861

Merged
merged 1 commit into from
Dec 18, 2024

Conversation

xiangguangyxg
Copy link
Contributor

@xiangguangyxg xiangguangyxg commented Dec 12, 2024

Why I'm doing:

To support disaster recovery for shared-data mode.

What I'm doing:

Introduce a config file cluster_snapshot.yaml for FE.
Put the image file of a cluster snapshot in fe/meta/image of the leader FE and clear the fe/meta/bdb,
than use ./bin/start_fe.sh --cluster_snapshot --daemon to start to restore from the cluster snapshot.
Other FE nodes use ./bin/start_fe.sh --helper <leader_ip>:<leader_edit_log_port> --daemon to start.

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
7 tasks
@xiangguangyxg xiangguangyxg force-pushed the restore_snapshot_yaml branch 2 times, most recently from c7b9e88 to 7d13b75 Compare December 13, 2024 02:29
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/lake/snapshot/RestoreClusterSnapshotMgr.java 42 49 85.71% [69, 78, 79, 80, 101, 102, 104]
🔵 com/starrocks/lake/snapshot/ClusterSnapshotConfig.java 66 73 90.41% [55, 148, 167, 168, 261, 262, 263]
🔵 com/starrocks/system/SystemInfoService.java 1 1 100.00% []

Copy link

[BE Incremental Coverage Report]

pass : 0 / 0 (0%)

@xiangguangyxg xiangguangyxg changed the title [Feature] Support restoring from a cluster snapshot for shared-data (part 1) [Feature] Support restoring from a cluster snapshot for shared-data mode (part 1) Dec 16, 2024
@@ -0,0 +1,39 @@
# do not include leader fe
frontends:
Copy link
Contributor

Choose a reason for hiding this comment

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

FE configure file is xml or json,why invole a new config type ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

using yaml is designed by pm ...

FOLLOWER,
OBSERVER;

@JsonCreator
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we use json? This way, we can unify the development to GSON and reduce the types of configuration for users.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

json do not support comment and is suitable for machine parsing but not for human reading, it is not suitable for configuration file.
yaml support comment and suitable for both machine parsing and human reading, it is a better new generation configuration file.
by the way, yaml can be handled by Jackson, which is used in many places in FE.

@HangyuanLiu HangyuanLiu merged commit 969593c into StarRocks:main Dec 18, 2024
112 of 113 checks passed
@xiangguangyxg
Copy link
Contributor Author

@mergify backport branch-3.4

Copy link
Contributor

mergify bot commented Dec 19, 2024

backport branch-3.4

✅ Backports have been created

mergify bot pushed a commit that referenced this pull request Dec 19, 2024
…ode (part 1) (#53861)

Signed-off-by: xiangguangyxg <[email protected]>
(cherry picked from commit 969593c)
wanpengfei-git pushed a commit that referenced this pull request Dec 19, 2024
@xiangguangyxg xiangguangyxg deleted the restore_snapshot_yaml branch December 19, 2024 06:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

shared-data mode support backup restore though automated snapshot
4 participants