forked from cockroachdb/cockroach
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
kv, storage: mandate presence of range/store ID in batch requests
Some test code was relying on an ancient and obscure feature of the Stores sender where batch requests without a range and/or store ID could be routed by the request key. Normally, this routing is handled by DistSender. Remove this feature so that requests in tests follow the same path as requests in production. Fix the few tests that were relying on it to manually route their requests to the correct range/store. There are no mixed-version compatibility concerns here. Production code paths, with one exception, have long since guaranteed that batch request headers contain a range ID and store ID by the time they reach the Stores sender. The one exception is during bootstrapping of a fresh cluster, but there are no concerns about version compatibility because the requests are directed to the local store before any other nodes have joined the cluster. That code has been adjusted to use a wrapping sender that installs an appropriate range and store ID. Release note: None
- Loading branch information
Showing
6 changed files
with
70 additions
and
71 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters