Shard split write-during-aborted tests expect wrong outcome for writes

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Server Serverless 2022-11-14
    • 35
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Access blockers will always reject a write during a tenant migration with either TenantMigrationAborted or TenantMigrationCommitted. We have a test that performs a number of writes during a tenant migration, and then expects the result to be OK which is impossible. It's likely that these writes have been completing after the split has been aborted, which is why we haven't seen a failure in the last year.

            Assignee:
            Matt Broadstone
            Reporter:
            Matt Broadstone
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: