Bulk write without shard key using the single shard optimization may target documents incorrectly

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • Fully Compatible
    • Repl 2024-04-01
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Similar to the issue in SERVER-87191, it looks like bulk writes without shard key uses getNShardsOwningChunks, which does not respect the atClusterTime in the case of a transaction with snapshot read concern. This can lead to inconsistent targeting as described in the previous ticket.

            Assignee:
            Sean Zimmerman
            Reporter:
            Jason Zhang (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: