Details
-
Bug
-
Resolution: Fixed
-
Major
-
3.2.8
-
None
Description
Summary
When testing a .NET application against a development CB Server running multiple nodes via cluster_run, the .NET SDK fails to connect to the correct node, eventually giving up:
Unhandled exception. Couchbase.Core.Exceptions.AmbiguousTimeoutException: The operation /35 timed out after 00:00:02.5000000. It was retried 6 times using Couchbase.Core.Retry.BestEffortRetryStrategy.
|
at Couchbase.Utils.ThrowHelper.ThrowTimeoutException(IOperation operation, IErrorContext context)
|
at Couchbase.Core.Retry.RetryOrchestrator.RetryAsync(BucketBase bucket, IOperation operation, CancellationTokenPair tokenPair)
|
at Couchbase.KeyValue.CouchbaseCollection.UpsertAsync[T](String id, T content, UpsertOptions options)
|
at examples.Program.Main(String[] args) in /Users/dave/Documents/CBSE-11643-UPS-null_prefix/reproducer/Program.cs:line 20
|
at examples.Program.<Main>(String[] args)
|
-----------------------Context Info---------------------------
|
{"DispatchedFrom":"::1","DispatchedTo":"::1","DocumentKey":"key_1","ClientContextId":"35","Cas":0,"Status":0,"BucketName":"default","CollectionName":"_default","ScopeName":"_default","Message":null,"OpCode":"Set"}
|
Steps to reproduce
- Compile and run CB Server with multiple nodes on the same machine - e.g.
$ cd ns_server$ ./cluster_run -n2 - Setup at least 2 nodes
./cluster_connect -n2 - Attempt to perform some operations against the cluster where the key is not on the first node - for example reproducer from
NCBC-3171.
Attachments
Issue Links
- relates to
-
-
- Resolved
-