Chetan GowdaandGitHub 76f7612aaa Retry on DataLoss error from persistence layer (#6789) ...

## What changed?
Added `serviceerror.DataLoss` to `IsPersistenceTransientError()` so that
we can retry on these errors. The number of times to retry is configured
by the retry policy (which is max 2 attempts)

## Why?
We've observed that the persistence layer may not always be reliable
especially when you read immediately after writing. With this change we
retry once before giving up.

## How did you test it?
Added unit tests

## Potential risks
If the retry policy is modified in the future, we may retry more than
once.

## Documentation
N/A

## Is hotfix candidate?
No

2024-11-12 19:06:24 +00:00

..

abstract_data_store_factory.go

Refactor fault injection package (#5886)

2024-05-10 17:47:36 -07:00

factory_test.go

Switch to uber gomock (#6493)

2024-09-09 14:44:20 -07:00

factory.go

Retry on DataLoss error from persistence layer (#6789)

2024-11-12 19:06:24 +00:00

fx.go

Refactor XDC cache (#6583)

2024-10-03 10:39:28 -07:00

health_request_rate_limiter.go

Use typed dynamic configs (#5962)

2024-06-03 18:16:15 -07:00

persistence_rate_limited_clients_test.go

Switch to uber gomock (#6493)

2024-09-09 14:44:20 -07:00

quotas_test.go

Import alignment (#6426)

2024-08-23 14:48:10 -06:00

quotas.go

Different error message for per namespace per shard rate limiting (#6433)

2024-08-30 18:47:36 +00:00