[SERVER-47560] Include "internalClient" field in ReplicaSetMonitor isMaster requests Created: 15/Apr/20 Updated: 29/Oct/23 Resolved: 20/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.0-rc2, 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Cheahuychou Mao | Assignee: | Cheahuychou Mao |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Backport Requested: |
v4.4
|
||||||||||||
| Sprint: | Service arch 2020-04-20, Service arch 2020-05-04 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
The optional "internalClient" field in the isMaster request determines whether the internal or external client's minWireVersion and maxWireVersion are appended to the response. The StreamableReplicaSetMontior (and ScanningReplicaSetMonitor) currently sends isMaster requests without the optional "internalClient" field. This leads to incorrect minWireVersion and maxWireVersion in ServerDescription and TopologyDescription::checkWireCompatibilityVersions as the minWireVersion for external client is always 0. |
| Comments |
| Comment by Githook User [ 20/Apr/20 ] |
|
Author: {'name': 'Cheahuychou Mao', 'email': 'cheahuychou.mao@mongodb.com', 'username': 'cheahuychou'}Message: (cherry picked from commit e84cf820af0e835b822f6599794ce8f4568c56b8) |
| Comment by Githook User [ 20/Apr/20 ] |
|
Author: {'name': 'Cheahuychou Mao', 'email': 'cheahuychou.mao@mongodb.com', 'username': 'cheahuychou'}Message: |