Note that this issue is occuring frequently in our labs/testing, and the issue is easy to reproduce by putting the VM under some CPU load while the application executes the openBucket request. The issue does not appear 100% of the time under CPU load, but it does occur greater than 50% of the time. When the issue does occur, 75 seconds later a log appears showing the bucket was successfully opened (e.g. some timer popped). Some of the initial logs (right after the openBucket request) and the last few logs showing the “open bucket” response are shown below. If you need additional logs to help resolve this issue, please contact myself or jberglund.
2016.07.19 17:08:37:744 EDT | Debug | CommonPersistency | cb-io-1-3
[Couchbase] State (EndpointStateZipper) DEGRADED -> CONNECTED
2016.07.19 17:08:37:744 EDT | Debug | CommonPersistency | cb-io-1-3
[Couchbase] State (QueryService) DEGRADED -> CONNECTED
2016.07.19 17:08:37:744 EDT | Debug | CommonPersistency | cb-io-1-2
[Couchbase] [id: 0x2e967224, L:/10.16.128.27:40320 - R:couchbase158.rtx.broadsoft.com./10.17.4.158:8093] ACTIVE
2016.07.19 17:08:37:744 EDT | FieldDebug | CommonPersistency | cb-io-1-2
[Couchbase] [couchbase158.rtx.broadsoft.com./10.17.4.158:8093][QueryEndpoint]: Channel Active.
2016.07.19 17:08:37:745 EDT | FieldDebug | CommonPersistency | cb-io-1-2
[Couchbase] [couchbase159.rtx.broadsoft.com./10.17.4.159:8092][ViewEndpoint]: Connected Endpoint.
2016.07.19 17:08:37:745 EDT | Debug | CommonPersistency | cb-io-1-2
[Couchbase] State (ViewEndpoint) CONNECTING -> CONNECTED
2016.07.19 17:08:37:745 EDT | Debug | CommonPersistency | cb-io-1-2
[Couchbase] State (EndpointStateZipper) CONNECTING -> DEGRADED
2016.07.19 17:08:37:745 EDT | Debug | CommonPersistency | cb-io-1-2
[Couchbase] State (ViewService) CONNECTING -> DEGRADED
… many more logs
2016.07.19 17:08:37:850 EDT | FieldDebug | CommonPersistency | cb-io-1-3
[Couchbase] Connected (DEGRADED) to Node couchbase159.rtx.broadsoft.com./10.17.4.159
2016.07.19 17:08:37:850 EDT | Debug | CommonPersistency | cb-io-1-3
[Couchbase] State (CouchbaseNode) DEGRADED -> CONNECTED
2016.07.19 17:08:37:851 EDT | FieldDebug | CommonPersistency | RxCachedThreadScheduler-1
CouchbaseEvent: NodeConnectedEvent{host=couchbase159.rtx.broadsoft.com./10.17.4.159}
2016.07.19 17:08:37:851 EDT | Info | CommonPersistency | RxCachedThreadScheduler-1
SystemEvent: Node Connected Event for host couchbase159.rtx.broadsoft.com./10.17.4.159
2016.07.19 17:08:37:852 EDT | FieldDebug | CommonPersistency | cb-io-1-3
[Couchbase] [couchbase159.rtx.broadsoft.com./10.17.4.159:11210][KeyValueEndpoint]: Channel Active.
2016.07.19 17:08:43:429 EDT | FieldDebug | CommonPersistency | cb-computations-1
[Couchbase] Received signal for outdated configuration.
… many more logs (and approx. 75 seconds after the openBucket request)
2016.07.19 17:09:52:922 EDT | FieldDebug | CommonPersistency | cb-computations-1
[Couchbase] [couchbase159.rtx.broadsoft.com.]: Service QUERY already added, skipping.
2016.07.19 17:09:52:922 EDT | Info | CommonPersistency | cb-computations-1
[Couchbase] Opened bucket bwsub
The previous post listed the version of the couchbase jars we are using (shown below as well), but I verified the issue exists in older jar files (from 5 months ago) as well.
couchbase-core-io-1.2.9.jar
couchbase-java-client-2.2.8.jar
rxjava-1.0.17.jar
Thanks