-
Notifications
You must be signed in to change notification settings - Fork 8
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 sure processedOffset is only updated together with processedSeq #295
Conversation
Please double and triple check this :) |
Open question: how do we handle reindexing? Do I just deploy a reindex of all leveldb indexes in Manyverse? Could we instead do that in ssb-db2 by bumping the version somehow? On the other hand, |
I think that would be the safest
I think a general level version would be good for this yes. As a separate PR for sure :) |
Benchmark results
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's gooooo
Benchmark results
|
From #291 (comment). I believe this should fix off-by-x bugs in level indexes.
From that comment:
Look at this line and imagine we have added a new plugin. In this case we will reindex, but most plugins will just skip. BUT they will update their
processedOffset
thus lovering it compared toprocessedSeq
. If you then kill the app while some of them have updated, but NOT keys or base then there will be a mismatch!