Skip to content

docs: move graceful cluster reconfiguration availability from v26.34 to v26.35 #37894

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

Merged
maheshwarip merged 1 commit into from
Jul 27, 2026
Merged

docs: move graceful cluster reconfiguration availability from v26.34 to v26.35 #37894

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
28 changes: 0 additions & 28 deletions doc/user/content/releases/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,34 +55,6 @@ For more information, see the `AUTO SCALING STRATEGY` option on
[`CREATE CLUSTER`](/sql/create-cluster/#autoscaling) and
[`ALTER CLUSTER`](/sql/alter-cluster/#speed-up-hydration-by-autoscaling-to-a-larger-size).

### Graceful Cluster Reconfiguration {#v26.34-background-cluster-reconfiguration}
`ALTER CLUSTER` for configuration changes (such as resizing) now returns immediately and runs in the background, rather than blocking until the new replica set is ready.

Because the command is now asynchronous, you can monitor the
progress of an in-flight reconfiguration using `SHOW CLUSTERS`.

```mzsql
SHOW CLUSTERS;
```
```nofmt
name | replicas | activity | comment
------------+------------+------------------------------+---------
my_cluster | r1 (400cc) | reconfiguring size to 1600cc |
```

For detailed status, query
[`mz_internal.mz_cluster_reconfigurations`](/reference/system-catalog/mz_internal/#mz_cluster_reconfigurations),
which reports the target shape, the deadline, and the reconfiguration's
lifecycle `status` (`in-progress`, then a terminal `finalized`, `timed-out`,
`cancelled`, or `resource-exhausted`):

```mzsql
SELECT cluster_id, status, deadline, on_timeout, target, changes
FROM mz_internal.mz_cluster_reconfigurations;
```

For more information, see [`ALTER CLUSTER`: Resizing process](/sql/alter-cluster/#resizing-process).

### AWS Glue Schema Registry Support for Sinks {#v26.34-aws-glue-schema-registry-support-sinks}

{{< public-preview />}}
Expand Down
6 changes: 3 additions & 3 deletions doc/user/content/sql/alter-cluster.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -150,8 +150,8 @@ The values in the `mz_cluster_replica_sizes` table may change at any
time. You should not rely on them for any kind of capacity planning.
{{< /warning >}}

#### Downtime considerations for v26.34 or after
Starting in v26.34, ALTER CLUSTER <name> SET (SIZE = ...) by default resizes
#### Downtime considerations for v26.35 or after
Starting in v26.35, ALTER CLUSTER <name> SET (SIZE = ...) by default resizes
the cluster gracefully and without downtime. For example:

```mzsql
Expand Down Expand Up @@ -224,7 +224,7 @@ To **cancel** an in-flight resize, reissue `ALTER CLUSTER` with the cluster's
current size. Materialize drops the pending replicas and keeps the current
configuration.

#### Downtime considerations for v26.33 or before
#### Downtime considerations for v26.34 or before
{{< private-preview />}}

You can use the `WAIT UNTIL READY` option to perform a zero-downtime resizing,
Expand Down
4 changes: 2 additions & 2 deletions doc/user/content/sql/create-cluster.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -162,12 +162,12 @@ See also:
You can change the size of a cluster to respond to changes in your workload
using [`ALTER CLUSTER`](/sql/alter-cluster).

As of **v26.34**, resizing is graceful and incurs **no downtime**: Materialize
As of **v26.35**, resizing is graceful and incurs **no downtime**: Materialize
provisions new replicas at the target size, waits for them to hydrate, then
retires the old ones. See [Monitoring a
resize](/sql/alter-cluster/#monitoring-a-resize).

In versions before v26.34, resizing could incur downtime, and zero-downtime
In versions before v26.35, resizing could incur downtime, and zero-downtime
resizing required the `WAIT UNTIL READY` option.

See the reference documentation for [`ALTER
Expand Down
Loading