Details
-
Bug
-
Resolution: Duplicate
-
Critical
-
4.0.0
-
Security Level: Public
-
400-2093
10 buckets, 20 gsi indexes
6 nodes, ( 2 kv+index+query, 4 are kv only)
attached screenshots for system configuation
- item count
- services on different nodes in the cluster
-
Untriaged
-
Centos 64-bit
-
Unknown
Description
0. Create cluster, create indexes - all online and ok.
1. Load tpcc data of 100 warehouses on the buckets ( see attached screenshot for item distribution)
2. Run mutations, queries on this cluster for about 4 hours
- seeing indexer crashing on one of the index nodes 10.6.2.164
Port server indexer on node 'babysitter_of_ns_1@127.0.0.1' exited with status 1. Restarting. Messages: runtime.goexit()
/usr/local/go/src/runtime/asm_amd64.s:2232 +0x1 fp=0xc24fc0df88 sp=0xc24fc0df80
created by github.com/couchbase/indexing/secondary/indexer.(*flusher).flushQueue
/home/couchbase/jenkins/workspace/sherlock-unix/goproj/src/github.com/couchbase/indexing/secondary/indexer/flusher.go:195 +0x929
[goport] 2015/05/12 14:37:53 /opt/couchbase/bin/indexer terminated: signal: aborted (core dumped)
logs
https://s3.amazonaws.com/cb-customers/r/1/collectinfo-2015-05-13T175739-ns_1%4010.6.2.164.zip
https://s3.amazonaws.com/cb-customers/r/1/collectinfo-2015-05-13T175739-ns_1%4010.6.2.167.zip
https://s3.amazonaws.com/cb-customers/r/1/collectinfo-2015-05-13T175739-ns_1%4010.6.2.168.zip
https://s3.amazonaws.com/cb-customers/r/1/collectinfo-2015-05-13T175739-ns_1%4010.6.2.194.zip
https://s3.amazonaws.com/cb-customers/r/1/collectinfo-2015-05-13T175739-ns_1%4010.6.2.195.zip
