If one of two nodes goes down then all get/set operations fail
I'm using couchbase-net-client and couchbase-aspnet to store our ASP.NET session in a Couchbase bucket. Doing testing in a two-node environment I'm finding that if a single node goes down then all sessions are essentially nulled. I have replicas enabled, so I would assume that if a get operation failed to one node, then it would try the replica node (and then swap active/replica flags).
Is that not the case? If not, using this solution results in an exponential decrease in reliability, as our site requires a session state to function. As it stands, if one of two nodes goes down then all get/set operations appear to fail. How can I fix this?