moveChunk in multi_stmt_txn_jscore_passthrough_with_migration can cause failures when mongos retries commands that are not idempotent

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • v4.4
    • Sharding 2020-03-09, Sharding 2020-03-23, Sharding 2020-04-06
    • 9
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      An example scenario with dropIndex with 2+ shards:

      1. test sends dropIndex to mongos.
      2. dropIndex successfully runs in shard0.
      3. dropIndex returns StaleConfig error in shard1 because of migration.
      4. Mongos retries dropIndex but got index does not exist error because it is already dropped in shard0.

            Assignee:
            Blake Oler
            Reporter:
            Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: