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
..
proto.go	Syncs AvailableShards when handling a ResizeInstruction.	2018-12-18 08:34:48 -06:00