Details
-
Bug
-
Resolution: Fixed
-
Critical
-
2.3.1
-
None
-
Security Level: Public
-
None
Description
[EDIT] remove previous description after analysis
This is specific to the case when there is only a single node and a new node is being added. In this case we will get a not-my-vbucket during the first relocation. Since the node has not yet been added (the current I/O handler must first return to the event loop) the client has nowhere that it can forward the command to, and ends up dispatching it with a not-my-vbucket.