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

Make posting list memory rollup happen right after disk #2731

Merged
merged 2 commits into from
Nov 7, 2018

Conversation

manishrjain
Copy link
Contributor

@manishrjain manishrjain commented Nov 7, 2018

  • Do not rollup posting lists right after commits, because it causes some strange race conditions which can cause a state mismatch between memory and disk.
  • For the PLs in LRU cache, roll them up right after doing a successful roll up on disk.
  • Modify Rollup function to take a readTs, which can be set to the roll up read ts.

This change is Reviewable

…routine. This ensures that we don't see as many minTs errors. And that we don't end up in weird race conditions which might cause a txn to be lost.
@manishrjain manishrjain merged commit 0178f80 into master Nov 7, 2018
@manishrjain manishrjain deleted the mrjn/plist-rollup branch November 7, 2018 02:48
dna2github pushed a commit to dna2fork/dgraph that referenced this pull request Jul 19, 2019
- Do not rollup posting lists right after commits, because it causes some strange race conditions which can cause a state mismatch between memory and disk.
- For the PLs in LRU cache, roll them up right after doing a successful roll-up on disk.
- Modify Rollup function to take a `readTs`, which can be set to the roll-up read ts.

* Do the memory rollup right after the disk rollup in the background goroutine. This ensures that we don't see as many minTs errors. And that we don't end up in weird race conditions which might cause a txn to be lost.

* Fix up some asserts.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant