resharding_generate_oplog_entries.js should retry on TransientTransactionError

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Cluster Scalability
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The resharding donor machinery forces an asynchronous catalog refresh which might end up happening during a second statement of any of the transactions in the resharding_generate_oplog_entries.js. Since a lock is hold, this generates a ShardCannotRefreshDueToLocksHeld.

      In case this error is reported during a second or higher statement of the transaction, the router returns the error up to the user as a form of TransientTransactionError, which should be handled.

            Assignee:
            [DO NOT USE] Backlog - Cluster Scalability
            Reporter:
            Enrico Golfieri
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: