mongos should not take the repairDatabase operation

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: 1.6.0
    • Component/s: Sharding
    • None
    • Environment:
      CentOS 5.4 x86_64
    • Sharding
    • Linux
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            [DO NOT USE] Backlog - Sharding Team
            Reporter:
            Justin Lintz
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: