[SERVER-25407] Potentially remove checkAdminDatabase() Created: 02/Aug/16  Updated: 06/Dec/22  Resolved: 02/Aug/16

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

Type: Improvement Priority: Major - P3
Reporter: Spencer Jackson Assignee: Backlog - Replication Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-21378 Add a setParameter that will bypass a... Closed
Assigned Teams:
Replication
Backwards Compatibility: Fully Compatible
Participants:

 Description   

Now that a node running with the 2.4 auth schema will never run in a mixed mode replicaset using the 2.6 auth schema or above, one could imagine removing the checkAdminDatabase() function from rs_initialsync.h.



 Comments   
Comment by Spencer Jackson [ 02/Aug/16 ]

However, this function is still valuable. There are corner cases, such as those described in SERVER-21378, where invalid authorization data can be ingested into a database. In these cases, we shouldn't allow it to replicate, potentially complicating database repair. It might be to prevent all ingestion of malformed system data by a reasonably determined restore administrator, but we do not currently do this. Until then, resolving this ticket would eliminate a valuable sanity check.

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