-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Provide log version information to fdbdr status #4274
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
Closed
Closed
Conversation
This file contains hidden or 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
Merge 6.2 to 6.3
Adding LZ4 to Centos 7 Docker Image: #4147
That's the only place they're needed. This fixes at least the USE_TSAN build and possibly other sanitizer builds
Set special sanitizer annotations in stacktrace.amalgamation.cpp
Stable interfaces
…many queue entries are processed without waiting on IO.
Fixed error with Windows CMake Compilation Error
…r-management-commands
Remove "a/" from tracing keys in special-key-space
…flow Fix stack overflow in Redwood
Whem the database is not fully replicated to remote, fault tolerance can be calculated by couting total number of tLogs replicas in primary and satellite - 1, as we can lose all but one of those, but we were subtracting 2 instead of 1.
Add c function fdb_database_force_recovery_with_data_loss
…ride Apply modernize-use-override to several files
Add CLI argument to print build information
Fix missing override in fdbrpc/FlowTests.actor.cpp
Simplified global knobs
Merge 6.3 to master 1 26 21
Support Testing S3BlobStore backup in simulation
Add network option to set tracer in fdbclient
Fix Windows build
…lconnection-read Improve SimExternalConnection::read performance
Collaborator
|
This PR looks good, you are free to rebase it against 6.2 |
Collaborator
Author
|
Automatic rebase master->6.2 was not successful. So I will close this PR and I will create a new one for 6.2 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem statement
I can make a fast consistent copy of a fdb cluster by stopping a DR site and copy all the files from all DR nodes to a new cluster nodes and detach this copy from the primary site.
I can perform a point-in-time recovery from this copy with
fdbrestore start --incremental --begin_version XXXXXXX.But there is no easy way to get a source db version for using with
--begin_versionoption.Findings
When dr agent runs it executes
dr_copy_diff_logstasks for copying version intervals of the mutation log to the DR database, When the task is executing, it hasbeginVersion: the version all changes before have been copied.Proposal
dr_copy_diff_logsexecutesfdbdr statusThis pull request implements this proposal.
P.S. I'd like to merge it to fdb 6.2. Is it possible?