Skip to content

Conversation

@bergundy
Copy link
Member

Why?

To differentiate between a namespace that's temporary unavailable and not active.
This new failure will be returned with a gRPC unavailable error and should be retried by clients automatically.

@bergundy bergundy requested review from a team as code owners November 19, 2024 14:43
string active_cluster = 3;
}

// NamespaceUnavailableFailure is returned by the service when a request addresses a namespace that is unavailable. For
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

worth call out that this is transient error that should be retried.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that's already captured by the fact that it's an unavailable error but I'll clarify.

@bergundy bergundy enabled auto-merge (squash) November 19, 2024 17:42
@bergundy bergundy merged commit 13e49f9 into temporalio:master Nov 19, 2024
2 checks passed
@bergundy bergundy deleted the namespace-unavailable-failure branch November 19, 2024 17:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants