Upgrade to SingleStore 7.3

Important Notes About Upgrading

This topic describes how to upgrade SingleStore. Please read the following information thoroughly before upgrading.

Once the upgrade is complete, refer to the Post-Upgrade Considerations section for additional information on behavioral changes that you should be aware of.

Upgrade Duration and Behavior

Anticipate a longer upgrade time for each node. At the end of the upgrade process, anticipate a multi-minute delay while final checks are run that ensure the upgrade has completed successfully and the cluster is ready for operation. If you connect to the cluster while these post-upgrade checks are running, you will receive an error that the upgrade is still in progress.

Plancache

Plans in the plancache are dependent upon the specific SingleStore patch version, so when you upgrade to a new SingleStore version, all previously compiled plans will be invalidated. This means that any queries run against the upgraded cluster will force a one-time plan compilation, which results in slower query times the first time those queries are run. After the plans have been recompiled, they will be stored again in the plancache and query latency will return to nominal values.

Non-Sync Variables

By default, convert_nonunique_hash_to_skiplist is set to TRUE as of SingleStore 7.3. This means that any non-unique hash index will be recovered as a skiplist index, any newly created table will also have its non-unique hash indexes created as skiplists. For more information about this engine variable see the Non-Sync Variables List.

Verify Your Cluster is Ready for Upgrade

Warning

If upgrading from MemSQL 6.0 or earlier, you must first upgrade to MemSQL 6.8 before upgrading to SingleStore 7.3.

If upgrading from MemSQL version 6.8 or earlier, refer to Upgrading to MemSQL 7.0 for the increased disk space requirements for SingleStore.

If upgrading from MemSQL 6.x, there must not be any disaster recovery (DR) databases present before upgrading to SingleStore 7.3. If there are any DR databases in the cluster, the database must be dropped before upgrading, and re-replicated after the upgrade. If you choose to keep a DR database, you must stop replicating to it before the upgrade. Note that this DR database cannot be used for replication after the upgrade.

If upgrading from SingleStore 7.x with DR clusters, SingleStore recommends that you upgrade your DR secondary cluster(s) one at a time, and then upgrade your primary cluster last so that replication will continue to work after each upgrade.

Prior to upgrading your cluster, SingleStore recommends that you take a backup as a standard precautionary measure. See Back Up and Restore Data.

In addition, run the following SQL commands from the Master Aggregator to confirm that the following are true.

All leaf nodes ("leaves") are online.
SQL
```
SHOW LEAVES;
```
All aggregators are online.
SQL
```
SHOW AGGREGATORS;
```
There are no partitions with an Orphan role.
SQL
```
SHOW CLUSTER STATUS;
```
No rebalance or restore redundancy is necessary.
SQL
```
EXPLAIN REBALANCE PARTITIONS;
```
SQL
```
EXPLAIN RESTORE REDUNDANCY;
```

After you have backed up your data and verified your cluster is ready, you are ready to upgrade your cluster to the latest version of SingleStore using the SingleStore management tools.

Upgrade Your Cluster

Upgrade Versions and Methods

The tables below depicts which versions of SingleStore can be upgraded to SingleStore 7.3 and the method by which the cluster can be upgraded.

Offline upgrade: Your SingleStore cluster will be shut down and restarted over the course of the upgrade
Online upgrade: Your SingleStore cluster will not be shut down over the course of the upgrade

Upgrade via SingleStore Toolbox

Upgrade from	Offline upgrade	Online upgrade
7.0	✔	From 7.0.16 and later
6.8	✔	From 6.8.19 and later
6.7	✔	From 6.7.27 and later
6.5	✘	✘

Step 1: Upgrade SingleStore Toolbox

To upgrade to SingleStore 7.3, you must have Toolbox 1.5.3 or later installed prior to the SingleStore upgrade process. SingleStore recommends that you use the latest version of Toolbox when upgrading your cluster.

Run the install command to either install Toolbox if it is not already installed, or upgrade an existing version of Toolbox to the latest version of the package.

Red Hat

Shell

sudo yum install singlestoredb-toolbox -y

Debian

SingleStore packages are signed to ensure integrity, so the GPG key needs to be added to this host. When done, verify that the SingleStore signing key has been added using apt-key list.

Shell

wget -O - 'https://release.memsql.com/release-aug2018.gpg' 2>/dev/null | sudo apt-key add - && apt-key list

Without using apt-key:

Shell

wget -q -O - 'https://release.memsql.com/release-aug2018.gpg' | sudo tee /etc/apt/trusted.gpg.d/memsql.asc 1>/dev/null

Upgrade Toolbox.

Shell

sudo apt install singlestoredb-toolbox -y

Upgrade without Internet Access

If your cluster does not have internet access, use one of the following buttons to download either the latest RPM or Debian singlestoredb-toolbox package to a location accessible by your cluster:

singlestoredb-toolbox (.rpm)

singlestoredb-toolbox (.deb)

Then, run the install command for the installed package manager and specify the path to the package.

Red Hat

Shell

sudo yum install /path/to/singlestoredb-toolbox.rpm -y

Debian

Shell

sudo apt install /path/to/singlestoredb-toolbox.deb -y

Step 2: Upgrade SingleStore

The simplest and preferred upgrade option is an offline cluster upgrade. It is the least error-prone and easiest to perform; however, it requires downtime as all of the nodes in the cluster will be upgraded at the same time, shutting down the entire cluster for the duration of the upgrade.

If the cluster is running with High Availability, you also have the option to perform an incremental online cluster upgrade, which maintains cluster availability throughout the upgrade process. See the instructions in the online upgrade section for more details.

Select an option below to upgrade your cluster.

Option 1: Offline Upgrade

Note: Using this method to upgrade SingleStore is referred to as an offline upgrade as your SingleStore cluster will be shut down and restarted over the course of the upgrade. Do not shut down your cluster prior to starting the upgrade. If the cluster or individual nodes are offline when the upgrade is started, the upgrade will fail.

Run the following command to start an offline upgrade.

Confirm that the cluster can be upgraded. The cluster will not be upgraded when running this command.
Shell
```
sdb-deploy upgrade --precheck-only
```
Upgrade your cluster.

Note: sdb-deploy upgrade will perform a snapshot of all databases prior to upgrade.
Shell
```
sdb-deploy upgrade --version 7.3
```

If you do not specify a patch version, your cluster will be upgraded to the latest patch version of SingleStore 7.3.

During the upgrade process, you will be prompted to enable synchronous replication on your existing databases, or to leave those databases using the previous asynchronous replication behavior.

As of SingleStore 7.3, synchronous replication is enabled by default on all new databases. This provides an extra layer of resiliency in clusters with high availability enabled.

Note: You cannot downgrade from your current version.

If your cluster does not have internet access, use one of the following buttons to download either the latest RPM or Debian singlestoredb-server package to a location accessible by your cluster:

singlestoredb-server (.rpm)

singlestoredb-server (.deb)

The singlestoredb-server package contains both the SingleStore binary and the low-level management tool, memsqlctl.

Run the sdb-deploy upgrade command and reference the appropriate package in the --file-path option. Running upgrade (as opposed to simply upgrading the package via the package manager) will perform an offline restart of all the nodes to make sure the cluster is using the new version.

Red Hat

Shell

sdb-deploy upgrade --file-path /path/to/singlestoredb-server.rpm

Debian

Shell

sdb-deploy upgrade --file-path /path/to/singlestoredb-server.deb

Refer to sdb-deploy upgrade for more information.

Once the upgrade is complete, refer to the Post-Upgrade Considerations section for any changes between versions that may impact your cluster.

Option 2: Online Upgrade

This upgrade method is referred to as an online upgrade as your SingleStore cluster will not be shut down over the course of the upgrade. Nodes will be restarted in a specific sequence to ensure that DML-based workloads will still function. Do not shut down your cluster prior to starting the upgrade. If the cluster or individual nodes are offline when the upgrade is started, the upgrade will fail.

Note

An online upgrade may fail if a long-running workload that writes to the database, or a workload that manipulates SingleStore files (such as an automated backup or maintenance script), is running on the target cluster. SingleStore recommends performing an online upgrade only after these workloads have completed.

Toolbox 1.11.7 and later provide the option to retry a failed online upgrade. Should the online upgrade ultimately fail, an offline upgrade will be attempted. Note that the cluster will be shut down and restarted over the course of an offline upgrade.

Run the following command to start an online upgrade.

Confirm that the cluster can be upgraded. The cluster will not be upgraded when running this command.
Shell
```
sdb-deploy upgrade --precheck-only
```
Upgrade your cluster.

Note: sdb-deploy upgrade will perform a snapshot of all databases prior to upgrade.
Shell
```
sdb-deploy upgrade --online --version 7.3
```

By specifying --version, your cluster will be upgraded to the latest patch version of SingleStore 7.3.

During the upgrade process, you will be prompted to enable synchronous replication on your existing databases. While asynchronous replication can still be chosen, the data replication mechanism as of SingleStore 7.0 has been enhanced to the point where synchronous replication is now the recommended option.

Note: You cannot downgrade from your current version.

If your cluster does not have internet access, use one of the following buttons to download either the latest RPM or Debian singlestoredb-server package to a location accessible by your cluster:

singlestoredb-server (.rpm)

singlestoredb-server (.deb)

The singlestoredb-server package contains both the SingleStore binary and the low-level management tool, memsqlctl.

Run the sdb-deploy upgrade --online command and reference the appropriate package in the --file-path option. Running upgrade (as opposed to simply upgrading the package via the package manager) will perform an offline restart of all the nodes to make sure the cluster is using the new version.

Red Hat

Shell

sdb-deploy upgrade --online --file-path /path/to/singlestoredb-server.rpm

Debian

Shell

sdb-deploy upgrade --online --file-path /path/to/singlestoredb-server.deb

Refer to sdb-deploy upgrade for more information.

Once the upgrade is complete, refer to the Post-Upgrade Considerations section for any changes between versions that may impact your cluster.

Confirm that the Upgrade Succeeded

Toolbox displays the progress of the upgrade and reports whether the upgrade succeeded. While typically not required, you may also perform an in-depth review of the post-upgrade cluster to reaffirm that the upgrade succeeded.

Confirm that all nodes are online and healthy.

The State column should display online for each node.

Shell

sdb-admin show-cluster

✓ Successfully ran 'memsqlctl show-cluster'
+---------------------+-----------+------+--------------------+-----------+-----------+--------+--------------------+------------------------------+--------+-------------------+
|        Role         |   Host    | Port | Availability Group | Pair Host | Pair Port | State  | Opened Connections | Average Roundtrip Latency ms | NodeId | Master Aggregator |
+---------------------+-----------+------+--------------------+-----------+-----------+--------+--------------------+------------------------------+--------+-------------------+
| Leaf                | 127.0.0.1 | 3307 | 1                  | null      | null      | online | 2                  |                              | 2      |                   |
| Aggregator (Leader) | 127.0.0.1 | 3306 |                    | null      | null      | online | 0                  | null                         | 1      | Yes               |
+---------------------+-----------+------+--------------------+-----------+-----------+--------+--------------------+------------------------------+--------+-------------------+

Confirm that all databases are healthy.

The summary column should display healthy for each database.

Shell

sudo memsqlctl query --sql "SELECT * FROM information_schema.MV_DISTRIBUTED_DATABASES_STATUS;"

+---------------+----------------+--------------------+---------+--------+-------------+------------+---------+------------+---------------+---------+---------------+
| database_name | num_partitions | num_sub_partitions | summary | online | replicating | recovering | pending | transition | unrecoverable | offline | sync_mismatch |
+---------------+----------------+--------------------+---------+--------+-------------+------------+---------+------------+---------------+---------+---------------+
| test          | 16             | 64                 | healthy | 16     | 16          | 0          | 0       | 0          | 0             | 0       | 0             |
+---------------+----------------+--------------------+---------+--------+-------------+------------+---------+------------+---------------+---------+---------------+

Confirm that all nodes reflect the version specified in the sdb-deploy upgrade command.

The Version column displays the version that each node is running.

Shell

sdb-admin list-nodes

+------------+--------+-----------+------+---------------+--------------+---------+----------------+--------------------+--------------+
| MemSQL ID  |  Role  |   Host    | Port | Process State | Connectable? | Version | Recovery State | Availability Group | Bind Address |
+------------+--------+-----------+------+---------------+--------------+---------+----------------+--------------------+--------------+
| CBDC2807B7 | Master | 127.0.0.1 | 3306 | Running       | True         | 8.7.11  | Online         |                    | 127.0.0.1    |
| EC33CC5A08 | Leaf   | 127.0.0.1 | 3307 | Running       | True         | 8.7.11  | Online         | 1                  | 127.0.0.1    |
+------------+--------+-----------+------+---------------+--------------+---------+----------------+--------------------+--------------+

Roll Back from a Failed Upgrade

Currently, SingleStore does not support downgrading directly. Use the following steps to roll back to an earlier version of SingleStore using the backup made at the beginning of this upgrade guide.

Note that a backup created from a given version of the SingleStore engine can only be restored to the same engine version or later.

Make a backup of the cluster configuration.
Shell
```
sdb-deploy generate-cluster-file
```
Delete all of the nodes in the cluster.
Shell
```
sdb-admin delete-node --stop --all
```
Use the following command to roll back to an earlier version of the SingleStore engine by removing the engine version(s) you do not want.

For example, if upgrading to SingleStore 7.3 fails, remove 7.3.
Shell
```
sdb-deploy uninstall --version 7.3
```
Unregister all hosts in the cluster.
Shell
```
sdb-toolbox-config unregister-host --all
```
Recreate the cluster using the cluster configuration captured in the cluster file. Note that the cluster file may contain the engine version, so be sure to update the cluster file with the engine version you wish to restore.
Shell
```
sdb-deploy setup-cluster --cluster-file /path/to/cluster/file
```
Restore the cluster's data from the backup that was made earlier. Refer to Back Up and Restore Data for more information.

Post-Upgrade Considerations

When upgrading to SingleStore 7.3, you should be aware of the following changes to system behavior or default configuration settings. The behavior of a cluster upgraded from an earlier version to SingleStore 7.3 may differ compared to a newly installed cluster on SingleStore 7.3 as described below. Most of the changes fall into two categories:

In some versions, the default value for a configuration variable was changed compared to previous versions, but clusters upgraded from earlier versions retain their previous setting, both if it was set to a specific value or if it was not explicitly set and hence using the previous default. In some of these cases, SingleStore recommends to update your configuration to the new default if you were previously using the old default, after appropriate testing.
Some new features are automatically enabled by default on newly installed SingleStore 7.3 clusters but not automatically enabled on clusters upgraded from an earlier version to 7.3. In some of these cases, SingleStore recommends to enable the new features, after appropriate testing.

Upgrades to 7.3

To reduce your total cost of ownership (TCO), you may be able store data in Universal Storage instead of rowstores. This is because rowstores store their data in RAM, which can be costly. Universal Storage now supports upserts, which were previously only supported in rowstores.
You may want to run the command REBALANCE ALL DATABASES. This command rebalances each database in the cluster, in alphabetical order of the database name. When a rebalance runs on a database d, it first considers the placement of the partitions of the other databases in the cluster before rebalancing the partitions of d.
You may want to set the cardinality_estimation_level engine variable to '7.3'. This setting uses sampling and histograms together (when both are available) to improve selectivity estimation. The default setting is '7.1'.
Changing the value of the data_conversion_compatibility_level engine variable can change the behavior of expressions in computed columns. Refer to the Data Type Conversion section of Data Types for more information.
sp_query_dynamic_param should be turned off if an application breaks post-upgrade due to a change in type conversion behavior. See the Example: Changes in Type Conversion Behavior for more information.
Upgrading the cluster, with json_extract_string_collation set to auto (default setting), changes the collation settings for JSON_EXTRACT_STRING from json to server. Refer to In-Depth Variable Definitions for information on json_extract_string_collation settings.

Upgrades from 6.8 and Earlier to 7.0 and Later

Synchronous Replication On by Default

In previous versions of SingleStore, in clusters with high availability enabled, replication between primary partitions and replica partitions happened asynchronously. Starting with 7.0, synchronous replication is enabled by default for all new databases. And as noted in the upgrade section of this topic, you have the option to opt-out of synchronous replication for the existing databases in your cluster. For more information on synchronous replication, see Replication and Durability and CREATE DATABASE.

Security Change for Resource Pools

Between MemSQL 6.5 to 6.8, all users were able to access all resource pools. Access had to be controlled externally from the database, such as in a client application. Starting in 7.0, users can only access resource pools that they have explicit permission to access when sync_permissions is enabled. Otherwise, no permission checking is done for any user for any resource pool. Refer to Synchronizing Permissions Across Your Cluster for more information.

To ensure current users will be able to access pools immediately after upgrading to 7.3, all existing users will be granted USAGE permissions to all existing and future resource pools if sync_permissions was enabled prior to upgrade (i.e. for each user GRANT USAGE ON RESOURCE POOL '*' TO <user>@<host> is run internally on upgrade to 7.0 or later) unless REVOKE USAGE ON RESOURCE POOL '*' FROM <user>@<host> is run. You will then have to explicitly grant USAGE permissions to specific resource pools for those users and any other new users created. Refer to Set Resource Limits for more information.

Many Existing Engine Variables are Now Sync Variables

The following engine variables from 6.8 are now Sync Variables, which means you set the value on the Master Aggregator and the change is propagated across your cluster. You no longer have to set and manage these variables on each node in the cluster.

Global variables

auditlog_disk_sync
columnstore_disk_insert_threshold
columnstore_flush_bytes
columnstore_ingest_management_queue_timeout
columnstore_segment_rows
disk_plan_expiration_minutes
enable_columnstore_ingest_management
enable_disk_plan_expiration
explain_expression_limit
forward_aggregator_plan_hash
geo_query_info
geo_sphere_radius
internal_columnstore_window_minimum_blob_size
load_data_internal_compression
load_data_max_buffer_size
load_data_read_size
load_data_write_size
materialize_ctes
max_connect_errors
max_prepared_stmt_count
multi_insert_tuple_count
pipelines_batches_metadata_to_keep
pipelines_extractor_debug_logging
pipelines_kafka_version
pipelines_max_concurrent
pipelines_max_concurrent_batch_partitions
pipelines_max_errors_per_partition
pipelines_stderr_bufsize
plan_expiration_minutes
read_advanced_counters
replication_timeout_ms
snapshot_trigger_size
sync2_timeout
synchronize_database_timeout

Session Variables

character_set_server
collation_connection
collation_database
collation_server
enable_binary_protocol
enable_broadcast_left_join
enable_local_shuffle_group_by
enable_multipartition_queries
enable_skiplist_sampling_for_selectivity
explain_joinplan_costs
ignore_insert_into_computed_column
inlist_precision_limit
leaf_pushdown_default
leaf_pushdown_enable_rowcount
lock_wait_timeout
max_broadcast_tree_rowcount
max_subselect_aggregator_rowcount
optimize_constants
optimize_expressions_larger_than
optimize_huge_expressions
optimize_stmt_threshold
optimizer_warnings
report_mpl_optimizations
reshuffle_group_by_base_cost
sampling_estimates_for_complex_filters
sql_select_limit
statistics_warnings

See the List of Engine Variables for more information on these variables.

On this page

Important Notes About Upgrading

Upgrade Duration and Behavior

Plancache

Non-Sync Variables

Verify Your Cluster is Ready for Upgrade

Upgrade Your Cluster

Upgrade Versions and Methods

Upgrade via SingleStore Toolbox

Step 1: Upgrade SingleStore Toolbox

Upgrade without Internet Access

Step 2: Upgrade SingleStore

Option 1: Offline Upgrade

Option 2: Online Upgrade

Confirm that the Upgrade Succeeded

Roll Back from a Failed Upgrade

Post-Upgrade Considerations

Upgrades to 7.3

Upgrades from 6.8 and Earlier to 7.0 and Later

Synchronous Replication On by Default

Security Change for Resource Pools

Many Existing Engine Variables are Now Sync Variables

Was this article helpful?

On this page

Was this article helpful?