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

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

XMLWordPrintableJSON

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

      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@mongodb.com Sean Zimmerman
            Reporter:
            jason.zhang@mongodb.com Jason Zhang
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: