[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:
Backports
Depends
is depended on by SERVER-47050 Add FCV test to check wire versions i... Closed
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: SERVER-47560 Include "internalClient" field in ReplicaSetMonitor isMaster requests

(cherry picked from commit e84cf820af0e835b822f6599794ce8f4568c56b8)
Branch: v4.4
https://github.com/mongodb/mongo/commit/f6d2dfefec7ffb0d3c3819dd29013a25f192048e

Comment by Githook User [ 20/Apr/20 ]

Author:

{'name': 'Cheahuychou Mao', 'email': 'cheahuychou.mao@mongodb.com', 'username': 'cheahuychou'}

Message: SERVER-47560 Include "internalClient" field in ReplicaSetMonitor isMaster requests
Branch: master
https://github.com/mongodb/mongo/commit/e84cf820af0e835b822f6599794ce8f4568c56b8

Generated at Thu Feb 08 05:14:32 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.