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

CLIENT_FILTER performance: No recovery/restart record is written in the repository database unless at least one document was stored in the target database #9

Open
ptitzler opened this issue Sep 7, 2016 · 0 comments

Comments

@ptitzler
Copy link
Contributor

ptitzler commented Sep 7, 2016

Recovery/restart records keep track of the last sequence number that was saved in the target database. Assume the source is a huge database and an aggressive filter is defined that eliminates most documents (lets say the first million) from the source. If the service encounters a fatal error before the first recovery record is written, the service restarts processing with sequence number 0 instead of resuming with the last sequence number that didn't pass the filter.

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

No branches or pull requests

1 participant