3 people d4ec8a178f Changing rate limiters to return ResourceScope in ResouceExhausted error (#5605) ...

## What changed?
Changing rate limiters to return resource scope in ResourceExhausted
errors.
ResourceScope is a new field added to ResourceExhaustedFailure to
specify if the namespace level or system level resource is exhausted.
Also added this field to other ResourceExhausted errors.

## Why?
We need to differentiate whether a request has been rate-limited because
of namespace limit or system limit.
This will help us better understand why requests are rate-limited and
which limits to adjust.

## How did you test it?
Unit tests. Will add more tests for persistence rate-limited clients.

## Potential risk
None

## Documentation

## Is hotfix candidate?
No

---------

Co-authored-by: Tim Deeb-Swihart <[email protected]>

2024-03-29 18:54:28 +00:00

..

cluster_metadata_manager.go

Add HTTP address field to ClusterInformation (#5627)

2024-03-29 11:03:11 -07:00

history_v2_persistence.go

Remove GetHistoryTree from persistence manager (#5410)

2024-02-14 12:26:22 -08:00

metadata_persistence_v2.go

Replace gogo/protobuf with google/protobuf (#5032)

2023-11-21 15:19:37 -08:00

persistence_test_base.go

Changing rate limiters to return ResourceScope in ResouceExhausted error (#5605)

2024-03-29 18:54:28 +00:00

queue_persistence.go

Replace gogo/protobuf with google/protobuf (#5032)

2023-11-21 15:19:37 -08:00

setup.go

Refactor var names related to visibility mysql8 and postgres12 (#5464)

2024-02-29 13:54:30 -06:00

shared_test.go

Use vanity import package name go.temporal.io/server (#511)

2020-07-08 16:09:12 -07:00