Document Nexus with Global Namespaces (multi-region failover) for self-hosted#4906
Draft
stephanos wants to merge 1 commit into
Draft
Document Nexus with Global Namespaces (multi-region failover) for self-hosted#4906stephanos wants to merge 1 commit into
stephanos wants to merge 1 commit into
Conversation
Documents how Nexus Operation completion callbacks behave when a Global Namespace fails over between clusters, and the configuration required for worker-target endpoints: endpoint registry parity, replicated Namespaces, auto-forwarding, and a frontend httpPort plus advertised httpAddress on every cluster. Reorders "Build and use Nexus Services" above the new section. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
📖 Docs PR preview links
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a Global Namespaces (multi-region failover) section to the self-hosted Temporal Nexus guide (
production-deployment/self-hosted-guide/temporal-nexus.mdx), and reorders Build and use Nexus Services above it.Why
Self-hosted operators running Nexus across two regions need to know how asynchronous Operation completion callbacks survive a Global Namespace failover, and exactly what to configure. The previous guide implied Nexus was single-cluster only.
Key points
httpPortand advertiseclusterMetadata.clusterInformation.<cluster>.httpAddress; theoperator cluster upsertflow does not set the latter (cross-cluster callbacks otherwise fail withHTTPAddress not configured for cluster: <name>).system.enableNamespaceNotActiveAutoForwarding; register the endpoint in every region (the registry is not replicated).Verification
Verified end-to-end against a local two-region xDC setup: graceful failover, handler-only failover, and unplanned hard failover / permanent region loss.
Still to do (draft)
🤖 Generated with Claude Code
┆Attachments: EDU-6740 Document Nexus with Global Namespaces (multi-region failover) for self-hosted