[SERVER-5095] Clients should not be able to write to config chunks/databases/changelog/mongos/etc. collections directly via mongos Created: 25/Feb/12  Updated: 06/Dec/22  Resolved: 31/Oct/19

Status: Closed
Project: Core Server
Component/s: Admin, Sharding, Usability
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Critical - P2
Reporter: Scott Hernandez (Inactive) Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding
Operating System: ALL
Participants:

 Description   

We should force all changes to be done via commands or directly on the config db for maintenance/administration. This will remove the chance that accidents happen from rouge scripts/users.



 Comments   
Comment by Sheeri Cabral (Inactive) [ 31/Oct/19 ]

Sometimes this is needed for support workarounds.

Comment by Scott Hernandez (Inactive) [ 25/Feb/12 ]

I'm up for other options as long as we can isolate normal user operations from explicit admin/maint. operations.

You can do this from the mongo shell using the same type of connection mongos does if you specify the set of config servers. It is the same as I understand... if not we can make it better so you can.

Comment by Eliot Horowitz (Inactive) [ 25/Feb/12 ]

Doing things directly on the configdb is much much riskier as then you have to make sure you do it at the same time, where doing it via mongos takes care of that for you.

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