Page MenuHomePhabricator

[identity] Send RETRY for transaction conflicts
AcceptedPublic

Authored by bartek on Wed, Oct 2, 1:07 AM.
Tags
None
Referenced Files
F2869089: D13568.diff
Wed, Oct 2, 4:23 PM
F2865527: D13568.diff
Wed, Oct 2, 8:55 AM
F2865081: D13568.id.diff
Wed, Oct 2, 7:55 AM
F2864429: D13568.id.diff
Wed, Oct 2, 6:13 AM
F2863058: D13568.id44812.diff
Wed, Oct 2, 3:23 AM
F2863022: D13568.id.diff
Wed, Oct 2, 3:22 AM
F2862940: D13568.diff
Wed, Oct 2, 3:21 AM
Subscribers

Details

Reviewers
varun
will
Summary

Part of ENG-9427.

  • Added a function that checks if DDB error is transaction conflict (we already have one but this one is more opinionated)
  • Added a case to handle_db_error to send retry tonic message instead of unexpected error

Depends on D13567

Test Plan

Simulated TransactionConflictException DDB error and checked gRPC status code in a UI client

Diff Detail

Repository
rCOMM Comm
Lint
No Lint Coverage
Unit
No Test Coverage