You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Temporal Cloud customers (specifically those with more complicated network setups using Private Connectivity) encounter issues due to misconfigured Workers when a Namspace is failed over to a standby region in the event of an incident. To improve this user experience, we should consider switching to a per region end point and change our SDKs to natively handle failovers (instead of relying on manual user setup).
Describe the solution you'd like
There are three requirements in this task:
Allow SDK to be able to connect to multiple endpoints for a namespace. Typical use case is region specific endpoints for MRN, and different endpoints for on-prem to cloud migration.
SDK should send requests to the “active“ endpoint based on the ns info it gets from Temporal server.
SDK should health check both endpoints to prevent connection errors post namespace failover.
Per-SDK Tickets
TBA
The text was updated successfully, but these errors were encountered:
atihkin
changed the title
Allow SDK to support connecting to multiple endpoints for Multi-region Namespaces
Allow SDKs to support connecting to multiple endpoints for Multi-region Namespaces
Sep 13, 2024
Is your feature request related to a problem? Please describe.
Temporal Cloud customers (specifically those with more complicated network setups using Private Connectivity) encounter issues due to misconfigured Workers when a Namspace is failed over to a standby region in the event of an incident. To improve this user experience, we should consider switching to a per region end point and change our SDKs to natively handle failovers (instead of relying on manual user setup).
Describe the solution you'd like
There are three requirements in this task:
Per-SDK Tickets
TBA
The text was updated successfully, but these errors were encountered: