Skip to content

Fill gaps from assistant conversations: clarify protected tier and node updates #307

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mintlify wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Fill gaps from assistant conversations: clarify protected tier and node updates #307

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a10227d
docs: clarify compute tier behavior during node maintenance
mintlify[bot] Aug 3, 2026
28a352a
docs: improve SEO metadata and split long sentences on scaling apps page
mintlify[bot] Aug 3, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 10 additions & 2 deletions scaling/scaling-apps.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: "Scaling Apps"
description: "Learn to optimise for cost and performance by scaling out apps"
title: "Autoscaling apps on Cerebrium"
description: "Configure replicas, scaling metrics, load balancing, and compute tiers to scale Cerebrium apps for cost, latency, and availability."
---

Cerebrium's scaling system automatically manages computing resources to match app demand, from single requests to multiple simultaneous requests, optimizing for both performance and cost.
Expand Down Expand Up @@ -284,6 +284,14 @@ Interruptible instances can be interrupted in two ways: the cloud provider can r

Protected instances are excluded from capacity consolidation and never run on preemptible capacity, so they are not interrupted in either case.

### Node Maintenance and Updates

The `compute_tier` setting governs preemption and consolidation only. It does not opt an instance out of node lifecycle events such as OS patches, kernel upgrades, or platform rollouts. Both interruptible and protected instances can be migrated to a new node when the underlying node is cycled for maintenance. In every case the instance receives SIGTERM and is drained within `response_grace_period` before SIGKILL.

See [Graceful Termination](/scaling/graceful-termination) for the shutdown sequence. Custom runtimes must handle SIGTERM themselves so in-flight requests complete instead of returning 502s.

To minimize disruption during a migration, run with `min_replicas >= 2` so at least one replica remains available while another is drained. Set `response_grace_period` to cover your worst-case request duration.

**Choosing a tier:**

- Use `interruptible` (default) for batch workloads, development, or cost-sensitive applications that can tolerate occasional interruptions.
Expand Down
Loading