-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Crash when loading data from badger in initStorage . #5573
Comments
@JimWen Does the same data directory work with v20.03.1 after a restart? Badger levels are supposed to be sorted. The crash indicates that your data is not sorted. @balajijinnah I suspect this is the result of the index caching that we added to badger recently. We're comparing only the smallest and the biggest keys for the tables https://github.com/dgraph-io/badger/blob/056d859606380082d8694d2ad3b3ebf4b10318d7/util.go#L54 and the biggest might be fetched from the cache. |
v20.03.1 is fine |
@JimWen This is definitely a bug in Badger. Your keys are not sorted which shouldn't happen. I'll run some experiments and circle back. |
OK, thank you |
@jarifibrahim when i bulkload, something is wrong at reduce phase and crash, and i think may be this is the same problem, stack is as followings
|
@JimWen How much data were you trying to insert? I think this shows up only when you have sufficiently large dataset. |
Yes, about 5 billion N-Quads |
This has been fixed in badger via dgraph-io/badger#1380 . I'll close this issue once badger is updated in master. |
What version of Dgraph are you using?
Dgraph version : v20.03.3
Dgraph SHA-256 : 08424035910be6b6720570427948bab8352a0b5a6d59a0d20c3ec5ed29533121
Commit SHA-1 : fa3c191
Commit timestamp : 2020-06-02 16:47:25 -0700
Branch : HEAD
Go version : go1.14.1
Have you tried reproducing the issue with the latest release?
yes
What is the hardware spec (RAM, OS)?
128G mem & 1.8T SSD
Linux version 3.10.0-1062.9.1.el7.x86_64 (mockbuild@kbuilder.bsys.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-39) (GCC) ) #1 SMP Fri Dec 6 15:49:49 UTC 2019
Steps to reproduce the issue (command/config used to run Dgraph).
Import large dataset with liveload and then restart.
Expected behaviour and actual result.
Log is as followings:
The text was updated successfully, but these errors were encountered: