-
Notifications
You must be signed in to change notification settings - Fork 80
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
1.0.4: Support handling of TailThread cursor/connection failures #174
Merged
timvaillancourt
merged 33 commits into
Percona-Lab:1.0.4
from
timvaillancourt:oplog_tailer_flush
Jun 16, 2017
Merged
1.0.4: Support handling of TailThread cursor/connection failures #174
timvaillancourt
merged 33 commits into
Percona-Lab:1.0.4
from
timvaillancourt:oplog_tailer_flush
Jun 16, 2017
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
Contributor
timvaillancourt
commented
Jun 16, 2017
- Support better handling/logging of TailThread cursor/connection failures
- Fsync the tailed oplog to disk on time or doc-writes thresholds.
- Pass 'backup_stop' event to threads to signal failure to other child threads.
- Allow oplog tailing to be disabled.
- Added script to simulate failure of cursor/query.
Merged
timvaillancourt
added a commit
that referenced
this pull request
Aug 4, 2017
* Only apply quorum checking to voting members * Only apply quorum checking to electable members (not arbiter or priority=0) * 'make docker' must depend on the bin/mongodb-consistent-backup Makefile-step (#167) * Fix issue #163, move to OperationError() (#168) * Remove 'secondary_count' logic, only count electable nodes for new quorum logic (#169) * 1.0.4: Print more mongodump details (#170) * Print more details about mongodump * Version must be set first * Check if version unknown * 1.0.4: Ensure Resolver consistent timestamp is not before end of mongodump (#164) (#171) * Don't return an consistent_end_ts that is earlier than the last_ts of mongodump oplogs * Some code cleanup and fixed rounding-up logic * 1.0.4: Support handling of TailThread cursor/connection failures (#174) Support better handling/logging of TailThread cursor/connection failures Fsync the tailed oplog to disk on time or doc-writes thresholds. Pass 'backup_stop' event to threads to signal failure to other child threads. Allow oplog tailing to be disabled. Added script to simulate failure of cursor/query. * Fix disabling of oplog tailer * Fix disabling of oplog tailer (#175) * 1.0.4: Mongodump handle error (#176) * Handle mongodump's "Failed: ..." messages as a proper error * 1.0.4: Support Google Cloud Storage upload v1 (#178) * 1.1.0 VERSION (#180) * Readme gcs (#181) * Readme gcs 2 (#182) * 1.1.0 requirements.txt update (#183) * Update Fabric and boto versions * 1.1.0 repllag default 10s (#184) * Raise default repl lag max to 10s, 5s has shown to be too low on many hosts. 3.4 adds a no-op oplog update every 10s so this seems to align nicely with it * 1.1.0 gcs upload threading (#185)
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.