Description
In cases where a 'NOT_MY_VBUCKET' is received, the client will spin the command again and again until a proper server is received. In some cases (See MB-9448) it will take quite some time (i.e. several hundred seconds) for the server to reply with a correct map. In this case the client will hang for that long.
Since this seems to actually be a server bug, there is no current 'bug' to fix in libcouchbase; however some steps may be taken to solve this:
(1) Provide an option to not spin loop for a NOT_MY_VBUCKET response
(2) Provide a 'real_start' field in the command structure; after this point the response is failed out as being timed out.
Attachments
Issue Links
- is triggered by
-
MB-9448 vBucket configuration shows -1 for master for prolonged periods
- Closed