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

Retryable write may execute more than once in sharded clusters when collection namespace is reused after drop or rename

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Catalog and Routing
    • ALL
    • CAR Team 2024-03-04, CAR Team 2024-03-18, CAR Team 2024-04-01, CAR Team 2024-04-15, CAR Team 2024-04-29, CAR Team 2024-05-13, CAR Team 2024-05-27, CAR Team 2024-06-10, CAR Team 2024-06-24, CAR Team 2024-07-08, CAR Team 2024-07-22, CAR Team 2024-08-05, CAR Team 2024-08-19, CAR Team 2024-09-02, CAR Team 2024-09-16, CAR Team 2024-09-30, CAR Team 2024-10-14, CAR Team 2024-10-28, CAR Team 2024-11-11, CAR Team 2024-11-25

      The shard which originally owned the data for the collection namespace in the first incarnation may not be the same shard as the one which own data for the collection namespace in the second incarnation. The lack of an entry in the second shard's config.transactions collection permits the second shard to perform the retryable write for a second time.

            Assignee:
            josef.ahmad@mongodb.com Josef Ahmad
            Reporter:
            max.hirschhorn@mongodb.com Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated: