Known issue with Badger? sync.runtime_Semacquire panic

I’m running a sustained load test using badger (no dgraph just yet) to test the underlying scalability. I’m writing ~50KEPS on an i3.4XL in AWS and after around 24 hours with a 12 hour TTL the program panic’d with the below paste. Just seeing if this is a known issue before making a more targeting test case to post.

opts := badger.DefaultOptions
opts.Dir = config.DBDirectory
opts.ValueDir = config.DBDirectory
opts.TableLoadingMode = options.MemoryMap
opts.MaxTableSize = 2 * (1024 * 1024 * 1024) // 2GB

And a go routine running every 30 mins on a ticker that calls: (err handling removed for clarity)

goroutine 2787863423 [semacquire]:
        /usr/local/go/src/runtime/sema.go:56 +0x39
        /usr/local/go/src/sync/waitgroup.go:129 +0x72*request).Wait(0xc7bfdec230, 0x460261, 0xc4205ae1e0)
        /mnt/mrnull/golang/src/ +0x35*DB).batchSetAsync.func1(0xc7bfdec230, 0xc9205b39a0)
        /mnt/mrnull/golang/src/ +0x2b
created by*DB).batchSetAsync
        /mnt/mrnull/golang/src/ +0x9c

goroutine 2787884118 [running]:
        goroutine running on other thread; stack unavailable

No, this isn’t a known issue. It would be helpful if you can share the entire stack trace and a program which reproduces this.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.