3 people 71dcad0e44 Add api to Eager retrieve the unknown namespace from remote cluster (#4769) ...

<!-- Describe what has changed in this PR -->
**What changed?**
Add new API at AdminClient to retrieve the namespace from remote
cluster.

<!-- Tell your future self why have you made these changes -->
**Why?**
To allow the passive cluster eagerly retrieve the namespace from the
active cluster for the following reason:
1. Namespace Replication may failed and never reached to passive
cluster, and passive cluster received the replication task.

<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->
**How did you test it?**
Unit test.

<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->
**Potential risks**
N/A

<!-- Is this PR a hotfix candidate or require that a notification be
sent to the broader community? (Yes/No) -->
**Is hotfix candidate?**
No.

---------

Co-authored-by: Will Duan <[email protected]>

2023-08-14 13:37:36 -07:00

..

client_gen.go

Add api to Eager retrieve the unknown namespace from remote cluster (#4769)

2023-08-14 13:37:36 -07:00

client.go

Add replication stream receiver logic (#4093)

2023-03-28 10:05:18 -07:00

metric_client_gen.go

Add api to Eager retrieve the unknown namespace from remote cluster (#4769)

2023-08-14 13:37:36 -07:00

metric_client.go

Fix metrics double emission in admin and operator handler (#4613)

2023-07-11 11:35:24 -07:00

retryable_client_gen.go

Add api to Eager retrieve the unknown namespace from remote cluster (#4769)

2023-08-14 13:37:36 -07:00

retryable_client.go

Add gRPC replication stream (#4057)

2023-03-23 10:42:03 -07:00