Details
-
Bug
-
Resolution: Fixed
-
Critical
-
5.5.0
-
Untriaged
-
Unknown
Description
In one of the system test logs in bug MB-30009, a panic was observed in DequeueUptoSeqno call of mutation queue. Stack -
panic: runtime error: invalid memory address or nil pointer dereference
|
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x569ff3]
|
goroutine 811505861 [running]:
|
panic(0xe39d40, 0xc420016080)
|
/home/couchbase/.cbdepscache/exploded/x86_64/go-1.7.6/go/src/runtime/panic.go:500 +0x1a1 fp=0xc65663bdc8 sp=0xc65663bd38
|
runtime.panicmem()
|
/home/couchbase/.cbdepscache/exploded/x86_64/go-1.7.6/go/src/runtime/panic.go:62 +0x6d fp=0xc65663bdf8 sp=0xc65663bdc8
|
runtime.sigpanic()
|
/home/couchbase/.cbdepscache/exploded/x86_64/go-1.7.6/go/src/runtime/sigpanic_unix.go:24 +0x214 fp=0xc65663be50 sp=0xc65663bdf8
|
github.com/couchbase/indexing/secondary/indexer.(*atomicMutationQueue).dequeueUptoSeqno(0xc44edfefc0, 0xef, 0xa9bc4, 0xc5dd1c5ce0, 0xc5dd1c5d40)
|
goproj/src/github.com/couchbase/indexing/secondary/indexer/mutation_queue_atomic.go:207 +0x163 fp=0xc65663bf88 sp=0xc65663be50
|
runtime.goexit()
|
/home/couchbase/.cbdepscache/exploded/x86_64/go-1.7.6/go/src/runtime/asm_amd64.s:2086 +0x1 fp=0xc65663bf90 sp=0xc65663bf88
|
created by github.com/couchbase/indexing/secondary/indexer.(*atomicMutationQueue).DequeueUptoSeqno
|
goproj/src/github.com/couchbase/indexing/secondary/indexer/mutation_queue_atomic.go:180 +0xaf
|
From code, it looks like head.next.mutation pointer could be nil or its meta could be nil.
Node: 172.23.96.153
Logs: https://s3.amazonaws.com/bugdb/jira/MB-30009-01/collectinfo-2018-06-07T095758-ns_1%40172.23.96.153.zip
Full set of cluster logs can be found in "logs" section of bug MB-30009
Attachments
Issue Links
- relates to
-
MB-30077 SystemTest: panic observed in MutationQueue.DequeueUptoSeqno
- Closed