[SERVER-17980] CatalogManagerLegacy should not allow replica sets as config servers Created: 10/Apr/15  Updated: 25/Jan/17  Resolved: 23/Jul/15

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

Type: Bug Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: dnsf
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-17970 Restore check that prevents replica s... Closed
Related
related to SERVER-19414 Switch to using CatalogManagerReplica... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

As part of the work to allow replica sets as sharding config servers, we disabled the check for the config servers to be legacy-style.

This ticket is to remind us to put this check back in once we have the RS-enabled catalog manager in place.



 Comments   
Comment by Spencer Brody (Inactive) [ 23/Jul/15 ]

Fixed by https://github.com/mongodb/mongo/commit/ac6ebf125d320e1c5542ac91a86b3b159ae5945d

Generated at Thu Feb 08 03:46:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.