Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-50995

Investigate resiliency to, or prohibition of, direct modifications to config.shards

    • Type: Icon: Improvement Improvement
    • Resolution: Works as Designed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Sharding
    • 0

      it is currently possible to perform manual/direct modifications to documents in config.shards on a live sharded cluster, even though this is not supported and has undefined consequences, including rendering the cluster inoperable. We should investigate if we want to make the system tolerant of such changes (and if so, in what way), or if they should be completely disallowed on running systems. (Note that it should probably never be disallowed completely, since it is sometimes necessary in order to fix unexpected issues.)

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            kevin.pulo@mongodb.com Kevin Pulo
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: