Description
Note: this is failure scenario; the node configured to bootstrap against has been failed over from the cluster. The proper behavior is to detect that SelectBucket failed and then raise the appropriate error message so that the developer can easily diagnose and fix the issue by changing the bootstrap node URI to be an active node.
at Couchbase.Core.Sharding.VBucketKeyMapper..ctor(BucketConfig config) in C:\Users\Jeff Morris\source\couchbase-net-client\src\Couchbase\Core\Sharding\VBucketKeyMapper.cs:line 26
at Couchbase.CouchbaseBucket.<BootstrapAsync>d__15.MoveNext() in C:\Users\Jeff Morris\source\couchbase-net-client\src\Couchbase\CouchbaseBucket.cs:line 188
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
at Couchbase.Core.ClusterContext.<BootstrapBucketAsync>d__43.MoveNext() in C:\Users\Jeff Morris\source\couchbase-net-client\src\Couchbase\Core\ClusterContext.cs:line 301
Believed to be fixed, as is not coming up in current tests. Deferring for further review by Jeff Morris.