I've also attached the logs and graphs for the Rb2OutEpt test that also fails in the same way. The test is the same test as the above but rebalances out the entry point node as one of the two -
Hi @Will Broadbelt what version (or SHA) of gocb is this against? It looks like the node (or nodes) that the "view not found" error is coming from is failing authentication. It's doing SCRAM auth and the first step succeeds but the second step we're getting auth fail back.
I'll see if I can get this running locally and shed some more light on it.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
Picking up a couple failures in situational testing with the particular test Rb2Out (& Rb2OutEpt) where the view queries begin to fail after the test rebound. Looking at the logs the reason reported seems to be that the 'connection is refused' and then that the 'views is not found' - which is odd as the there are a mixture of successful and non-successful view queries in the same time period as is shown on the graphed output: http://sdk-testresults.couchbase.com.s3.amazonaws.com/SDK-SDK/CB-6.5.0-4960/Rb2Out-HYBRID/02-13-20/054368/de3501131132927a5fd6cf7afb2a70ba-HT.html
Ive attached the sdk (
), sdkd (
) logs and the spreadsheet of results (
) for the test.
I've also attached the logs and graphs for the Rb2OutEpt test that also fails in the same way. The test is the same test as the above but rebalances out the entry point node as one of the two -
(Using gocb v2.0.0, gocbcore v8.0.1)