docs: document the partition-count ceiling and autoscaling guidance - #392
Merged
Conversation
tillrohrmann
force-pushed
the
docs/cluster-sizing
branch
from
August 31, 2026 18:28
515a523 to
d039723
Compare
tillrohrmann
force-pushed
the
docs/cluster-sizing
branch
from
August 31, 2026 20:23
d039723 to
34d504e
Compare
tillrohrmann
force-pushed
the
docs/cluster-sizing
branch
2 times, most recently
from
August 31, 2026 20:34
c7a628d to
924aec4
Compare
tillrohrmann
force-pushed
the
docs/cluster-sizing
branch
from
August 31, 2026 20:45
924aec4 to
9490285
Compare
tillrohrmann
force-pushed
the
docs/cluster-sizing
branch
2 times, most recently
from
August 31, 2026 21:02
7e9c03d to
d49d637
Compare
tillrohrmann
force-pushed
the
docs/cluster-sizing
branch
3 times, most recently
from
August 31, 2026 21:10
7adbab0 to
e4f039d
Compare
tillrohrmann
marked this pull request as ready for review
August 31, 2026 21:10
gvdongen
approved these changes
Sep 1, 2026
tillrohrmann
force-pushed
the
docs/cluster-sizing
branch
from
September 4, 2026 14:31
e4f039d to
7e6dbce
Compare
tillrohrmann
force-pushed
the
docs/cluster-sizing
branch
from
September 5, 2026 12:08
7e6dbce to
65cc730
Compare
tillrohrmann
force-pushed
the
docs/cluster-sizing
branch
from
September 5, 2026 12:35
65cc730 to
8b4c9fb
Compare
Two gaps that led a customer to put an HPA in front of a 4-partition cluster and conclude Restate does not scale. The partition count caps how far a cluster can usefully scale out, since nodes beyond it hold no partition leader, and it is fixed at provisioning -- raising it means a new cluster and a migration. Neither fact appeared in "Sizing Clusters", where an operator would look. Autoscaling went unmentioned entirely, while the overview advertises "Horizontal Scaling" with no hint that resizing is manual in both directions. Adds a section saying so, plus a pointer from that table. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
tillrohrmann
force-pushed
the
docs/cluster-sizing
branch
from
September 5, 2026 13:02
8b4c9fb to
3e0b247
Compare
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
The partition count caps how far a cluster can usefully scale out, since
nodes beyond it hold no partition leader, and it is fixed at provisioning
-- raising it means a new cluster and a migration. Neither fact appeared
in "Sizing Clusters", where an operator would look.
Autoscaling went unmentioned entirely, while the overview advertises
"Horizontal Scaling" with no hint that resizing is manual in both
directions. Adds a section saying so, plus a pointer from that table.
Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com
Stack created with GitHub Stacks CLI • Give Feedback 💬