[SERVER-2352] mongos should not take the repairDatabase operation Created: 12/Jan/11  Updated: 06/Dec/22  Resolved: 08/Aug/18

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

Type: Bug Priority: Major - P3
Reporter: Justin Lintz Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

CentOS 5.4 x86_64


Issue Links:
Duplicate
duplicates SERVER-28872 remove ClusterRepairDatabaseCmd from ... Closed
Assigned Teams:
Sharding
Operating System: Linux
Participants:

 Description   

Recently I ran into an issue where I inadvertently connected to mongos instead of mongod and sent a repairDatabase command which instead of being run on the slave server got pushed out to the master servers. It seems it would be a bad idea to allow this to get proxied out to the masters. I think it should either not be allowed at all via mongos or prompt with a warning on certain commands.


Generated at Thu Feb 08 02:59:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.