Skip to content

Conversation

@baileympearson
Copy link
Contributor

@baileympearson baileympearson commented Oct 29, 2025

Description

Summary of Changes

This PR adds exponential backoff between convenient transaction API failures if the transaction must be restarted. (DRIVERS-1934)

Release Highlight

withTransaction now applies exponential backoff during transaction retries

The convenient transaction API now uses exponential backoff between retries if a transaction must be retried. Under scenarios of high server load, this can prevent transaction retry storms.

Double check the following

  • Lint is passing (npm run check:lint)
  • Self-review completed using the steps outlined here
  • PR title follows the correct format: type(NODE-xxxx)[!]: description
    • Example: feat(NODE-1234)!: rewriting everything in coffeescript
  • Changes are covered by tests
  • New TODOs have a related JIRA ticket

@baileympearson baileympearson changed the title wip feat(NODE-7122): exponential backoff between retries in convenient transaction API feat(NODE-7122): exponential backoff between retries in convenient transaction API Nov 25, 2025
@baileympearson baileympearson marked this pull request as ready for review November 25, 2025 23:31
@baileympearson baileympearson requested a review from a team as a code owner November 25, 2025 23:31
@durran durran self-assigned this Nov 26, 2025
@durran durran added the Primary Review In Review with primary reviewer, not yet ready for team's eyes label Nov 26, 2025
durran
durran previously requested changes Nov 26, 2025
PavelSafronov
PavelSafronov previously approved these changes Dec 1, 2025
@dariakp dariakp assigned dariakp and unassigned durran Dec 1, 2025
@dariakp dariakp added Team Review Needs review from team and removed Primary Review In Review with primary reviewer, not yet ready for team's eyes labels Dec 1, 2025
@dariakp dariakp dismissed durran’s stale review December 2, 2025 21:17

comments addressed

@dariakp dariakp requested review from dariakp and removed request for durran December 3, 2025 18:10
@baileympearson
Copy link
Contributor Author

@dariakp Comments addressed. Sorry about the rebase + force push, force of habit 😅.

});
});

// 5. Compare the two time between the two runs.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And this is how we catch spec typos 😅 time -> times
let's update here and maybe include this in the next spec PR or as a one-off?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Team Review Needs review from team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants