Indexer crash in longevity run

Build 2009

Fairly long running workload constantly adding new items, at some point the indexer crashed. There are 9 MOI indexes on it, the memory usage now is much lower than what it was previously and the indexes are constantly in "bootstrap".

Service 'indexer' exited with status 1. Restarting. Messages: runtime.goexit()
/home/couchbase/.cbdepscache/exploded/x86_64/go-1.6/go/src/runtime/asm_amd64.s:1998 +0x1 fp=0xc826d32fb0 sp=0xc826d32fa8
created by net/http.(*Transport).dialConn
/home/couchbase/.cbdepscache/exploded/x86_64/go-1.6/go/src/net/http/transport.go:853 +0x10a6
[goport] 2016/04/03 02:12:03 /opt/couchbase/bin/indexer terminated: signal: aborted
Service 'indexer' exited with status 1. Restarting. Messages: runtime.goexit()
/home/couchbase/.cbdepscache/exploded/x86_64/go-1.6/go/src/runtime/asm_amd64.s:1998 +0x1 fp=0xc8269effb0 sp=0xc8269effa8
created by github.com/couchbase/gometa/common.NewPeerPipe
/home/couchbase/jenkins/workspace/watson-unix/goproj/src/github.com/couchbase/gometa/common/peerPipe.go:60 +0x142
[goport] 2016/04/03 00:51:03 /opt/couchbase/bin/indexer terminated: signal: aborted

The indexer node is: ec2-54-219-64-21.us-west-1.compute.amazonaws.com

Logs are at:
https://s3.amazonaws.com/cb-engineering/perry/samsung/collectinfo-2016-04-03T021908-ns_1%40ec2-54-215-123-219.us-west-1.compute.amazonaws.com.zip
https://s3.amazonaws.com/cb-engineering/perry/samsung/collectinfo-2016-04-03T021908-ns_1%40ec2-54-219-195-14.us-west-1.compute.amazonaws.com.zip
https://s3.amazonaws.com/cb-engineering/perry/samsung/collectinfo-2016-04-03T021908-ns_1%40ec2-54-219-197-161.us-west-1.compute.amazonaws.com.zip
https://s3.amazonaws.com/cb-engineering/perry/samsung/collectinfo-2016-04-03T021908-ns_1%40ec2-54-219-255-167.us-west-1.compute.amazonaws.com.zip
https://s3.amazonaws.com/cb-engineering/perry/samsung/collectinfo-2016-04-03T021908-ns_1%40ec2-54-219-64-21.us-west-1.compute.amazonaws.com.zip