DOC-1008 Update upgrade.adoc - #969
Open
priyankagunaki-cloud wants to merge 2 commits into
Open
Conversation
victorleeTG
reviewed
Aug 13, 2026
| The right upgrade approach depends on your cluster's configuration and how much downtime it can tolerate. | ||
|
|
||
| * *Production clusters with a replica (recommended for production):* use xref:upgrade.adoc#_rolling_upgrade[Rolling Upgrade] to keep the cluster online during maintenance updates, with disruption limited to brief leader switch events. | ||
| * *Critical production clusters that require near-zero downtime and instant rollback:* consider a blue-green deployment strategy, where a second, upgraded cluster is stood up and validated against real workload before traffic is switched over. This is not a built-in TigerGraph feature -- it is a system architecture pattern that you design and operate using TigerGraph's replica and HA building blocks. |
Collaborator
There was a problem hiding this comment.
Suggested change
| * *Critical production clusters that require near-zero downtime and instant rollback:* consider a blue-green deployment strategy, where a second, upgraded cluster is stood up and validated against real workload before traffic is switched over. This is not a built-in TigerGraph feature -- it is a system architecture pattern that you design and operate using TigerGraph's replica and HA building blocks. | |
| * *Critical production clusters that require near-zero downtime and instant rollback:* consider a blue-green deployment strategy, where a second, upgraded cluster is stood up and validated against real workload before traffic is switched over. | |
| Talk to TigerGraph support if you have questions about designing and deploying a blue-green system. |
| == Rolling Upgrade (Preview) | ||
|
|
||
| A rolling upgrade allows you to upgrade your TigerGraph installation with minimal downtime by upgrading nodes in batches, ensuring that at least one full replica of the cluster is online throughout the process. | ||
| A rolling upgrade allows you to upgrade your TigerGraph installation with minimal service disruption by upgrading nodes in batches, ensuring that at least one full replica of the cluster remains online throughout the process. Under normal conditions, service interruptions are typically limited to leader switch events, which generally complete within a few seconds to approximately 1–2 minutes, depending on the cluster topology and upgrade strategy. If leaders are upgraded together, total disruption is roughly one leader switch; if upgraded one partition at a time, it scales with the number of partitions. |
Collaborator
There was a problem hiding this comment.
Suggested change
| A rolling upgrade allows you to upgrade your TigerGraph installation with minimal service disruption by upgrading nodes in batches, ensuring that at least one full replica of the cluster remains online throughout the process. Under normal conditions, service interruptions are typically limited to leader switch events, which generally complete within a few seconds to approximately 1–2 minutes, depending on the cluster topology and upgrade strategy. If leaders are upgraded together, total disruption is roughly one leader switch; if upgraded one partition at a time, it scales with the number of partitions. | |
| A rolling upgrade allows you to upgrade your TigerGraph installation with minimal service disruption by upgrading nodes in batches, ensuring that at least one full replica of the cluster remains online throughout the process. Under normal conditions, service interruptions are typically limited to leader switch events, which generally complete within a few seconds to approximately 1–2 minutes, depending on the cluster topology and upgrade strategy. | |
| If leaders are upgraded together, total disruption is roughly one leader switch; if upgrading one partition at a time, it scales with the number of partitions. |
@priyankagunaki-cloud
Question for TSE: how does the user configure whether upgrading leaders together or one partition at a time?
Contributor
Author
There was a problem hiding this comment.
Hello @deepkhajanchi
Could you please confirm on this?
Thanks.
cc : @Tushar-TG-14
| ==== | ||
| When switching to a new version of TigerGraph it will stop the current services which will make the cluster temporarily unavailable. | ||
|
|
||
| The upgrade runs through a sequence of pre-upgrade checks, a version switch, and post-upgrade checks across the infra, engine, GSQL, and GUS components (see xref:upgrade.adoc#_nn_option_2[n/N option] for the full script sequence). Of these, the GSQL steps typically take the longest, since they perform full catalog validation, including query syntax checks, query installation, and UDF compatibility checks to ensure the new version is compatible with your existing schema and queries. |
Collaborator
There was a problem hiding this comment.
Suggested change
| The upgrade runs through a sequence of pre-upgrade checks, a version switch, and post-upgrade checks across the infra, engine, GSQL, and GUS components (see xref:upgrade.adoc#_nn_option_2[n/N option] for the full script sequence). Of these, the GSQL steps typically take the longest, since they perform full catalog validation, including query syntax checks, query installation, and UDF compatibility checks to ensure the new version is compatible with your existing schema and queries. | |
| The upgrade runs through a sequence of pre-upgrade checks, a version switch, and post-upgrade checks across the infra, engine, GSQL, and GUS components. (See xref:upgrade.adoc#_nn_option_2[n/N option] for the full script sequence). Of these, the GSQL steps typically take the longest, since they perform full catalog validation, including query syntax checks, query installation, and UDF compatibility checks to ensure the new version is compatible with your existing schema and queries. |
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
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.
No description provided.