Intermittent frequent Connect callback did not return
Description
When testing CBAS, we use java client to upsert documents. Frequently, our tests fail due to: com.couchbase.client.deps.io.netty.channel.ConnectTimeoutException: Connect callback did not return, hit safeguarding timeout. The last saved run which encountered this issue is available at at http://analytics.jenkins.couchbase.com/job/cbas-cbcluster-test/772
There is no need to investigate on the Analytics side as the code was restructured to avoid the issue.
Michael Nitschinger September 4, 2018 at 8:19 AM
Actually we gained insight on this over the last couple months: this is just because some op during the connect phase in the back and forth did not complete in time, so it is basically another connect timeout safety net.
Is this still an issue we need to investigate on the analytics side?
Michael Nitschinger September 25, 2017 at 5:30 PM
I'll add it to the next bugfix release but might need to go into the 1.5.2 depending on how much effort it is to figure out whats going on
Michael Nitschinger September 25, 2017 at 5:29 PM
That would be awesome, thanks!
Won't Do
Pinned fields
Click on the next to a field label to start pinning.
When testing CBAS, we use java client to upsert documents. Frequently, our tests fail due to:
com.couchbase.client.deps.io.netty.channel.ConnectTimeoutException: Connect callback did not return, hit safeguarding timeout.
The last saved run which encountered this issue is available at at http://analytics.jenkins.couchbase.com/job/cbas-cbcluster-test/772