Repository navigation
Configure idle suspension alongside node capacity - #687
Merged
Merged
Conversation
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.
Automatic suspension was fixed at five minutes. Nodes now provides one capacity and suspension area: operators edit node limits there and save a deployment-wide idle timeout of 30–86,400 seconds (default 300). Necessary explanations use help tooltips.
Core stores the timeout in the deployment row and reads it under the existing lifecycle transaction, so current allocations adopt changes without a restart or generation rollout. Already-started suspension, snapshot retention and early reclamation under capacity pressure keep their behavior. PATCH uses the existing deployment resource; provider and public protocols are unchanged. Generated administration schema/client and English/Chinese documentation are updated.
Validation: independent review without actionable findings; deployment/API/execution/server unit tests, complete deployment PostgreSQL tests, 34 affected integration tests and focused API tests passed. Client 719, Web 384 plus focused follow-ups, four browser scenarios, typecheck/build, Go vet and three translation checks passed.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.