Document the per-Namespace Worker Controller Instance limit - #5199
Open
lennessyy wants to merge 1 commit into
Open
Document the per-Namespace Worker Controller Instance limit#5199lennessyy wants to merge 1 commit into
lennessyy wants to merge 1 commit into
Conversation
Adds a Max Worker Controller Instances entry to the Cloud limits page, covering the 100 default, that drained versions still count, and how it differs from the per-deployment version limit. Notes the limit in the serverless encyclopedia page and in both deploy guides at the step where a version is created.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
| @@ -398,3 +398,13 @@ The maximum number of versions that the server allows to be registered in a sing | |||
| ### Max Task Queues In Deployment Version limits {/* #max-task-queues-in-deployment-version-limits */} | |||
Contributor
There was a problem hiding this comment.
📝 [vale] <Temporal.Headings> reported by reviewdog 🐶
'Max Task Queues In Deployment Version limits *****************************************************' should use sentence-style capitalization.
Contributor
📖 Docs PR preview links
|
Contributor
There was a problem hiding this comment.
Pull request overview
Documents the per-Namespace Worker Controller Instance limit for Serverless Workers.
Changes:
- Adds the default limit, error, scope, and remediation.
- Adds limit guidance to Serverless Worker concepts and deployment guides.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
cloud-run/index.mdx |
Notes the limit during version creation. |
aws-lambda/index.mdx |
Notes the limit during version creation. |
limits.mdx |
Defines the Cloud limit and remediation. |
serverless-workers/index.mdx |
Explains WCI lifecycle and limit behavior. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Comment on lines
+93
to
+96
| A Namespace runs at most 100 WCI Workflows by default, which caps how many Worker Deployment Versions in the Namespace | ||
| can have a compute provider at once. A version's WCI runs until the version is deleted, so drained versions count | ||
| against the limit. See | ||
| [Max Worker Controller Instances limits](/cloud/limits#max-worker-controller-instances-limits). |
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
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
Verified against
temporal-auto-scaled-workersonmain:wci/client/config.go(workercontroller.maxInstances, default 100),wci/client/client.go(theResourceExhaustedcheck), and the visibility count query, which filters on running WCI Workflows only. The delete path intemporal'sversion_workflow.goremoves the WCI when the version is deleted, not when it drains.