Revisit kStartingTransaction for getMore retries in the AsyncRequestsSender

XMLWordPrintableJSON

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

      As patrick.freed@mongodb.com pointed out in this code review, the getMore retry strategy refresh code added in SERVER-129898 could always apply kNotStartingTransaction for getMores, since a getMore can't start a transaction. The net effect shouldn't change since we'd use the kStrictlyNotIdempotent retry policy anyway, but it would be conceptually more correct.

            Assignee:
            Unassigned
            Reporter:
            Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: