[BUG]: Concurrent manifest corruption bugfix not pulled into latest build #1819
Assignees
Labels
kind/bug
Something is broken.
Comments
|
Thanks, @joshua-goldstein! I really appreciate the fast response. |
skrdgraph
pushed a commit
that referenced
this issue
Nov 3, 2022
…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 <kesken88@gmail.com>
|
@dangermike Thanks again for bringing this to our attention, issue is patched in Badger v3.2103.4. |
mangalaman93
pushed a commit
that referenced
this issue
Feb 14, 2023
…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 <kesken88@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version of Badger are you using?
v3.2103.3
What version of Go are you using?
Go 1.19 (not that it matters)
Have you tried reproducing the issue with the latest release?
Yes
What is the hardware spec (RAM, CPU, OS)?
Doesn't matter
What steps will reproduce the bug?
Look at #1756, see it in the
masterbranch, but not on thev3.2103.3branchExpected behavior and actual result.
Expected merged bugfix to be in the latest release. Actually not.
Additional information
I think this was just missed when the tag was created. It's a big deal for those affected by it.
The text was updated successfully, but these errors were encountered: