Loading...

XML

Word

Printable

Prior to Faster Failover, NotMyVBucket responses would trigger an immediate re-fetch of the bucketconfig.

When Faster Failover is available, the logic should be

If the response contains a new BucketConfig, use that.
Otherwise, treat the NMVB as a notice that the current config is out of date, just as if we got a config push.

For Gerrit Dashboard: NCBC-3740
#	Subject	Branch	Project	Status	CR	V
207463,8	NCBC-3740: Should not trigger a full config fetch request in response to NMVB when Faster Failover is available.	master	couchbase-net-client	Status: MERGED	+2	+1
207464,2	(WIP) NCBC-3740: Should not trigger a full config fetch request in response to NMVB when Faster Failover is available.	master	couchbase-net-client	Status: ABANDONED	0	+1

There are no open Gerrit changes

Hide There are 2 closed Gerrit changes

NCBC-3740: Should not trigger a full config fetch request in response to NMVB when Faster Failover is available.: Gerrit Review:

(WIP) NCBC-3740: Should not trigger a full config fetch request in response to NMVB when Faster Failover is available.: Gerrit Review:

In Faster Failover mode, NotMyVBucket always result in a GetClusterMap request.