Skip to content

Update for free service restarts #4591

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
atovpeko merged 5 commits into from
Dec 4, 2025
Merged

Update for free service restarts #4591

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
0069014
update for free service restarts
atovpeko Nov 24, 2025
8cb0b2c
Merge branch 'latest' into 518-docs-rfc-update-maintenance-and-upgrad…
billy-the-fish Nov 27, 2025
b401484
Merge branch 'latest' into 518-docs-rfc-update-maintenance-and-upgrad…
atovpeko Nov 27, 2025
feb99d7
Update use-timescale/upgrades.md
atovpeko Dec 4, 2025
18ec395
Merge branch 'latest' into 518-docs-rfc-update-maintenance-and-upgrad…
atovpeko Dec 4, 2025
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
4 changes: 3 additions & 1 deletion use-timescale/upgrades.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ After a maintenance upgrade, the DNS name remains the same. However, the IP addr
## Minor software upgrades

If you do not [manually upgrade $TIMESCALE_DB][minor-manual-upgrade] for non-critical upgrades,
$CLOUD_LONG performs upgrades automatically in the next available maintenance window. The upgrade is first applied to your $SERVICE_SHORTs tagged `#dev`, and three weeks later to those tagged `#prod`. [Subscribe][subscribe] to get an email notification before your `#prod` $SERVICE_SHORTs are upgraded. You can upgrade your `#prod` $SERVICE_SHORTs manually sooner, if needed. See [Service management][service-management] for how to manage $SERVICE_SHORT tags.
$CLOUD_LONG performs upgrades automatically in the next available maintenance window. The upgrade is first applied to your standard $SERVICE_SHORTs tagged `#dev`, and three weeks later to those tagged `#prod`. [Subscribe][subscribe] to get an email notification before your `#prod` $SERVICE_SHORTs are upgraded. You can upgrade your `#prod` $SERVICE_SHORTs manually sooner, if needed. See [Service management][service-management] for how to manage $SERVICE_SHORT tags.

Most upgrades that occur during your maintenance windows do not require any downtime. This means that there is no
$SERVICE_SHORT outage during the upgrade. However, all connections and transactions in progress during the upgrade are
Expand All @@ -51,6 +51,8 @@ able to do so. Best practice is to [schedule your maintenance window][define-mai
disrupts your workloads as little as possible and [minimize downtime with replicas][minimize-downtime]. If there are no
pending upgrades available during a regular maintenance window, no changes are performed.

Free $SERVICE_SHORTs are upgraded and restarted during the maintenance window each week, if there is a new version available. Some background maintenance tasks performed at other times can also cause connection resets. When a connection reset occurs, you can immediately reconnect to your $SERVICE_SHORTs.

To track the status of maintenance events, see the $CLOUD_LONG [status page][status-page].

### Minimize downtime with replicas
Expand Down