Prathyush PVandGitHub 209d75c895 Different error message for per namespace per shard rate limiting (#6433) ...

## What changed?
Different error message for per-shard per-namespace rate limiting. Shard
level rate limiting was done by namespaceRateLimiter object.
namespaceRatelimiter was a MultiRequestRateLimiter with both namespace
rate limiter and shard-level rate limiter. Here it is split into two so
we can differentiate between rate limiters and return appropriate error
messages.

## Why?
Currently, per-namespace rate limiter and per-shard per-namespace rate
limiter return the same error message.
It is difficult to pinpoint the reason for rate limiting in this case.

## How did you test it?
Unit tests

## Potential risks
None

## Documentation

## Is hotfix candidate?
No

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

..

cluster_metadata_manager.go

Import alignment (#6426)

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

history_v2_persistence.go

Import alignment (#6426)

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

metadata_persistence_v2.go

Import alignment (#6426)

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

persistence_test_base.go

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

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

queue_persistence.go

Import alignment (#6426)

2024-08-23 14:48:10 -06: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