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

Metadata should become read-only when mongos detects config databases being different

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • 2.4.14
    • Sharding
    • None
    • 2 shards, 3 config servers
    • Sharding
    • ALL

    Description

      If mongos detects that config servers are different, metadata should not be changed.

      • Ongoing split/moveChunks operations can lead to the full inconsistency if the first config is corrupted for some reason;
      • Ongoing metadata changes can mask the original issue

      I checked manually with 2.4.1, and I could do manual splitAt and moveChunk, while my second config server was out of sync.

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            alex.komyagin@mongodb.com Alexander Komyagin
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: