-
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
[Release Blocker] AddHelper Slice index crash #1387
Comments
The crash happens because uint32 overflow. The following code is called for every new addition Lines 223 to 226 in e013bfd
On line 241, we try to increase the size (len: 4172166119) by 50% Lines 234 to 244 in e013bfd
So
and the newly allocated slice by the The maximum size of uint32 is around 4 GB. So the question is how could there be a single table of more than 4 GB? |
…1406) This reverts commit 7f4e4b5. This revert is necessary because b.sz won't exist after builder changes are reverted and the assert is no longer valid. The commit 7f4e4b5 is being reverted because we have seen some crashes which could be caused by these changes. We haven't been able to reproduce the crashes yet. Related to #1389, #1388, #1387 Also see https://discuss.dgraph.io/t/current-state-of-badger-crashes/7602
This reverts commit 21735af. The commit is reverted because we have seen some crashes which could be caused by this change. We haven't been able to reproduce the crashes yet. Related to #1389, #1388, #1387 Also, see https://discuss.dgraph.io/t/current-state-of-badger-crashes/7602
This reverts commit aadda9a. This commit is being reverted because we have seen some crashes which could be caused by it. We haven't been able to reproduce the crashes yet. Related to #1389, #1388, #1387 Also, see https://discuss.dgraph.io/t/current-state-of-badger-crashes/7602
This reverts commit b13b927. This commit is being reverted because we have seen some crashes which could be caused by it. We haven't been able to reproduce the crashes yet. Related to #1389, #1388, #1387 Also, see https://discuss.dgraph.io/t/current-state-of-badger-crashes/7602 This commit had some conflicts. See PR description for details.
I wasn't able to reproduce this issue after multiple attempts. I'm closing this as non-reproducible. |
Github issues have been deprecated. |
…1406) This reverts commit 7f4e4b5. This revert is necessary because b.sz won't exist after builder changes are reverted and the assert is no longer valid. The commit 7f4e4b5 is being reverted because we have seen some crashes which could be caused by these changes. We haven't been able to reproduce the crashes yet. Related to #1389, #1388, #1387 Also see https://discuss.dgraph.io/t/current-state-of-badger-crashes/7602
This reverts commit 21735af. The commit is reverted because we have seen some crashes which could be caused by this change. We haven't been able to reproduce the crashes yet. Related to #1389, #1388, #1387 Also, see https://discuss.dgraph.io/t/current-state-of-badger-crashes/7602
This reverts commit aadda9a. This commit is being reverted because we have seen some crashes which could be caused by it. We haven't been able to reproduce the crashes yet. Related to #1389, #1388, #1387 Also, see https://discuss.dgraph.io/t/current-state-of-badger-crashes/7602
This reverts commit b13b927. This commit is being reverted because we have seen some crashes which could be caused by it. We haven't been able to reproduce the crashes yet. Related to #1389, #1388, #1387 Also, see https://discuss.dgraph.io/t/current-state-of-badger-crashes/7602 This commit had some conflicts. See PR description for details.
Originally seen in hypermodeinc/dgraph#5752
The crash is seen on badger commit cddf7c0.
We added support for background compression/encryption in b13b927 which could be the reason for the crash.
The issue isn't reproducible.
The text was updated successfully, but these errors were encountered: