Web Session stuck with OperationTimeout after faileover about couchbase-aspnet HOT 10 CLOSED

@jbengit -

v3.0 is up on NuGet w/Couchbase SDK 2.6.0 official release.

from couchbase-aspnet.

@jbengit Thanks for the bug report, we'll look to reproduce and see what's going on.

from couchbase-aspnet.

Thank you. I reproduced the issue again with the following steps:

1. Stop two nodes at the same time in which the web sessions were present
   => the page waited for a response infinitely
2. Failover manually the two nodes and rebalance
   => the page responded (no error) and the website was up again
3. Restart the two missing nodes and join
4. Rebalance the cluster
   => From this point, the page responded after a delay of 30-40 seconds, with "Operation Timeout" and "VBucketBelongsToAnotherServer" in client logs (recycle did not help)
   => For new web sessions, no encountered issues
   => In the client settings, one node among the three was missing in the "servers" section. When I added it, the issue on the existing web session disappeared.
   It seems that for some specific cases of node failures, the client needs to be aware of all the nodes in the cluster.

from couchbase-aspnet.

Hi @jbengit - can you let me know what version of the CouchbaseNetClient package you're using? It's the actual library that interacts with the Couchbase cluster and is a dependency of the couchbase-aspnet package. The latest version (as of 12th June) is 2.5.12.

CouchbaseNetClient - Release Notes - Nuget

from couchbase-aspnet.

We are using the Couchbase.NetClient v2.5.10

from couchbase-aspnet.

@jbengit -

Have you tried beta Beta3? It may be a resolved issue.

-Jeff

from couchbase-aspnet.

@jeffrymorris
We did not try the Beta3 because it depends on a beta version of the couchbase sdk client.
Which couple of versions (CouchbaseNetClient + couchbase-aspnet) should be used for a production environment (Couchbase Community edition 5.0.1, or Enterprise 5.1.1 version)?

from couchbase-aspnet.

@jbengit -

Can you try Beta 3 in a non-production environment? If there are any issues, we can squeeze bug fixes in before EOM.

v2.0 is probably the most stable, but uses the CB 4.0 way of doing authentication (non-RBAC). Very soon v3 (Around the 1st week of July 2018) will be released along with SDK 2.6.0; I would suggest waiting for v3 in production if you can.

• Jeff

from couchbase-aspnet.

Thank you! I will try it.
The log4net and / or NewtonSoft.Json additional dependencies are really required or is it possible to remove them in a future version?

from couchbase-aspnet.

@jbengit -

I removed the dependencies on log4net and NewtonSoft.JSON on main project. Thanks for reporting.

from couchbase-aspnet.