Avoid querying previous config.placementHistory documents when inserting new ones

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.1.0-rc0, 7.0.0-rc1
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • v7.0
    • Sharding EMEA 2023-05-01
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      While most DDLs just insert new document into config.placementHistory as part of their commit, moveChunk and renameCollection perform first a lookup into the same collection to retrieve the latest placement information and build a new document on top of it.

      If such behaviour were removed, it could be possible to perform arbitrary trimming of the config.placementHistory log without the need to block any DDL.

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

              Created:
              Updated:
              Resolved: