Optimize the compound index of config.placementHistory

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Sharding EMEA 2022-10-17
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The config.placementHistory collection is currently supported by a compound index defined as {nss: 1, timestamp: 1}; nevertheless, most queries sort documents in descending order of timestamp.

            Assignee:
            Paolo Polato
            Reporter:
            Paolo Polato
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: