[SERVER-62079] remove scanning RSM Created: 15/Dec/21  Updated: 29/Oct/23  Resolved: 26/May/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.3.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Lamont Nelson Assignee: Andrew Witten (Inactive)
Resolution: Fixed Votes: 0
Labels: sharding-nyc-subteam2, sharding-remove-scanning-rsm
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-62620 Link in version_impl and transport_la... Closed
Related
related to SERVER-62784 Complete TODO listed in SERVER-62079 Closed
Backwards Compatibility: Fully Compatible
Participants:

 Description   

This implementation of the RSM interface is redundant at this point and should be removed.



 Comments   
Comment by Githook User [ 19/Jan/22 ]

Author:

{'name': 'Davis Haupt', 'email': 'davis.haupt@mongodb.com', 'username': 'davish'}

Message: SERVER-62079 removes rsm scanning
Branch: master
https://github.com/mongodb/mongo/commit/ac9d5b9ea14af74e9b4ba3bad952cf4442fa4b93

Comment by Davis Haupt (Inactive) [ 14/Jan/22 ]

After removing kScanning from the enum, this patch build shows that no other tests are failing besides the unit test mentioned in SERVER-62620, implying no other changes should need to be made besides that ticket.

Comment by Davis Haupt (Inactive) [ 13/Jan/22 ]

The first step to remove the scanning RSM is to remove it as an option from ReplicaSetMonitorProtocol. After that, the compiler will guide most of the changes, with the exception being tenant_migration_donor_service_test. I opened SERVER-62620 with more details on the changes necessary to get that test to pass.

The next thing that I'm planning on investigating is if there are any errors in an evergreen patch build when the kScanning enum option is removed.

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