Jason Wilder 43118ce78e Send database and retention policy with remote writes ... There was a race where a remote write could arrive before a meta client cache update arrived. When this happened, the receiving node would drop the write because it could not determine what database and retention policy the shard it was supposed to create belonged to. This change sends the db and rp along with the write so that the receiving node does not need to consult the meta store. It also allows us to not send writes for shards that no longer exist instead of always sending them and having the receiving node logs fill up with dropped write requests. This second situation can occur when shards are deleted and some nodes still have writes queued in hinted handoff for those shards. Fixes #5610		2016-03-01 21:23:03 -07:00
..
data.pb.go	Send database and retention policy with remote writes	2016-03-01 21:23:03 -07:00
data.proto	Send database and retention policy with remote writes	2016-03-01 21:23:03 -07:00