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

Simplify exact_shard_key_target.js so that it does not depend on orphan writing

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.3.0
    • Affects Version/s: None
    • Component/s: Sharding
    • Fully Compatible
    • Sharding EMEA 2022-01-10

      As a consequence of PM-2423, write operations to orphan documents have no effect on the actual data, leaving it unchanged on disk and waiting for range deleter to do its job.

      The exact_shard_key_target.js test verifies that shard key targeted update/delete operations go to exactly one shard when targeted by nested shard keys. This is currently based on explicit insertion of orphan documents, requiring now additional logic to properly handle the new behavior of writes to orphans.

      Evaluate a new implementation in order to achieve the same test's goals without using orphan documents.

      Refer to this comment for more information on the requirement.

            Assignee:
            antonio.fuschetto@mongodb.com Antonio Fuschetto
            Reporter:
            antonio.fuschetto@mongodb.com Antonio Fuschetto
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: