[SERVER-66313] Defragmentation utils should use a direct connection to shards to check the feature flag Created: 09/May/22  Updated: 11/May/22  Resolved: 11/May/22

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

Type: Bug Priority: Major - P3
Reporter: Allison Easton Assignee: Allison Easton
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-65956 Skip "SplitChunks "Phase of Collectio... Closed
Operating System: ALL
Sprint: Sharding EMEA 2022-05-16
Participants:

 Description   

The defragmentation util includes a check for whether the NoMoreAutosplitter feature flag is enabled. This check uses the feature flag utils which check both the feature flag value and the FCV (to make sure the feature flag is enabled on the version the node is actually running).

The current check in the defragmentation utils calls the the feature flag util with a connection to the mongos. Mongos have no FCV, therefore the feature flag library is not taking into account the FCV currently running.

We should amend the check to use a direct connection so that the feature flag util can correctly check the feature flag. We should also add in a comment or a check to the feature flag util to make sure callers are aware that the util should not be used from a mongos.



 Comments   
Comment by Allison Easton [ 11/May/22 ]

This is being addressed in a small follow-up ticket under SERVER-65956 which is in code review, so marking as a duplicate of that

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