.NET client unavailable to service operations without connection to streaming API

Details

Description

When the client is configured with just one address (an HA proxy for example), and receives a timeout. Because this is the only server in the list, the client waits a full second before attempting to reconnect. During this time, all operations fail until it reconnects. There is another enhancement pending (http://www.couchbase.com/issues/browse/NCBC-36) to improve some of that behavior.

However, this bug is for the larger problem of not being able to service requests without a connection to the streaming API even though the vbucket map is still valid.

Have a few reports from customers stating that when the .NET client loses it's connection to the streaming API of the cluster, it causes data operations to fail.

When the client is configured with just one address (an HA proxy for example), and receives a timeout. Because this is the only server in the list, the client waits a full second before attempting to reconnect. During this time, all operations fail until it reconnects. There is another enhancement pending (http://www.couchbase.com/issues/browse/NCBC-36) to improve some of that behavior.

However, this bug is for the larger problem of not being able to service requests without a connection to the streaming API even though the vbucket map is still valid.

When the client is configured with just one address (an HA proxy for example), and receives a timeout. Because this is the only server in the list, the client waits a full second before attempting to reconnect. During this time, all operations fail until it reconnects. There is another enhancement pending (http://www.couchbase.com/issues/browse/NCBC-36) to improve some of that behavior.

However, this bug is for the larger problem of not being able to service requests without a connection to the streaming API even though the vbucket map is still valid.