-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
feat(restore): introduce incremental restore (#7942) #8624
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mangalaman93
requested review from
akon-dey,
MichelDiz,
matthewmcneely,
skrdgraph,
darkn3rd,
meghalims and
billprovince
as code owners
January 20, 2023 21:38
mangalaman93
added
the
slash-to-main
PRs which bring slash branch on par with main.
label
Jan 20, 2023
More tests to add:
|
mangalaman93
force-pushed
the
aman/lock
branch
2 times, most recently
from
February 2, 2023 05:17
f0b4621
to
2163656
Compare
mangalaman93
force-pushed
the
aman/incr
branch
from
February 2, 2023 14:12
40bc31b
to
7e4c9d3
Compare
mangalaman93
force-pushed
the
aman/incr
branch
from
February 14, 2023 20:25
7e4c9d3
to
a76d18f
Compare
mangalaman93
force-pushed
the
aman/incr
branch
3 times, most recently
from
February 24, 2023 13:08
c7f6c5a
to
870b8ab
Compare
mangalaman93
force-pushed
the
aman/incr
branch
3 times, most recently
from
March 6, 2023 20:27
3e485b5
to
825dc2d
Compare
joshua-goldstein
previously approved these changes
Mar 7, 2023
mangalaman93
force-pushed
the
aman/incr
branch
3 times, most recently
from
March 7, 2023 19:56
ac1a070
to
ec61a62
Compare
This commit introduces incremental restore. It allows incremental backups to be restored on top of a set of already restored backups. In between two incremental restores, the cluster is in draining mode.
all-seeing-code
approved these changes
Mar 15, 2023
joshua-goldstein
approved these changes
Mar 15, 2023
skrdgraph
added a commit
that referenced
this pull request
Mar 17, 2023
Similar to #8743 but two changes. - github.com/dgraph-io/graphql-transport-ws did not have any CVE's, see #8624: - Bumping google.golang.org/[email protected] to v1.52.0 caused issues, but this was not a CVE fix. See #8655 We now have parity with main branch (i.e. equal number and same CVE's on main and slash). --------- Co-authored-by: skrdgraph <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
dgraph
Issue or PR created by an internal Dgraph contributor.
slash-to-main
PRs which bring slash branch on par with main.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit introduces incremental restore. It allows incremental backups to be restored on top of a set of already restored backups. In between two incremental restores, the cluster is in draining mode.
fixes #8533