-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
fix(manifest): fix manifest corruption due to race condition in concurrent compactions (#1756) #1820
Conversation
|
@skrdgraph The CI jobs are not running because this needs to be merged into release/v3.2103 (not main)... Can we update the CI workflow to allow the jobs to run when a PR is opened against a release branch? See #1821 |
6a2b41a
to
d949429
Compare
@skrdgraph It would be good to get the CI jobs to run against branch before merging, I have another open PR here that should get the jobs to run: #1821 |
81899eb
to
dcfb65a
Compare
…rrent compactions (#1756) `manifestFile.rewrite` closes the file due to which `manifest.fp.Sync()` can fail. This leads to an updated manifest but non-updated tables set. Hence, the compaction process enters into an infinite loop failing with the `MANIFEST removes non-existing table` error. This PR fixes it. (cherry picked from commit 6ed45ae)
dcfb65a
to
29148c6
Compare
…rrent compactions (#1756) (#1820) This PR is a cherry pick of #1756. Addresses [this issue](https://discuss.dgraph.io/t/badgerdb-manifest-corruption-issue-solution/15915) on Discuss and[ this issue](#1819) on Badger. Co-authored-by: Kenan Kessler <[email protected]>
This PR is a cherry pick of #1756. Addresses this issue on Discuss and this issue on Badger.