-
Notifications
You must be signed in to change notification settings - Fork 138
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
Rev pruning algorithm deletes entire revtree if only branch is a tombstoned branch #2695
Comments
Note: cannot repro with higher revs_limit, seems related to rev pruning |
Reverting commit the rev pruning change (commit 4d4e4f2), the test passes. So it's confirmed to be caused by that commit. |
Debugging into this sync gateway error message:
The doc.History is completely empty, which is why it can't find the revision. In the log line directly above that error, I'm seeing:
and digging into that I can see that the entire revtree is getting pruned away when it consists of only a single tombstoned/deleted branch: Before revtree pruningAfter revtree pruningAfter pruning there is no rev history whatsoever. I would expect it to keep 60 revisions after the rev tree pruning, since |
I just pushed the following changes up to the feature/issue_2695_sg_returns_500_err_delete branch:
Going to clean up the changes and push up a PR. |
Spun out of #2687, regression caused by #2669
Steps to repro:
1.Run test_sg_sdk_interop_shared_docs[sync_gateway_default_functional_tests-1-1000] against commit 85f79d0:
Pause python interpreter after updates, before deletes.
Using curl, try to delete latest rev:
Get error:
The text was updated successfully, but these errors were encountered: