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

Implement granularity update for timeseries collection

    • Type: Icon: New Feature New Feature
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • QE 2021-11-15, QE 2021-11-29, QE 2021-12-13, QE 2021-12-27, QE 2022-01-10, QE 2022-04-04, QE 2022-02-07, QE 2022-02-21, QE 2022-03-07, QE 2022-03-21, QE 2022-01-24

      Currently during a granularity update, mongos and shards may see inconsistent granularity values. This causes read / write operations routed to wrong shards, and we need to have a consistent value for granularity during the update. The value will be stored on the config server, and read / write operations will be blocked temporarily during its update and use the config server value as the source of truth.

      See this document for more detailed discussion https://docs.google.com/document/d/1ljVx7gni5dg6vuLSL2li14lq13T2RqENWEGKKeliCzw/edit#heading=h.948j6cnha6ak.

            Assignee:
            rui.liu@mongodb.com Rui Liu
            Reporter:
            rui.liu@mongodb.com Rui Liu
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: