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

Consider deleting config.cache documents on config servers during setFCV downgrade

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Sharding NYC

      Config servers can accumulate these documents when they become catalog shards. Normally, they would be harmless to keep around. Even if we transition them to dedicated config servers back to catalog shards multiple times, the catalog cache loader logic can handle updating/auto-correcting the cached documents. However, if the collection is dropped while it is in dedicated config server (either in v6.0 or v7.0), these documents can stay there forever.

            Assignee:
            backlog-server-sharding-nyc [DO NOT USE] Backlog - Sharding NYC
            Reporter:
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: