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

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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Won't Fix
    • Affects Version/s: 2.4.14
    • Fix Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Environment:
      2 shards, 3 config servers
    • Operating System:
      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

            Assignee:
            backlog-server-sharding Backlog - Sharding Team
            Reporter:
            alex.komyagin Alexander Komyagin
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: