SG 2.6 (Couchbase Sync Gateway/2.6.0(127;b4c828d) CE)
Attached are the goroutines at the time of the crash. The first goroutine (…20_28_33) is when a user crashed the SG. Second goroutine was me by testing the oneshot push replication (i.e. signing in to an account the first time). Heap and goroutine are downloaded and stored automatically as soon as the SG crashes/hangs. Then it’s restarted.
This issue is reproducible on my production cluster! It worked on my dev cluster - a lot less powerful, single user only. Production cluster might have around 200 concurrent sync users. So not too many. There is lots of unallocated RAM and IDLE compute resources available. Prod and dev have the same software installed.
Is this issue related to my other post?
(By SG crash I mean that all connected Android clients show the replication status BUSY. No changes are synced until the SG service is restarted.)