[SERVER-80771] Implement cluster-wide maxWireVersion discovery mechanism Created: 05/Sep/23 Updated: 19/Sep/23 Resolved: 19/Sep/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Patrick Freed | Assignee: | Patrick Freed |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
In order to ensure that gRPC-based clients can properly identify a maxWireVersion supported by the entire routing layer through a load balancer, the routers need to report it via the gRPC metadata. In order for the routing layer itself to report a consistent value, a wire version discovery mechanism needs to be implemented. See the design for more details: https://docs.google.com/document/d/1MoNt1rCEXrOZplNPQrnEYdBxIoqvSNvXUAts4z78cv8/edit#heading=h.gq89gct6uf3u |
| Comments |
| Comment by Patrick Freed [ 19/Sep/23 ] |
|
Closing out in favor of SERVER-81068, which should address this issue in a transport-agnostic way. |