[SERVER-47048] Test that mongos can find primary despite "ping" failures Created: 23/Mar/20  Updated: 29/Oct/23  Resolved: 17/Apr/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.4.0-rc2, 4.7.0

Type: Task Priority: Major - P3
Reporter: Janna Golden Assignee: Cheahuychou Mao
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.4
Sprint: Service arch 2020-04-20
Participants:

 Description   

The new protocol uses a ping command to determine RTT, but the success/failure of the ping should not affect the RSM's ability to discover a node. In order to test this, cause a primary node to fail all ping requests, and check that mongos can still find the primary and does not mark it as down.



 Comments   
Comment by Githook User [ 20/Apr/20 ]

Author:

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

Message: SERVER-47048 Test that mongos can find primary despite "ping" failures

(cherry picked from commit 05eb5a55e9a7f50db04c0a7a12e6cd06248bbab5)
Branch: v4.4
https://github.com/mongodb/mongo/commit/30e8c4e7b3cefa766274316867f4e5c5a12bbc3b

Comment by Githook User [ 17/Apr/20 ]

Author:

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

Message: SERVER-47048 Test that mongos can find primary despite "ping" failures
Branch: master
https://github.com/mongodb/mongo/commit/05eb5a55e9a7f50db04c0a7a12e6cd06248bbab5

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