Travis Turner d28170ddc6 Syncs AvailableShards when handling a ResizeInstruction. ... There was a situation where availableShards on a new node were not in sync with the cluster, so queries following a resize were incorrect. - Start a one-node cluster. - Write data to shards 0 and 1 - Start a second node. In the case where the hash algo was moving shard 0 to node1, then node1 only knew about shard 0, so queries to node1 would be incomplete. This PR modifies the ResizeInstruction message to replace `Schema` with `NodeStatus` (which contains both `Schema` and `AvailableShards`). So now when a resize instruction is received, the receiving node is able to sync its schema and availableShards.		2018-12-18 08:34:48 -06:00
..
clustertests	fix bug where cluster goes into RESIZING instead of NORMAL	2018-12-11 09:22:03 -06:00
test	implements Not() query	2018-09-11 15:29:43 -05:00
internal.go	Apply Apache License 2.0	2017-04-28 14:22:03 -05:00
LICENSE	Add LICENSE to internal/ folder.	2017-05-01 20:32:04 -05:00
private.pb.go	Syncs AvailableShards when handling a ResizeInstruction.	2018-12-18 08:34:48 -06:00
private.proto	Syncs AvailableShards when handling a ResizeInstruction.	2018-12-18 08:34:48 -06:00
public.pb.go	Merged with master	2018-11-26 17:03:38 +03:00
public.proto	Merged with master	2018-11-26 17:03:38 +03:00