.NET Client 2.1.1 leaks connections when bucket does not exist




CouchbaseClientsComparison2x.zip (25.9 KB)

If the .NET Couchbase Client attempts to
.GetBucket() on a bucket that’s in the configuration, but does not
exist, the client will throw an AggregateException. Additionally, the
client will leak connections (equal to the min pool size) for every

This is easily duplicated with the test project I’ve attached.

To do so, just ensure that bucket4 doesn’t exist (or change to use bucketNE).

You can monitor the connections on the couchbase server.


From the issue:

@Unhuman -

Thanks for reporting; were planning on refactoring the bootstrapping logic in the near future, so we’ll take care of this then.