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

Understand why findAndModify upsert retry on DuplicateKey succeeds when it shouldn't

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • ALL
    • 200

      When we retry the reproducer of SERVER-95523 in a transaction, the write succeeds on a second try violating the unique index. Understand the reason even though _opCtx->_ruState got set to RecoveryUnitState::kFailedUnitOfWork (and crashes the server in commit).

            Assignee:
            evan.bergeron@mongodb.com Evan Bergeron
            Reporter:
            wei.hu@mongodb.com Wei Hu
            Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated: