SingleStore Toolbox Release Notes
On this page
2025-08-28 Version 1. 18. 5
-
Upgraded the Golang compiler, which is used to build the
sdb-admin,sdb-deploy,sdb-report, andsdb-toolbox-configToolbox binaries, to version 1.24. 6 -
Deprecated the
sdb-deploy cluster-in-a-boxcommand in favor of the SingleStore Dev Image -
Updated the following commands to allow a "Version 2" license to be set for clusters running SingleStore 8.
5 versions 8. 5. 42 and later and SingleStore 8. 7 versions 8. 7. 28 and later -
sdb-deploy setup-cluster -
sdb-admin create-node -
sdb-admin bootstrap-aggregator -
sdb-admin set-license
-
-
Added a
dpkgcollector to thesdb-report collectcommand to capture the output from thedpkg -lcommand on each host -
Added an
rpmcollector to thesdb-report collectcommand to capture the output from therpm -qacommand on each host -
Added the
--host,--port,--user,--password,--ssland--ssl-caoptions to thesdb-admin dumpcommand for querying a node directly -
Fixed a bug where the
sdb-admin upgrade –preinstalled-path …command would fail when a cluster’s hosts were configured with a non-US locale
2025-07-28 Version 1. 18. 4
-
Upgraded the Golang compiler, which is used to build the
sdb-admin,sdb-deploy,sdb-report, andsdb-toolbox-configToolbox binaries, to version 1.24. 4 -
Fixed an issue in the
sdb-adminandsdb-deploycommands where free licenses could not be set for SingleStore versions earlier than 8.9. 5
2025-06-13 Version 1. 18. 3
-
Updated the
memsqlTracelogscollector to collect JLucene logs with thesdb-report collect,sdb-report collect-local, andsdb-report collect-kubecommands -
Updated the
sdb-admin start-monitoringandsdb-admin start-monitoring-kubecommands to add adetailscolumn to the event tracing metrics table -
Updated the
sdb-deploy upgradecommand to collect a cluster report before performing an upgrade-
Added a
--report-pathoption to specify a custom path for the report -
Added a
--skip-reportflag to skip collecting the report
-
2025-05-05 Version 1. 18. 2
-
Added the
--multipart-chunk-size-mboption to thesdb-admin create-backupandsdb-admin restore-backupcommands to specify a multipart-chunk-size-mb configuration for S3-compatible backup repositories -
Upgraded the Golang compiler, which is used to build the
sdb-admin,sdb-deploy,sdb-report, andsdb-toolbox-configToolbox binaries, to version 1.24. 2 -
Updated the
sdb-deploy upgradecommand to allow online upgrades for clusters where the consensus_enabled engine variable is set to ON
2025-04-08 Version 1. 18. 1
-
Added the
--roleoption to thesdb-admin add-aggregatorcommand to set the aggregator role to either "voting member" or "follower" when adding a new aggregator -
Added the
--aggregator-roleoption to thesdb-admin create-nodecommand to set the aggregator role to either "voting member" or "follower" when adding a new node -
Fixed a bug in the
sdb-deploy upgradecommand where offline upgrades would fail with errors for clusters where theconsensus_engine variable was set toenabled ON -
Updated the
sdb-deploy upgradecommand to block online upgrades for clusters where theconsensus_engine variable is set toenabled ON
2025-03-20 Version 1. 18. 0
-
Updated the following commands to display an error message if a user attempts to apply a license that is not applicable to earlier versions of SingleStore:
-
sdb-deploy setup-cluster -
sdb-deploy cluster-in-a-box -
sdb-admin create-node -
sdb-admin bootstrap-aggregator -
sdb-admin set-license
-
-
Added an
informationSchemaConnectionAttributescollector to thesdb-report collectcommand to capture attributes about client connections -
Added an
informationSchemaRolePrivilegescollector to thesdb-report collectcommand to captureinformation_table content on an aggregator nodeschema. ROLE_ PRIVILEGES -
Added an
informationSchemaUserscollector to thesdb-report collectcommand to captureinformation_table content on each nodeschema. USERS -
Added an
lsblkAllJsoncollector to thesdb-report collectcommand to save the output of thelsblk -O -Jcommand for each host -
Added a
showUserscollector to thesdb-report collectcommand to captureSHOW USERSquery results on an aggregator node -
Added an
sslFilesAndDatadirPermissionscollector to thesdb-report collectcommand to save the permissions of the SSL certificates, keys files, anddatadirfor each node -
Added the following checkers to ensure that the cluster setup follows SingleStore security recommendations:
sdbHCAdvancedHDFSPipelineFeaturessdbHCNetworkAccesssdbHCAesDefaultEncryptionModesdbHCPasswordPolicysdbHCAuditlogDiskSyncsdbHCReplicationTlsOnlysdbHCAuditlogLevelsdbHCResourceLimitssdbHCAuditlogRetentionPeriodsdbHCReviewTlsConfigsdbHCAuditlogsDirsdbHCRoleBasedAccessControlsdbHCBindAddresssdbHCRootPasswordsdbHCDedicatedAdminConnectionssdbHCRowLevelSecuritysdbHCDefaultPortsdbHCSecureFilePrivsdbHCDefaultUserRequireSSLsdbHCServiceAccountsdbHCEnableWASMsdbHCSslFilesAndDatadirPermissionssdbHCEncryptedBlockDevicesdbHCSyncPermissionssdbHCEngineVersionsdbHCTlsCertKeysdbHCFailedLoginAttemptLockoutPolicysdbHCTlsFipsModesdbHChttpAPIsdbHCUnnecessaryDefaultUserssdbHCLicenseVisibilitysdbHCUserAuthentication -
Added a
--security-recommendationsflag to thesdb-report collect,sdb-report check,andsdb-report collect-and-checkcommands to collect only security-related configuration data and to run only those checkers that ensure that the cluster follows SingleStore security recommendations -
Added a
maxNicePrioritychecker to thesdb-report checkcommand to ensure that “Maxnicepriority” is set above the recommended threshold for allmemsqldprocesses -
Updated the
memsqlTracelogscollector to capture websocket_proxy logs -
Upgraded the Golang compiler, which is used to build the
sdb-admin,sdb-deploy,sdb-report, andsdb-toolbox-configToolbox binaries, to version 1.23. 6
2025-02-04 Version 1. 17. 19
-
Fixed an issue where the
sdb-deploy uicommand did not display the most recent SingleStore server versions -
Fixed a bug where Toolbox commands did not retry a snapshot for databases in a recovery state
2024-11-05 Version 1. 17. 18
-
Upgraded the Golang compiler, which is used to build the
sdb-admin,sdb-deploy,sdb-report, andsdb-toolbox-configToolbox binaries, to version 1.23. 2 -
Added the
--bind-to-l3flag to thesdb-admin optimizecommand which allows leaf nodes to bind to L3 cache indices for optimized performance
2024-10-03 Version 1. 17. 17
-
Added an
informationSchemaMvRecoveryStatuscollector to thesdb-report collectcommand to capture data from theinformation_tableschema. MV_ RECOVERY_ STATUS -
Updated the
sdb-admin sync-ldapcommand to allow a unique set of parameters to be specified for users that are synced from specific LDAP groups
2024-09-12 Version 1. 17. 16
-
Changed the pre-upgrade checks in the
sdb-deploy upgradecommand to allow an upgrade to be performed when a rebalance is pending.Instead of blocking the upgrade, a warning is now displayed. -
Upgraded the Golang compiler, which is used to build the
sdb-admin,sdb-deploy,sdb-report, andsdb-toolbox-configToolbox binaries, to version 1.21. 13
2024-08-20 Version 1. 17. 15
-
Enhanced the warning message in the
versionHashchecker when Toolbox cannot connect to the SingleStore server -
Added the
--temp-diroption to thesdb-report checkcommand to specify a custom temporary folder for report checks
2024-07-10 Version 1. 17. 14
-
Added the
informationSchemaMvVersionHistorycollector to thesdb-report collectcommand to capture data from theinformation_andschema. MV_ VERSION_ HISTORY information_tablesschema. MV_ VERSION_ HISTORY_ EXTENDED -
Fixed a bug where the
sdb-admin dumpcommand would fail if an object’s name contained a backtick -
Updated the
sdb-report collect,sdb-report collect-local, andsdb-report collect-kubecommands to record the collection time for each collector on each host
2024-06-26 Version 1. 17. 13
-
Added a pre-install check to the
sdb-deploy upgrade --precheck-onlycommand to ensure that all hosts havetar-install-dirdefined when upgrading SingleStore from a tarball -
Added the
informationSchemaMvGlobalStatuscollector to thesdb-report collectcommand to capture data from theinformation_tableschema. MV_ GLOBAL_ STATUS -
Added the
informationSchemaMvProcesslistcollector to thesdb-report collectcommand to capture data from theinformation_tableschema. MV_ PROCESSLIST -
Updated the
sdb-admin start-monitoringcommand to create additional columns in theact_table within the monitoring databasesamples
2024-06-05 Version 1. 17. 12
-
Prevents the
sdb-deploy upgradecommand from directly upgrading SingleStore 7.3 and earlier to SingleStore 8. 7 and later -
Fixed a bug where monitoring would generate an out-of-range value for the
batch_column for monitoring metrics pipelinesid
2024-05-10 Version 1. 17. 11
-
Fixed a bug where the
sdb-report collectcommand would hang when run with the--opt memsqlTracelogs.optiontracelogStartTimestamp -
Enhanced the
sdb-admin dumpcommand to includeALTER PIPELINEstatements in the dump file -
Improved reporting on orphan partitions on a leaf node with the addition of an
OrphansDetectedrecovery state in the output of thesdb-admin list-nodescommand -
Added an
informationSchemaMvBackupStatuscollector to thesdb-report collectcommand which captures content from theinformation_tableschema. MV_ BACKUP_ STATUS -
Fixed layout issues in the output of the
sdb-report collect --helpcommand
2024-04-15 Version 1. 17. 10
-
Upgraded the Golang compiler, which is used to build the
sdb-admin,sdb-deploy,sdb-report, andsdb-toolbox-configToolbox binaries, to version 1.21. 5 -
Updated Toolbox command help messages
-
Fixed a bug where the
sdb-reporttool would report false-positive errors from thetraceloghardShutdownreport checker -
Fixed inconsistencies in the output of the
sdb-admin list-backupscommand between JSON and plaintext formats
2024-02-29 Version 1. 17. 9
-
Enhanced the
sdb-admin dumpcommand to include the output from theQUERY_parameter for resource poolsMEMORY_ PERCENTAGE -
Added a
--containeroption to thesdb-admin start-monitoring-kubecommand to specify the container in which to run the command -
Refactored the
informationSchemaMvBottomlesscollector to exclude retrieving data from theinformation_tableschema. MV_ BOTTOMLESS_ REMOTE_ STATS -
Added the
informationSchemaMvBottomlessRemoteStatscollector to both thesdb-report collectandsdb-report collect-kubecommands to save data from theinformation_tableschema. MV_ BOTTOMLESS_ REMOTE_ STATS
2024-01-25 Version 1. 17. 8
-
Fixed a bug in the
sdb-deploy upgrade --upgrade-to-latest-minorcommand where the specified version was not installed on some hosts -
Renamed the
--upgrade-to-latest-minorflag to--upgrade-to-latest-patchfor thesdb-deploy upgradecommand
2024-01-24 Version 1. 17. 7
-
Added an
--upgrade-to-latest-minorflag to thesdb-deploy upgradecommand to allow upgrading a cluster to the latest minor (patch) release of the current major release -
Updated the
sdb-admin dumpcommand to displayCREATE USERSQL statements -
Added a
--tmp-diroption to thesdb-deploy install,sdb-deploy upgrade,sdb-deploy setup-cluster, andsdb-deploy cluster-in-a-boxcommands to specify a directory for temporary files on local and remote hosts -
Enhanced the
sdb-report collectcommand to display a more detailed error message when no hosts are registered
2023-11-22 Version 1. 17. 6
-
Added a
--collect-event-tracesflag to thesdb-admin start-monitoringandsdb-admin start-monitoring-kubecommands to allow event traces to be collected from the exporter’s/event-tracesendpoint -
Updated the
sdb-admincommand to provide more detailed information when a host is not found by name -
Added a
databaseDiskUsagecollector to thesdb-report collectcommand that captures disk usage per database -
Updated the
sdb-admin sync-ldapcommand to infer the database root user’s password from an environment variable -
Added a confirmation message to allow the
sdb-report calibrate-blob-storagecommand to change the value ofmaximum_blob_ cache_ size_ mb -
Updated the
sdb-admin sync-ldapcommand to accept a multi-line value for the--query-filteroption
2023-10-23 Version 1. 17. 5
-
Fixed an issue that would cause the
sdb-admin sync-ldapcommand to fail due to insufficientGRANTpermissions for SingleStore users. -
Enhanced the
sdb-admin sync-ldapcommand by adding support for multi-line filter parameters in the configuration YAML file.This enhancement provides additional flexibility when configuring LDAP synchronization.
2023-10-06 Version 1. 17. 4
-
Upgraded the Golang compiler, which is used to build the
sdb-admin,sdb-deploy,sdb-report, andsdb-toolbox-configToolbox binaries, to version 1.21. 1 -
Updated Toolbox command help messages to clarify how to specify multiple values for those flags that can accept them
2023-09-08 Version 1. 17. 3
-
Introduced a
--no-regionflag for multiplesdb-admincommands, includingcreate-backup,delete-backup,validate-backup,summarize-backups, andlist-backups.This flag enables operations without the need to specify a region for S3-compatible paths. -
Added a
studioFilescollector to thesdb-report collectcommand which captures SingleStore Studio configuration and state files -
Enhanced the
sdb-admin sync-ldapcommand with--hostand--portoptions which enable a direct connection to a specific SingleStore node -
Introduced an
--sslflag to thesdb-admin queryandsdb-admin sync-ldapcommands which enforces an SSL connection between Toolbox and a SingleStore node -
Added an
--ssl-caoption to thesdb-admin queryandsdb-admin sync-ldapcommands which allows a custom certificate to be specified for SSL connections -
Optimized memory usage in the
sdb-report collectcommand when used with thetracelogStartTimestampargument -
Resolved an issue where the
sdb-admin create-backupcommand would fail when attempting to perform backups to an NFS folder -
Fixed a bug in the
sdb-report checkcommand where not all issues detected by thenumaConfigurationchecker were reported
2023-08-03 Version 1. 17. 2
-
Added
ssl-caandssl-capathoptions to thesdb-admin start-monitoring-kubecommand to enable HTTPS connections to the monitoring exporter -
Updated the
sdb-report calibratecommand to preserve the original value of theread_configuration after executionadvanced_ counters -
Fixed an issue where the
sdb-report collect-kubecommand would not collect the Operator logs
2023-07-24 Version 1. 17. 1
-
Fixed an issue where the
sdb-admin sync-ldapcommand was unable to match a user to a group due to uppercase and lowercase differences in the attributes -
Updated the
sdb-deploy upgrade,sdb-deploy setup-cluster, andsdb-toolbox-config register-hostcommands to ensure that CA certificates are uniformly located on all cluster hosts -
Updated the
sdb-report checkcommand to issue a warning instead of a failure when detecting inconsistencies in themax_settingsmemory
2023-07-14 Version 1. 17. 0
-
Upgraded the Golang compiler, which is used to build the
sdb-admin,sdb-deploy,sdb-report, andsdb-toolbox-configToolbox binaries, to version 1.20. 5 -
Updated the
sdb-adminandsdb-deploycommands to include aLimitNICE=-10parameter in thememsql.file when SingleStore is deployed via tarballservice
2023-06-15 Version 1. 16. 1
-
Updated the
sdb-admin sync-ldapcommand to allow multiple LDAP services to be specified in the configuration YAML file -
Added an
insecure_option to the configuration YAML file that allows theskip_ verify sdb-report send-alertcommand to skip TLS certificate validation -
Updated the
sdb-report collectcommand to save global variables in theshowVariablescollector report -
Renamed the
sdb-admin update-node-basedircommand tosdb-admin update-node-base-install-dirto more accurately reflect this command’s function -
Updated the
sdb-report checkcommand to log hard shutdown events produced by SingleStore versions 8.1 and later
2023-05-08 Version 1. 16. 0
-
Updated the
sdb-deploy upgradecommand to validate SSL certificates prior to upgrading to SingleStore version 8.1 and later -
Updated the
sdb-report checkcommand to report a failure if theMalloc_variable (from SHOW STATUS EXTENDED) exceeds 10 GBactive_ memory -
Refined the error messages should the
sdb-admin add-leafcommand fail -
Added the
--tagoption to thesdb-admin create-backupcommand that allows tags to be assigned to newly created backups -
Added the
--set-configsoption to thesdb-admin create-nodecommand that allows node variable values to be set before a new node is started -
Added the
--set-configsoption to thesdb-deploy upgradecommand that allows node variable values to be set before an upgraded node is started -
Updated the
sdb-report collectcommand to obscure user credentials in the pipeline collector's output -
Updated the
sdb-report collectcommand to include information in the final report about hosts that failed to collect reports -
Updated the
sdb-report collectcommand to run thetoolboxConfigcollector only on the host where thesdb-reportcommand is located -
Updated the
sdb-report collectcommand to incorporate all pipeline metadata tables in the cluster report
2023-04-11 Version 1. 15. 3
-
Updated the
sdb-deploy upgradecommand to automatically undo an offline upgrade to the specified SingleStore version if it cannot be managed by the current Toolbox version -
Updated the
sdb-deploy upgradecommand to retry the "rebalance partitions" upgrade step in the event of a failure -
Added a
--containeroption to thesdb-report collect-kubecommand to specify the container in which to run the report -
Added a new
informationSchemaDistributedDatabasesOnSitescollector to thesdb-reportcommands which collects the contents of theinformation_table on an aggregator nodeschema. distributed_ databases_ on_ sites -
Added a new
informationSchemaInternalTableStatisticscollector to thesdb-reportcommands which collects the contents of theinformation_table on an aggregator nodeschema. internal_ table_ statistics -
Updated the
sdb-report checkcommand to report a warning when thevm.value is greater thanswappiness 10on a host
2023-02-28 Version 1. 15. 2
-
Fixed a bug where the
sdb-report calibratecommand would fail with SingleStore versions 8.0 or later -
Added an
--exclude-ldap-users-to-loweroption to thesdb-admin sync-ldapcommand to exclude LDAP usernames from syncing to lowercase database usernames
2023-02-09 Version 1. 15. 1
-
Added an
exclude_field to the configuration YAML file to exclude the specified LDAP users from syncing with theusers sdb-admin sync-ldap --config-filecommand -
Added
--exclude-ldap-usersand--exclude-ldap-users-fileoptions to thesdb-admin sync-ldapcommand to exclude LDAP users from syncing -
Added an
--ldap-users-to-loweroption to thesdb-admin sync-ldapcommand to sync LDAP usernames to lowercase SQL usernames
2023-01-30 Version 1. 15. 0
-
Fixed a bug where the
sdb-admin configure-monitoringcommand incorrectly detected when a user did not have the permissions required to start the exporter -
Fixed a bug where the
sdb-admin summarize-backupscommand swapped the “Oldest backup” and “Newest backup” column headers -
All engine variables can now be set in the cluster configuration YAML file and used by the
sdb-deploy setup-clustercommand -
Updated the
sdb-admin update-configcommand to prevent theresource_engine variable from being changedpool -
Fixed a bug when the
sdb-deploy uicommand reported an error -
Updated the
sdb-admin show-aggregatorsandsdb-admin show-clustercommands to show theRolefield for aggregator nodes -
Added a
--roleoption to thesdb-admin add-aggregatorcommand to create an aggregator node as a voting member -
Added an
--aggregator-roleoption to thesdb-admin create-nodecommand to create an aggregator node as a voting member -
Updated the
sdb-admin describe-nodecommand to display an aggregator node’s role -
Added an
aggregator_field to the cluster configuration YAML file to allow therole sdb-deploy setup-clustercommand to set up a cluster with aggregator nodes as voting members
2022-12-14 Version 1. 14. 4
-
Added an
--allow-ipv6option to thesdb-admin create-nodecommand to allow a newly-created node to use IPv6 -
Added an
--allow-ipv6option to thesdb-deploy setup-clustercommand that sets theallow_engine variable toipv6 truefor each newly-created node in the cluster -
Added an
allow_variable to the cluster configuration YAML file that creates nodes that can use IPv6 when running theipv6 sdb-deploy setup-clustercommand
2022-12-07 Version 1. 14. 3
-
Excludes the
processFilescollector from the default output of thesdb-report collectcommand -
Excludes the
cpuFreqPolicychecker from the default output of thesdb-report collectcommand -
Added a
--require-sslflag to thesdb-admin sync-ldapcommand to enableREQUIRE SSLfor sync users -
Changed the
sdb-report collectcommand to runinformationSchemaTablesandinformationSchemaStatisticscollectors only for the Master Aggregator node -
Permits the
allow_variable to be set in the cluster configuration YAML file for setting up the clusterunsuported_ filesystem -
Fixed a bug where the
sdb-admin restore-backupcommand would fail when trying to restore a backup from a network file system -
Changed the
nodeDirectoriesDiskUsagecollector to collect information for all subdirectories within a node’s main directory
2022-11-29 Version 1. 14. 2
-
Fixed a bug where the
sdb-admin update-configcommand would fail to set thedata_variableconversion_ compatibility_ level engine -
Added the
--ssl-caand--ssl-capathoptions to thesdb-admin start-monitoringcommand and the--exporter-ssl-cert,--exporter-ssl-key,--exporter-ssl-passphrase, and--exporter-use-httpsoptions to thesdb-admin configure monitoringcommand to support setting up monitoring over HTTPS
2022-11-16 Version 1. 14. 1
-
Fixed bug where the
sdb-report calibrate-blob-storagecommand would fail when thedata_engine variable was set toconversion_ compatibility_ level 8.0 -
Added the
informationSchemaAvailabilityGroupscollector which collects the contents of theinformation_table on an aggregator nodeschema. availability_ groups -
Added the
--shard-queriesoption to thesdb-report collect-kubecommand which reduces the load on the Master Aggregator by sharding queries among the aggregators during report collection
2022-11-09 Version 1. 14. 0
-
Prevents the
sdb-deploy upgradecommand from directly upgrading SingleStore 7.1 and earlier to SingleStore 8. 0. -
Added the
--shard-queriesoption to thesdb-report collectandsdb-report collect-and-checkcommands which reduces the load on the Master Aggregator by sharding queries among the aggregators during report collection -
Changed a
nodeDirectoriesDiskUsagecollector to report only the total size of the node directories -
Added a
nodeFilesDiskUsagecollector that collects file-level disk usage information for each node directory
2022-09-22 Version 1. 13. 13
-
Updated the monitoring schema to improve the performance of data purges
-
Deprecated the
--purge-limitoption of thesdb-admin start-monitoringcommand
2022-09-19 Version 1. 13. 12
-
Added an
--ssh-control-persistoption to thesdb-admincommand to control theControlPersistoption in SSH connections
2022-09-16 Version 1. 13. 11
-
Changed the
malloc_checker to report a warning instead of a failure on values above the thresholdactive_ memory -
Added an
--ssh-control-persistoption to thesdb-reportcommand to control theControlPersistoption in SSH connections -
Added an
--ssh-strict-host-key-checkingoption to Toolbox commands to enableStrictHostKeyCheckingin SSH connections -
Added an
--ssh-user-known-hosts-fileoption to Toolbox commands to specify the path to theknown_filehosts -
Updated the
sdb-report collectcommand to excludesmapsfiles from theprocessFilescollector’s output
2022-08-18 Version 1. 13. 10
-
Added a new
systemLimitsreport checker that ensuresnprocandNOFILEconfigurations are set to the recommended values on a host -
Fixed a bug where the
sdb-report collectcommand would fail with anhttp2: no cached connection was availableerror
2022-07-20 Version 1. 13. 9
-
Fixed a bug where
sdb-admin create-backupdid not work for local backups -
Fixed a bug where the
tracelogHardShutdownchecker reported false-positive warnings
2022-06-06 Version 1. 13. 8
-
Added a new
informationSchemaMvReplicationManagementcollector to thesdb-report collectcommand that runsSELECT *for the following tables:-
MV_REPLICATION_ MANAGEMENT -
MV_REPLICATION_ MANAGEMENT_ PARTITIONS_ STATE -
MV_REPLICATION_ MANAGEMENT_ REF_ DB_ STATE -
MV_REPLICATION_ MANAGEMENT_ STATE
-
2022-05-10 Version 1. 13. 7
-
Fixed a bug where the
sdb-report calibrate-blob-storagecommand would hang when all blobs were not successfully evicted -
Added retrying an online upgrade when the
hit error preparing for failovererror is encountered -
Updated Toolbox to only request
sudocredentials when more privileges are required than provided by the defaultmemsqluser -
Changed the order of SQL statements in the output from the
sdb-admin dumpcommand
2022-03-28 Version 1. 13. 6
-
Added the following timestamp flags to the
sdb-report collectcommand that allow logs to be collected starting from the provided timestamp:-
For audit logs:
memsqlAuditlogs.auditLogStartTimestamp -
For command logs:
memsqlCommandLogs.commandLogStartTimestamp -
For tracelogs:
memsqlTracelogs.tracelogStartTimestamp
-
-
Fixed a bug in the
installedPermissionschecker where thesdb-repot checkcommand would incorrectly report a failure -
Updated the
sdb-admin unregister-nodeandsdb-deploy setup-clustercommands to display more detailed messages should an error occur
2022-03-02 Version 1. 13. 5
-
Fixed a validation bug in the
sdb-admin register-nodecommand when configuring a node -
Fixed the partition count in the diagnostic output of the
sdb-report calibratecommand -
Fixed permission issues for the
sdb-report calibrate-blob-storagecommand -
Added the
--skip-validationoption to thesdb-admin restore-backupcommand to skip validating backups before restoring -
Updated incremental backup validation for the
sdb-admin restore-backupandsdb-admin validate-backupcommands -
Added a
tracelogHardShutdownchecker that checks for hard shutdowns in a node’s tracelog
2022-02-03 Version 1. 13. 4
-
Added the
sdb-admin enable-http-apicommand to enable the Data API on selected nodes -
Added a new
--roleoption to thesdb-admin update-configcommand.This option allows updating the configuration on all nodes that have selected role. -
Changed the
sdb-toolbox-config describe-hostcommand to prompt interactively for a hostname -
Made the online upgrade more reliable by making multiple attempts to re-attach a leaf node on account of a failure
2022-01-20 Version 1. 13. 3
-
Added a new
--skip-system-warningsoption to thesdb-admin start-node,sdb-admin restart-node, andsdb-deploy upgradecommands.This option allows users to skip displaying the extended version of system configuration limitations and warnings. -
Fixed a data file-permissions issue in the
sdb-report calibrate-blob-storagecommand -
Fixed the TSV files generated by the
sdb-report collectcommands to escape newlines, tabs, and slashes when saving query results -
By default, the
sdb-deploy setup-clustercommand now configures the host's operating system per SingleStore's recommendations.To disable this auto-configuration, use the new --skip-auto-configoption in the YAML configuration file.The --skip-auto-configoption has also been added to thesdb-deploy cluster-in-a-boxcommand.
2021-12-20 Version 1. 13. 2
-
Updated the
sdb-deploy setup-clusterandsdb-deploy cluster-in-a-boxcommands to allow the--preinstalled-pathoption to be used with Debian and Red Hat package installations -
Expanded the output of the
sdb-admin start-nodecommand with warnings about system configurations and limits -
Fixed the output of the
sdb-admin update-configcommand that is returned when the command is run for multiple hosts or for updating global variables.This fix applies to SingleStore versions 7. 3. 22 and later, 7. 5. 15, 7. 1. 25 and later, and 7. 6. 7 and later -
Improved the Toolbox monitoring commands by optimizing
purge_andblobs purge_proceduresmetrics -
Updated the
mv_column's type toqueries. query_ text LONGTEXT -
Added a new
--create-service-onlyoption to thesdb-admin enable-nodes-autostartcommand that allows the command to be run without prompting for arootpassword; this option creates amemsql.file on the specified hosts without enabling the serviceservice -
Added a new
informationSchemaMvBlockedQueriescollector to thesdb-reportcommands that runs theSELECT * FROM information_query on the Master Aggregatorschema. MV_ BLOCKED_ QUERIES -
Added a new
informationSchemaMvBottomlesscollector to thesdb-reportcommands that saves data from the following tables:-
MV_BOTTOMLESS_ API_ EVENTS -
MV_BOTTOMLESS_ REMOTE_ STATS -
MV_BOTTOMLESS_ STATUS -
MV_BOTTOMLESS_ STATUS_ EXTENDED -
MV_BOTTOMLESS_ SUMMARY -
MV_MILESTONES
-
2021-12-06 Version 1. 13. 1
-
Added support for using the
rsynccommand to copy files on a remote host ifscpis not found -
Fixed the
sdb-admin optimizecommand to work for SingleStore versions 7.5. 13, 7. 5. 14, 7. 6. 4, and 7. 6. 5 -
Updated the
--preinstalled-pathoption in thesdb-deploy upgradecommand to work with Debian and Red Hat package installations -
Updated the pre-installation checks of the
sdb-deploy upgradecommand to additionally verify that the folder specified by the--preinstalled-pathoption meets the prerequisites
2021-11-23 Version 1. 13. 0
-
Added support for starting each node as a separate
systemdunit viasystemctl.To perform this action, systemctluses ansdb-systemd-clientscript, which can be distributed across the cluster using thesdb-admin enable-systemd-clientcommand -
Updated the
--passwordflag insdb-admin change-root-passwordandsdb-admin create-nodecommands to support theMEMSQL_environment variablePASSWORD -
Fixed the
sdb-admin update-configcommand to work for SingleStore versions7.6. 4 and 7. 5. 13, however, without the support for extended output -
Improved the error message caused by running
sdb-deploycommands with the--preinstalled-pathoption in Debian and RPM package installations
2021-11-08 Version 1. 12. 5
-
Fixed an error with calling a
nilfunction in thesdb-deploycommands -
Updated the
sdb-deploy installcommand not to mark the new version of SingleStore as active in tarball-based installations.To install a new version and make it the active version, upgrade the cluster by running the sdb-deploy upgrade --preinstall-pathcommandIn Debian and RPM package installations, only one version of SingleStore can be installed at any given time
-
Fixed an issue with creating incremental backups on Network File System (mounted on a remote machine) when the target file does not exist
-
Updated the
sdb-deploy upgradecommand to retry upgrade if the process fails during partition promotion -
Added a new
sdb-admin show-clustercommand that outputs the results of bothsdb-admin show-leavesandsdb-admin show-aggregatorscommands.This command can be run on any node in the cluster if the Master Aggregator is not available. This command works with SingleStore version 7. 6 and above
2021-10-25 Version 1. 12. 4
-
Fixed the default value of the
pipelines_variable in theextractor_ get_ offsets_ timeout_ ms defaultVariableschecker of thesdb-report checkcommand -
Updated the
sdb-admin update-configcommand to restrict users from setting specific variables on node startup
2021-10-12 Version 1. 12. 3
-
Added SAML and JWT authentication methods to the
--auth-methodoption of thesdb-admin sync-ldapcommand and a new--saml-user-domain-attributeflag.SAML requires either the --user-principal-name-attributeor the--saml-user-domain-attributespecification for successful authentication.For more information, see sdb-admin sync-ldapcommand reference.
2021-09-27 Version 1. 12. 2
-
Added a new
--precheck-onlyflag to thesdb-admin enable-high-availabilitycommand to verify that high availability can be enabled on a cluster -
Added a new
force_option to theregistration: <true | false> nodesection of a cluster configuration YAML file for use with thesdb-deploy setup-clustercommand -
Added a new
--temp-dirflag to thesdb-report calibratecommand to specify the absolute path on the Master Aggregator in which to extract the dataset -
Improved the
sdb-reportcommands to verify that the command is run by amemsqlgroup member.If so, the report collects data that is otherwise restricted. If not, a warning is displayed -
Updated the
sdb-deploy upgradecommand to remove the priormemsql-server/singlestorerdb-serverversion package after a successful upgrade.Use the new --skip-uninstallflag to skip this step -
Fixed a file-permissions issue in the
sdb-deploy setup-clustercommand that would sometimes cause the command to fail when run against large, frequently-accessed databases
2021-09-13 Version 1. 12. 1
-
By default, the
sdb-toolbox-config register-hostcommand now configures the host's operating system per SingleStore's recommendations.To disable this option, use the new skip-auto-configflag -
Added support for verifying the length of the path to the runtime directory to prevent SSH issues due to long socket paths
-
Added new
informationSchemaMvAggregatedReplicationStatusandreplicationLagcollectors to report when the replication on the secondary cluster is out of sync with the primary cluster -
Improved the Toolbox command outputs to hide user passwords in verbose mode
2021-08-30 Version 1. 12. 0
-
Added
calibrate-blob-storageto thesdb-reportcommand to measure blob storage performance -
Extended the output of the
sdb-admin update-configcommand to better integrate with automation processes -
Improved the performance of permissions checks for the
sdb-deploy setup-clustercommand -
Extended the
defaultVariableschecker to check for all documented variables -
Fixed a bug in the
sdb-deploy upgradecommand that would not properly set thetoolbox_variable on all nodes if an offline upgrade failedversion
2021-08-16 Version 1. 11. 11
-
Improved
sdb-deploy cluster-in-a-boxto optimize the cluster with respect to the NUMA configuration of the host -
Added the ability to limit the number of rows collected by the
informationSchemaPipelinescollector -
Improved
sdb-admin restart-nodecommand to not require the--allflag when performing an online restart -
Improved the output of the environment validation checks in the
sdb-deploy setup-clustercommand -
Expanded the output from the
memsqlctlcommand in thesdb-admin optimizecommand -
Fixed a bug in the
sdb-deploy upgradecommand that may have led to issues with an offline upgrade following a failed online upgrade
2021-08-02 Version 1. 11. 10
-
Improved the
sdb-admin create-backupcommand to create missing directories specified in the location of file system backups -
Updated the
sdb-report collectcommand to allow optional compression of node log files -
Fixed the
sdb-report collect-and-check --include-performancecommand to run performance-related collectors and checkers in addition to the default ones -
Fixed a bug in the
sdb-report checkcommand that would cause invalid decompression of some files in cluster diagnostics reports
2021-07-19 Version 1. 11. 9
-
Added a new
dataSkewnesscollector to collect information about data skew in the cluster -
Fixed a bug in the
sdb-report send-alertcommand that would cause some collectors to become unavailable -
Updated the
sdb-deploy cluster-in-a-boxcommand to search for free ports -
Improved the
sdb-report collect-and-checkcommand to use the values defined by--remote-temp-dirand--temp-dirflags
2021-07-05 Version 1. 11. 8
-
Added a new
studioVersioncollector to collect information about the Studio version -
Updated the
sdb-report collectcommand to compress node log files before adding them to a report -
Updated the
sdb-admin start-monitoringcommand to set retention period and purge frequency on individual monitored hosts -
Fixed a pre-installation check in the
sdb-deploy setup-clustercommand that would cause an error in certain incremental cluster setups
2021-06-21 Version 1. 11. 7
-
Added pre-installation checks to
sdb-admin add-leafandsdb-admin add-aggregatorcommands.The checks can be skipped using a new --skip-validate-envflag -
Added support for creating incremental backups to the
sdb-admin create-backupcommand -
Added support for incremental backup restoration to the
sdb-admin restore-backupcommand.Specific versions of incremental backups can be restored via the --incr-backupflag -
Added support for deleting incremental backups to the
sdb-admin delete-backupcommand -
Fixed the
sdb-admin delete-backupcommand to clean up.filesmanifest -
Improved the JSON output of the
sdb-report checkcommand -
Updated the
sdb-deploy upgradecommand to allow users to retry the upgrade steps upon the occurrence of specific errors
2021-06-07 Version 1. 11. 6
-
Changed the output of the
sdb-admin list-backupscommand to include incremental backups -
Updated the
sdb-admin validate-backupcommand to validate incremental backups -
Added the
--incr-backup-idflag to thesdb-admin validate-backupcommand to validate specific versions of an incremental backup -
During an offline upgrade of SingleStore 7.
0 and later versions via the sdb-deploy upgradecommand, theleaf_engine variable will no longer be set tofailure_ detection OFF -
Improved the description of the
sdb-admin optimizecommand
2021-05-24 Version 1. 11. 5
-
Removed the redundant output from the
sdb-deploy uicommand -
Added support for installing
singlestoredb-serverpackages via thesdb-deploycommand -
Updated the
--helpflag in specific Toolbox commands to display the minimum version of SingleStore required to run the commands -
Changed the
sdb-admin start-monitoringcommand to perform query sampling by default.A new disable-sample-queriesflag has been added to this command to disable query sampling -
Improved the
sdb-report collect-kubecommand to support in-cluster configurations -
Fixed a bug in the
sdb-deploy setup-clustercommand that would sometimes cause the command to crash when running pre-installation checks
2021-05-10 Version 1. 11. 4
-
Updated the
numaConfigurationchecker to better handle multiple NUMA nodes per host -
Fixed the
transparentHugepagechecker to display the correct output when transparent huge pages are enabled and/sys/kernel/mm/transparent_is set tohugepage/defrag madvise -
Added the
toolboxEnvcollector to gather information about the Toolbox configuration -
Fixed a bug in the
sdb-report collect --merge-pathcommand that would result in either an inconsistent directory structure or a failure when merging reports from remote hosts -
Added the
sdb-admin update-node-basedircommand to move the base directory of a node and update the corresponding engine variables -
Fixed a bug in the
sdb-report collectcommand that would cause the command to crash if a node was offline -
Added the
nodeDirectoriesDiskUsagecollector to collect disk usage information for each node directory -
Improved the execution time of
informationSchemaTableStatistics,informationSchemaIndexStatistics, andinformationSchemaMvQueriescollectors
2021-04-26 Version 1. 11. 3
-
Added the
sdb-admin disable-nodes-autostartcommand to disable the use ofsystemdfor restarting all nodes on specified hosts at startup -
Added an ability to create backup using
WITH SPLIT PARTITIONSin thesdb-admin create-backupcommand -
Fixed the
installedPermissionscollector that would cause a crash if system information is unavailable for some files -
Added a snapshot retry when a database connection is not established
-
Added the
--rename-toflag to thesdb-report restore-backupcommand to rename a database while it is restored -
Fixed a bug in the
minFreeKbyteschecker that would cause the checker to use an incorrect threshold -
Updated the
sdb-deploycommand to prevent the direct upgrade from SingleStore version 6.x to 7. 5 and later -
Updated the
sdb-deploy setup-clustercommand to set theskip_property toinstall truewithout specifying thepackage_property in the cluster filetype -
Improved the
sdb-report collect-kubecommand to discover Kube services
2021-04-12 Version 1. 11. 2
-
Fixed a bug in the
sdb-admin enable-high-availabilitycommand that would cause it to fail for clusters runningmemsql-serverversions earlier than 7.1 -
Improved the description of the
--resetflag in thesdb-admin update-configcommand -
Improved the execution time of the
sdb-admin delete-nodeand thesdb-admin sync-ldapcommands
2021-03-29 Version 1. 11. 1
-
Added the
sdb-admin dumpcommand to dump cluster objects into a DDL file similar to the usage ofmysqldump -
Added OpenSSL FIPS support for Toolbox via the
--ssl-fips-modeflag in thesdb-admin create-nodeand thesdb-admin register-nodecommands, and via thessl_cluster file property in thefips_ mode sdb-deploy setup-clustercommand -
Added the
--load-balancedflag and theload_cluster file property to thebalanced sdb-deploy setup-clustercommand to allow clusters to be set up with high availability in theload_modebalanced -
Replaced the
leafPairschecker with ahighAvailabilitychecker in thesdb-reportcommand that determines the fidelity of high-availability clusters in bothpairedandload_modesbalanced -
Changed the
cpuHyperThreadingchecker in thesdb-reportcommand to not report stderr when it only contains whitespace characters, which is considered empty -
Fixed a bug in the
sdb-admin enable-high-availabilitycommand that would cause leaf nodes to be paired incorrectly
2021-03-15 Version 1. 11. 0
-
Added the
sdb-report calibratecommand to calibrate a cluster’s performance against a benchmark using a variety of queries -
Added the
whitespacesInObjectNamechecker to thesdb-reportcommand to check for objects in the schema that have leading or trailing whitespaces in their names -
Added the
--temp-dirflag to thesdb-report collectand thesdb-report collect-and-checkcommands to select a directory for storing temporary files on both remote and local hosts.The --remote-temp-dirflag is now deprecated. -
Added a new option to specify a password while executing the
sdb-admin configure-monitoringcommand; the password can now be specified via theEXPORTER_environmental variable in addition to thePASSWORD --exporter-passwordflag -
Added a check to verify that a node is registered in Toolbox and runs the same version as the Master Aggregator when the node is added as a leaf or an aggregator
-
Added the
--load-balancedflag to thesdb-admin enable-high-availabilitycommand to allow high availability to be enabled in theload_modebalanced -
Enabled the
--mask-ipflag in thesdb-report collect-kubecommand -
Removed an unused field from the Toolbox state file
-
Fixed a bug in the
sdb-report checkcommand that would cause theduplicatePartitionDatabaseschecker to return incorrect output in some cases
2021-03-01 Version 1. 10. 1
-
Added
ImplementationandLockfreeTimestampfields to the backup cache -
Improved the
sdb-deploy setup-clustercommand to skip the root password prompt if each node has a password already set -
Improved the
dmesgcollector in thesdb-report collectcommand to also look for thedmesgexecutable in/usr/bin,/bin, and/usr/local/bindirectories -
Changed the
informationSchemaProcesslistcollector in thesdb-report collectcommand to mask user credentials in the output -
Changed the
leafAverageRoundtripLatencychecker in thesdb-report checkcommand to apply stricter criteria while detecting outliers -
Fixed a bug in the
sdb-admin list-backupscommand that would cause a crash -
Fixed a bug in the
sdb-admin start-monitoringcommand that would cause timestamps in themv_table to be invalidevents
2021-02-15 Version 1. 10. 0
-
Added the
--kerberos-realmflag to thesdb-admin sync-ldapcommand to override the Kerberos realm value, which is used to create new SQL users with the--auth-method kerberosflag -
Improved the
sdb-admin describe-hostcommand to display thememsqlctlpath and thememsqlctlconfig path correctly for installations that are not tarball-based -
Changed the
informationSchemaUserPrivilegescollector to no longer run during environment validation -
Fixed a bug in the
sdb-report collect --mask-ipcommand that would cause an error when the command is run by a non-member of thememsqlgroup
2021-02-01 Version 1. 9. 7
-
Added the
sdb-report collect-kubecommand to build a diagnostics report for a Kubernetes cluster -
Added the
cgroupInfocollector and thecgroupMemoryUsagechecker to thesdb-reportcommand to check if thememsqldprocess runs inside the memory cgroup and that memory usage is not too close to the limit -
Added an ability to set availability groups in the
sdb-deploy uicommand -
Added an ability to set a
memsql-server.file as an installation target in thetar sdb-deploy uicommand -
Improved the output of the
leafAverageRoundtripLatencychecker in thesdb-report checkcommand to pinpoint the nodes that have the longest round-trip latency -
Improved the error messages caused by running Toolbox with
sudo -
Improved error messages in the
sdb-deploy upgradecommand -
Changed all Toolbox commands to no longer require a special configuration to run as the
rootuser directly and without usingsudo -
Changed the validation performed by the
sdb-deploy setup-clustercommand to be less strict for thememsqldirectory on each host -
Changed the row timeout of some queries used in the
sdb-deploy upgradecommand from 1 minute to 15 minutes -
Fixed the Toolbox auto-complete feature for
bashandzshso that it will work with bothmemsql-*andsdb-*commands -
Added taking database(s) snapshots when using Toolbox to stop or restart a node to decrease the time it takes for the node to recover
2021-01-19 Version 1. 9. 6
-
Added the
sdb-admin snapshot-databasecommand to create database snapshots -
Added the
--snapshotto thesdb-admin restart-nodeand thesdb-admin stop-nodecommands to create snapshots of databases before restarting or stopping a node -
Added the contents of the
memsqlctl.and thehcl nodes.files to the output of thehcl memsqlcltInfocollector -
Added the
ServerVersionand theMemoryUsagefields to the backup cache -
Improved the description of the
--onlineflag in thesdb-deploy upgradecommand -
Improved the request to run as
sudomessage in the Toolbox commands -
Changed the warning messages in the
defaultWorkloadManagementchecker to be more consistent -
Fixed a bug in the
sdb-report collect --mask-ipcommand that would cause an error when collecting report information for a stopped node
2021-01-08 Version 1. 9. 5
-
Improved the error message of the
sdb-deploy setup-clustercommand when an environment validation fails due to different users owning data directories of a node
2021-01-04 Version 1. 9. 4
-
Added the
--mask-ipflag to thesdb-report collectcommand to mask sensitive data in the report files, such as IP addresses, MAC addresses, usernames, and passwords -
Added the
rolecolumn to themv_table for population by the monitoring pipelinenodes -
Added the
sdb-admin enable-nodes-autostartcommand to enable nodes autostart on system reboot -
Changed the
chronydStatusand thepartitionsStartcollectors in thesdb-reportcommand to be excluded by default -
Changed the description of
analyzeTablecollector in thesdb-reportcommand -
Changed the memory units in the
consistent_checker from kilobytes (KB) to megabytes (MB)maximum_ memory
2020-12-15 Version 1. 9. 3
-
Fixed an issue in the deployment UI that would occur after clicking the Add Another Host button
-
Fixed a bug in the
sdb-deploy setup-clustercommand that would sometimes place thememsqlctl.file in an incorrect folderhcl
2020-12-14 Version 1. 9. 2
-
As of Toolbox 1.
9. 2, each memsql-command now has an associatedsdb-analog that is both compatible with, and functionally identical to, thememsql-command.All memsql-commands will continue to function as expected.With this enhancement: -
sdb-adminis equivalent tomemsql-admin -
sdb-deployis equivalent tomemsql-deploy -
sdb-reportis equivalent tomemsql-report -
sdb-toolbox-configis equivalent tomemsql-toolbox-config
-
-
Added the
sdb-toolbox-config state, thesdb-deploy state, thesdb-admin state, and thesdb-report statecommands to display the Toolbox state from thetoolbox-state.filehcl -
Added the
--preinstalled-pathflag to thesdb-deploy install,sdb-deploy cluster-in-a-box, and thesdb-deploy setup-clustercommands to specify the folder where amemsql-server.file has been extracted as an install targettar -
Added the
networdBuffersMaxchecker to thesdb-reportcommand to check that thewmem_and themax rmem_values are at least 8MBmax -
Added the
--config-fileflag to thesdb-admin send-alertcommand to specify a YAML file containing both the location and the thresholds as an alternative to using the--alert-locationand the--thresholdsflags -
Added the
--monitoring-versionflag to thesdb-admin start-monitoringcommand to specify amemsql-serverversion to pass to thememsql-exporter -
Added the
--batch-intervalflag to thesdb-admin start-monitoringcommand to specify a time interval between data extractions -
Added the
--sample-queriesand the--high-cardinality-metricsflags to thesdb-admin start-monitoringcommand to enable the collection of additional monitoring data -
Updated the
sdb-admin start-monitoringcommand to support features introduced in the SingleStore 7.3 version of the memsql-exporter -
Changed the
mallocActiveMemorychecker to fail ifmalloc_is greater than 5GB (up from 2GB)active_ memory -
Changed the
diskUsageand thediskInodesUsagecheckers in thesdb-report checkcommand to not report high usage on loopback filesystems -
Fixed a bug in the
sdb-deploy upgradecommand that would sometimes cause aggregator actions to be displayed in an incorrect order during a dry run
2020-11-30 Version 1. 9. 1
-
Added the
processFilescollector to thememsql-reportcommand to collect all/proc/<pid>/*files for thememsqldand thememsqld_processessafe -
Added the
autoAttachchecker to thememsql-reportcommand to warn if theauto_engine variable is not set toattach ON -
Added the
--preinstalled-pathflag to thememsql-deploy upgradecommand to specify the folder as an upgrade target where amemsql-server.file has been extractedtar -
Improved the error message for the
memsql-deploy uicommand when registered hosts are detected
2020-11-16 Version 1. 9. 0
-
Added the
cgroupDisabledchecker andosReleasecollector to thememsql-reportcommand to check thatcgroup memoryis disabled for Red Hat 7.x or later -
Added the
memsql-report send-alertcommand to automatically runmemsql-report collect-and-checkand alert on fails or warnings -
Updated the descriptions of multiple checkers in the
memsql-reportcommand -
Improved the long message for the
memsql-admin change-root-passwordcommand -
Improved the long message for the
memsql-admin change-root-passwordcommand -
Improved the error message for the
memsql-admin start-monitoringcommand when the exporter host is inaccessible from other hosts -
Improved the error messages related to environment validation in the
memsql-report collectand thememsql-deploy setup-clustercommands -
Improved the
orchestratorProcesseschecker to include each process in the report only once, even if more than one instance of the process is running on the host -
Changed the
memsql-deploy setup-clustercommand to check that all of the nodes that will be registered have the correct file permissions and owner -
Changed the output of the
schemacollector to include views definitions, and improved how functions, procedures, and error messages are displayed -
Changed the
memsql-deploy setup-clustercommand to set thesecure_engine variable to a default path offile_ priv <memsqlctl's-default-install-dir>/db_for each newly-created nodefiles -
Fixed a bug in the
memsq-admin restart-nodecommand that would sometimes display an incorrect error message -
Fixed a bug in the
clusterMemoryUsagechecker that would produce incorrect output -
Fixed a bug in the
memsql-admin enable-high-availabilitycommand that would sometimes cause a kernel panic if Toolbox is configured incorrectly
2020-11-02 Version 1. 8. 1
-
Improved the error message in the
memsql-adminbackup-related commands when the--repositoryflag contains an invalid value -
Fixed a bug where the
memsql-report check --validate-envcommand would crash when a host has TarInstallDir defined andmemsql-serverinstalled -
Added the
installedPermissionschecker and collector to thememsql-reportcommand to verify that cluster files and directories have the correct permissions -
Fixed a bug where the
--skip-validate-envflag was ignored by thememsql-deploy setup-clustercommand -
Added the
--data-dirflag to thememsql-deploy setup-clustercommand for specifying the absolute path to each node’s data directory (DataDir) -
Improved the
memsql-deploy uicommand to support pre-deployment environmental checks -
Improved the error message in the
memsql-admin restart-node --onlinecommand to inform the user that relevant nodes must be running to perform the restart -
Fixed a bug in the
memsql-deploy upgradecommand that incorrectly determined that all columnstore tables could be safely upgraded
2020-10-19 Version 1. 8. 0
-
Added the
memsql-admin sync-ldapcommand to synchronize LDAP users and groups with SingleStore/MemSQL database users -
Added a dry (trial) run message to the
memsql-report collectcommand that displays the number of collectors that will be executed -
Fixed a bug where the value of the timeout in the
memsql-admin query --row-timeoutcommand was not taken into account by the command -
Added a
clusterMemoryUsagechecker to thememsql-report checkcommand to determine if there is at least 10% of unused memory left for each node -
Added a
diskInodesUsagechecker to thememsql-report checkcommand to determine if there is at least 15% of unused disk inodes left on each host -
Fix a bug where the
dmesg -Tcommand was not executed while collecting reports with thememsql-report collectcommand -
Added a
diskLatencyReadchecker to thememsql-report checkcommand to determine if the disk read latency is below the recommended threshold on each host -
Added a
diskLatencyWritechecker to thememsql-report checkcommand to determine if the disk write latency is below the recommended threshold on each host
2020-10-05 Version 1. 7. 2
-
Added the
memsql-admin unregister-nodeandmemsqlctl unregister-nodecommands to unregister nodes in Toolbox -
Added the
majorPageFaultschecker and collector to thememsql-reportcommand to verify if the number of major page faults that the system generates per second is lower than a specific threshold -
Added the
swapUsagechecker and collector to thememsql-reportcommand to verify if the swap usage is lower than a specific threshold -
Added the
cpuIdlechecker and thecpuUtilizationcollector to thememsql-reportcommand to verify if the percentage of time the CPUs have been idle is higher than a specific threshold -
Added the
memoryCommittedchecker and collector to thememsql-reportcommand to verify if the percentage of memory required for a given workload is less than a specific threshold -
Added the
swapEnabledchecker to thememsql-report checkcommand to verify if the total swap memory is not less than 10% of the physical memory -
Added the
vmSwappinesschecker to thememsql-report checkcommand that checks if thevm.kernel setting is greater thanswappiness 0on each host -
Added environment validation to the
memsql-deploy setup-clustercommand -
Added the
--tar-install-dirflag to thememsql-deploy cluster-in-a-boxcommand -
Changed the
max_checker of thememory_ settings memsql-report checkcommand to accept a maximum memory use of 91%, up from 90% -
Updated the
memsql-admin querycommand to not require a password for the MemSQLrootuser -
Updated the
memsql-admin change-root-password,memsql-admin create-node,memsql-admin query, andmemsql-admin register-nodecommands to prompt for a password only after all of the included flags have been verified -
Improved the warning messages in the
memsql-deploy upgrade --precheck-onlycommand -
Fixed a bug in the
memsql-report checkcommand where messages about unavailable checks were displayed -
Fixed a bug where the
syncCnfVariableschecker in thememsql-report checkcommand would inadvertently return incorrect results -
Fixed a bug in the
memsql-admin querycommand that would ignore the--userflag -
Fixed a bug in the
memsqlctlcommand where some commands that were run with the--timeoutflag would not exit after the specified timeout
2020-09-21 Version 1. 7. 1
-
Added an
--include memsqlAuditlogsflag to thememsql-report collectcommand to collect audit logs -
Fixed a bug in the
memsql-report checkcommand wheremaxMemorySettingsreported a failure when a host has more than 10GB of memory free -
Added a
no_option to thestart: true nodesection of a cluster configuration YAML file for use with thememsql-deploy setup-clustercommand -
Fixed a bug where host fingerprinting would fail to compute on some hosts
-
Added a
--no-partition-changeflag to thememsql-admin optimizecommand to skip any changes made to thedefault_MemSQL variablepartition_ per_ leaf -
Fixed a bug in the
memsql-admin enable-high-availabilitycommand that would co-locate nodes on the same host that were in different availability groups -
Improved the error message for the
memsql-deploy setup-clustercommand when duplicate hosts are found in the cluster configuration YAML file -
Improved the logging function by saving all of the messages generated when running Toolbox commands with the
--jsonflag -
Improved the
memsql-deploy setup-clustercommand to display an error message when a node is specified with an incorrect availability group in the cluster configuration YAML file -
Fixed a bug where standard output of
memsqlctlcommands was sometimes lost -
Moved the message that
memsqlctlis an earlier version to verbose output
2020-09-09 Version 1. 7. 0
-
Added the
memsql-admin configure-monitoringcommand that updates the monitoring configuration for the cluster -
Added the
memsql-admin start-monitoringandmemsql-admin stop-monitoringcommands to start and stop the collection of monitoring data -
Added the
memsql-report collect-and-checkcommand that runs both collect and check reports -
Improved the high availability functionality in the
memsql-deploy setup-clusercommand by pairing leaves of different hosts -
Fixed a bug in the
memsql-admin enable-high-availabilitycommand where nodes were assigned non-optimal availability groups -
Improved the
memsql-deploy upgradecommand to report all precheck failures -
Improved the
memsql-deploy setup-clustercommand to explain why a clean cluster is required before deploying MemSQL -
Fixed a bug where the
syncCnfVariableschecker would crash in thememsql-report checkcommand -
Fixed a bug in the
memsql-admin querycommand where--passwordwas not correctly processed
2020-08-26 Version 1. 6. 7
-
Fixed a bug where an
access denied
error would cause thememsql-deploy upgradecommand to fail
2020-08-21 Version 1. 6. 6
-
Added
bashandzshtab completion to all Toolbox commands -
Fixed a bug in the
memsql-admin querycommand where--passwordwas not correctly processed -
Improved the
memsql-admin bootstrap-aggregator,memsql-admin create-node,memsql-admin set-license,memsql-deploy cluster-in-a-box, andmemsql-deploy setup-clustercommands to use the license from the MEMSQL_LICENSE environment variable -
Fixed a bug where
memsql-deploy upgradewould fail due to a replicating database -
Fixed a bug where a blob existed but couldn’t be opened in the
memsql-adminbackup-related commands -
Improved logging to always include output of SQL queries
-
Fixed the error message in the
memsql-deploy setup-clustercommand when a host withoutmemsql-serverinstalled was already part of the cluster -
Added a warning to not edit the
memsql.file manuallycnf -
Added retries to
sudoprompting -
Improved the error message for the
memsql-deploy upgradecommand when using a tar file without specifyingtar-install-dir -
Improved the
transparentHugepagechecker of thememsql-report checkcommand to not check defrag if THP is disabled
2020-08-10 Version 1. 6. 5
-
Added the
attachRebalanceDelaychecker to thememsql-report checkcommand that verifies that attachRebalanceDelay is not set to 86400 -
Fixed a bug where an error wasn’t displayed when attaching a leaf failed while executing the
memsql-deploy upgradecommand -
Updated the
memsql-toolbox-config register-hostcommand to validate the--memsqlctl-pathvalue and added the--skip-validationflag to skip this validation -
Improved the
memsql-deploy upgradecommand to attempt to attach and detach a leaf under certain error conditions instead of proceeding to an offline upgrade -
Improved the error message when an attempted SSH connection fails
-
Added the
diskBandwidthchecker to thememsql-report checkcommand that checks disk read, write, and sync-read bandwidth -
Improved the
informationSchemaMvEventschecker of thememsql-report checkcommand to order events by time -
Added the
--disable-spinnerflag to all Toolbox commands to disable the progress spinner, which some terminal sessions/environments may have issues with -
Improved the
memsql-deploy setup-clustercommand to suppress an error if one or more hosts did not havememsqlctlinstalled -
Changed the
validLicensechecker of thememsql-report checkcommand to report in units for clusters with a unit-based license -
Added the
--base-install-dirflag to thememsql-deploy setup-clustercommand which sets each node’s base install directory on all hosts
2020-07-27 Version 1. 6. 4
-
Improved the
memsql-admin delete-backupcommand to no longer error if a backup name is listed more than once -
Added a password prompt to all Toolbox commands as an alternative to specifying the password as a command-line argument, which would be captured in the shell’s history
-
Fixed a bug where tarball-based installations failed for remote hosts
-
Improved the descriptions of the
memsql-admin delete-node,memsql-deploy uninstall, andmemsql-toolbox-config unregister-hostcommands -
Added the
consistentMaxMemorychecker to thememsql-report checkcommand that confirms themaximum_setting is consistent across all leaves and aggregatorsmemory -
Added the
memsql-deploy destroy-clustercommand that deletes all data, deletes all MemSQL nodes, and unregisters all hosts -
Improved the dry runs of the
memsql-admin delete-node,memsql-deploy uninstall, andmemsql-toolbox-config unregister-hostcommands -
Improved the cluster file used by the
memsql-deploy setup-clustercommand to accept the case-insensitive role of a node -
Added an
--allflag to thememsql-admin describe-nodecommand to list the details for all nodes -
Added a
--precheck-onlyflag to thememsql-deploy upgradecommand to check if a cluster is stable and an upgrade is possible without performing an upgrade -
Improved the
memsql-admincommand’s backup/restore functionality to search for a backup in a repository if one isn’t found in a cache -
Improved the
memsql-deploy upgradecommand to compare the target upgrade version against the major version that is already installed -
Changed the
syncCnfVariableschecker of thememsql-report checkcommand to confirm that its value is equal to the runtime value inmemsql-server
2020-07-13 Version 1. 6. 2
-
Added the
--master-port,--leaf-port, and--bind-addressflags to thememsql-deploy cluster-in-a-boxcommand -
Updated the
memsql-deploy setup-clustercommands to not allow SSH for localhost -
Fixed a bug where the
memsql-deploy upgradecommand fails when memsql-server 7.1 is already installed on a host -
Added details as to why some Toolbox commands prompt for a
sudopassword -
Added a check in the
memsql-deploy upgradecommand that confirms that the activememsql-serverpackage is the one for the target version -
Updated the
memsql-deploy setup-clustercommand to provide the same output with or without the--config-fileflag -
Removed the connections per node limit in the
memsql-deploy upgradecommand -
Fixed a bug where SSH standard error output was sometimes discarded
-
Added a
--file-pathflag to thememsql-admin set-licensecommand to allow the license to be stored in, and read from, a file -
Updated the
memsql-deploycommands to prompt for which package manager to use if bothdebandrpmpackage managers are installed -
Improved the version checks of the
memsql-deploy upgradecommand -
Added a
--skip-version-checkflag to thememsql-deploy upgradecommand that ignores the currently active memsql version and enables downgrading -
Added the
--role,--license,--user,--user-password,--availability-group, and--force-masterflags to thememsql-admin create-nodecommand.Refer to the memsql-admin create-node reference page for more information. -
Improved the functionality of the collector-related flags in the
memsql-reportcommands
2020-06-30 Version 1. 6. 1
-
Fixed a bug where
memsql-deploy setup-clusterfails when run with the--cluster-fileflag
2020-06-29 Version 1. 6. 0
-
Changed the
memsql-deploy cluster-in-a-boxcommand to bind nodes to the address127.instead of0. 0. 1 0.0. 0. 0 -
Changed the
memsql-deploy uninstall --all-versionscommand to return a0exit code if there are no versions to uninstall -
Added the
memsql-deploy uicommand that runs a web UI to install MemSQL and deploy a cluster -
Added
syncCnfVariableschecker to thememsql-report checkcommand that confirms that there are no sync variables values defined in thememsql.file on a hostcnf -
Updated the
memsql-deploy cluster-in-a-boxcommand to deduce the package format when the--file-pathflag is specified -
Added the
--force-package-formatflag to thememsql-deploy list-versionscommand that lists the versions installed by the chosen package manager -
Fixed a bug where
memsql-deploy upgradedisplays an error message when attempting to upgrade to the MemSQL version that already installed and activated on the host -
Changed the
memsql-report checkcommand to display results only for checkers that have all needed data, and list those checkers that do not -
Updated the
memsql-admin optimizecommand to display a message when non-uniform memory allocations for leaves are found -
Updated the description of the
memsql-admin put-filecommand
2020-06-15 Version 1. 5. 5
-
Added a required
--passwordflag to thememsql-deploy cluster-in-a-boxcommand that sets a password for the MemSQLrootuser -
Fixed a bug where the
memsql-report checkcommand crashes when theorphanTableschecker does not find specific information in a report -
Fixed a typo in the
memsql-reportcommand’s error message when it fails to detect whethermemsqlctlis installed on a host -
Fixed a bug where performance collectors were executed by default with the
memsql-report collectcommand -
Added support for
fileprotocol formemsql-adminbackup functionality
2020-06-03 Version 1. 5. 4
-
Added a
--force-package-formatflag to thememsql-deploy uninstallcommand which will allow MemSQL to be uninstalled when there are both dpkg and rpm package managers found on a host -
Fixed a bug where
memsql-admin enable-high-availabilityfails with MemSQL version below 7.0. 6 -
Added the result of
ANALYZE OPTIMIZER_of theSTATE INTO OUTFILE memsql-report collectcommand to the collector’s section of theanalyzeTablesreport -
Fixed a bug where
memsql-report checkwould issue a warning on a validdistributed_valuekeepalive_ timeout -
Updated the
memsql-deploy list-versionscommand to display its output more quickly -
Displays a more specific error message when a file on a host cannot be accessed
-
Updated the output of commands that are run with
-vvvto be more readable -
Added
--remote-temp-dirflag to thememsql-report collectcommand that allows setting a directory for storing temporary files on a host -
Fixed a bug where a
validLicensecheck reports a failure on a valid license
2020-05-18 Version 1. 5. 3
-
Added
analyzeTablescollector tomemsql-report collectthat saves column and histograms recorded on each table -
Added the ability to store a path to a license file (rather than the license itself) in the cluster configuration file used by
memsql-deploy setup-cluster --cluster-file -
Improved
dmesgcollector with timestamps that users can recognize and interpret -
Fixed a bug where
memsql-deploy upgradedoes not show an error if the final upgrade step fails -
Fixed a bug where
memsql-deploy upgradewould hang if there were orphan databases -
Added a
--max-column-widthflag to thememsql-admin querycommand that allows query output columns to be truncated to the specified number of characters -
Added a
--allow-duplicate-host-fingerprintsflag tomemsql-deploy setup-clusterandmemsql-toolbox-config register-hostcommands that allows hosts with identical SSH host keys to be added to the cluster
2020-05-04 Version 1. 5. 2
-
Fixed a bug where
memsql-report collecthangs when collecting reports from some hosts -
Fixed a bug where a
cpuFreqPolicycheck reports a failure on a valid configuration -
Fixed a bug where the
chronydStatuscollector does not work for a host that does not havepgrep -
Removed
maxOpenFilesandfilesystemTypechecks frommemsql-report check --validate-env -
Added a warning and the request for user conformation when
memsql-toolbox-config register-hostis run with--localhostand--host 127.0. 0. 1 -
Fixed a bug where
memsql-deploy upgradeincorrectly estimates the disk space required to upgrade from MemSQL 6 to MemSQL 7 -
Made
memsql-admin delete-backupfaster by deleting multiple backups in parallel -
Added
cpuMemoryBandwidthcollector and checker tomemsql-reportthat measures CPU-memory bandwidth on each host and confirms that both bandwidth and latency are within acceptable limits -
Added
--include-performanceflag tomemsql-report collectandmemsql-report checkthat is required to run performance checks for a cluster -
Displays a detailed error message when the
memsql-toolbox-config register-hostandmemsql-deploy setup-clustercommands are run with multiple localhosts
2020-04-20 Version 1. 5. 1
-
Added new collectors and checkers to
memsql-report collectandmemsql-report checkcommands:-
memsqldProcessLimits
collects limits for allmemsqldprocesses -
chronydStatus
collects the status of thechronydservice -
chronydDisabled
checks thatchronydis disabled -
partitionsStart
collects information about each partition’s start sector number -
partitionsConsistency
checks that all partition start sectors are consistent -
cpuThreadingInfo
collects information about CPU threading configuration -
cpuHyperThreading
checks that all CPUs have hyperthreading enabled -
cpuFreqInfo
collects information about CPU frequency configuration -
cpuFreqPolicy
checks that all CPUs have power save disabled and turbo mode enabled
-
-
Fixed a bug where the
ulimitchecker reportsFAILeven when set correctly for thememsqluser -
Displays a more meaningful error message when
regionorendpoint_is missing in a backup commandurl -
Fixed a bug where
memsql-report collectfails if some node IDs could not be read -
Fixed a bug where
memsql-deploy upgrade --onlinefails to upgrade from MemSQL version 7.0. 15 -
Added
region
to the backup functionality help examples
2020-04-06 Version 1. 5. 0
-
Added functionality for backup management:
-
memsql-admin create-backup- backup one or more databases to a repository -
memsql-admin delete-backup- delete a backup -
memsql-admin list-backups- list all the latest backups -
memsql-admin restore-backup- restore a database from a backup -
memsql-admin summarize-backups- print summary information for backups -
memsql-admin validate-backup- verify that a backup is correct
-
-
Fixed a bug where
memsql-deploy setup-clusterfails if the cluster configuration file containsskip_install:true -
Added a check to
memsql-deploy setup-clusterthat prevents nodes from sharing the same folder on a host when specified in a cluster configuration file
2020-03-23 Version 1. 4. 4
-
Added computation of a
fingerprint
for each host to avoid adding the same host multiple times under a different name. -
Added
--onlineflag formemsql-deploy upgradethat runs online upgrade for MemSQL. -
Fixed a bug where detectCrashStackTraces check displayed warnings if the memsqlStacks.
files. json file was absent. -
Improved error message for
memsql-deploy setup-clusterwhen the path to the source file is incorrect. -
Added toolboxConfig collector to
memsql-report collectthat saves the Toolbox’s configuration to a report file. -
Added a host collector to
memsql-report collectthat saves each host’s description to a report file. -
Fixed a bug where
memsql-admin enable-high-availabilitydoes not request the correct privilege. -
Added a snapshot retry before upgrade if a database is re-provisioning.
-
Removed extra escape characters in log outputs to make verbose logs more readable.
2020-03-09 Version 1. 4. 3
-
Improved command
memsql-deploy upgrade:-
Added a disk space check and a database snapshot is taken before an upgrade is started.
-
Added cleanup steps in case of an unsuccessful upgrade.
-
-
Added
memsql-admin put-filecommand that copies a file to the same path on all hosts. -
Fixed a bug where
memsql-admin stop-node --all --forcedid not stop any nodes if one node was unavailable. -
Stopped producing messages if no action will be taken by a command.
-
Fixed a bug where
memsql-deploy upgradedid not wait for the database to restart after an upgrade is finished. -
Fixed a bug in
memsql-admin enable-high-availabilitywhere the command does not work correctly if two leaf nodes on the same host have different hostnames. -
Added an additional check to
memsql-reportthat ensures all cluster hosts have SSD drives. -
Added
--validate-envoption tomemsql-reportthat will validate if MemSQL can be installed.
2020-02-11 Version 1. 4. 2
-
Improved the prompt message that is displayed when upgrading databases to the new replication modes in MemSQL 7.
0. -
Improved the speed of health checks that are performed on columnstore tables during upgrades.
-
Improved the way
memsql-deploy upgradewaits for node recovery. -
Fixed a bug where
memsql-toolbox-configis not able to resolve a state file but returns incorrect error. -
Fixed a bug where
memsql-deploydownloaded the package twice for online upgrade. -
Fixed the behavior of disk checks before upgrade: always fail upgrade if there is not enough space, show success message on success only.
-
Fixed a bug where toolbox commands did not close the environment after a command failure.
-
Added command-line flag checks to
memsqlctlclient. -
Added possibility to set MaxSSHSessionsPerHost parameter with command line (
--ssh-max-sessions) or config file. -
Fixed bug where the
memsql-deploy setup-cluster --cluster-file <cluster-file>command returns nodes with Unknown role.
2019-11-25 Version 1. 4. 1
-
Fixed a bug where all Toolbox commands were not able to pass the
--parallelismflag. -
Fixed a bug where running
memsql-deploy upgradewithout any flags would perform a rolling restart on the cluster. -
Fixed a bug where the user would always be prompted for changes to the replication mode of the databases, instead of only being asked when upgrading to MemSQL 7.
0.
2019-11-19 Version 1. 4. 0
-
Updated
memsql-deployto support upgrade to MemSQL 7.0 -
Added TSV based output for some
memsql-reportcollectors. -
Fixed a bug where
memsql-report checkfails to check for blocked queries with time 0. -
Updated
memsql-admin update-config --set-globalto automatically run on the Master Aggregator. -
Updated the
securityLimitscollector to include the output of/etc/security/limits.andd /proc/PID/limits -
Updated the
numactlchecker to check if the sum of numa node memory capacity exceeds machine memory capacity. -
Added new collectors to
memsql-report collect:-
top -
informationSchemaMvBackupHistory
-
-
Added new checkers to
memsql-report check:-
orphanTables
-
2019-10-09 Version 1. 3. 0
-
Added support for
memsql-deploy setup-clusterto accept a YAML file with cluster configurations. -
Fixed a bug where
memsql-reportexits with a status of 0 if it fails. -
Fixed a bug that caused the output of
memsql-report collectto be not parsable bymemsql-report check -
Added new collectors to
memsql-report collect:-
uptime -
shutdownTime -
rebootTime
-
-
Added new checkers to
memsql-report check:-
tracelogOOM -
tracelogOOD -
explainRebalancePartitionsChecker -
longRunningQueries -
detectCrashStackTraces -
defaultVariables
-
-
Updated the checkers
defaultKeepaliveSettingsanddefaultHeartbeatSettingsto be part ofdefaultVariableschecker
2019-09-03 Version 1. 2. 3
-
Fixed a bug where the output of
memsql-report collectcould be missing information.
2019-08-06 Version 1. 2. 2
-
Added support for rootless memsql-server installs using tar-based packages.
-
Added the
--roleflag tomemsql-admin start-nodeto start the nodes by role. -
Added the
--roleflag tomemsql-admin stop-nodeto stop the nodes by role. -
Added the
Bind Addresscolumn tomemsql-admin list-nodesoutput. -
Updated
memsql-admin delete-nodeto remove leaves and child aggregators from the cluster before deleting them. -
Updated the sort order for
memsql-admin list-nodesto be consistent with other commands. -
Improved the readability of the
License Expirationfield inmemsql-admin show-license. -
Fixed a bug that caused the
schemacollector inmemsql-report collectto not collect procedures from memsql-server version 6.7. 11 and above. -
Added new collectors to
memsql-report collect:-
explainRestoreRedundancy -
explainRebalancePartitions -
showClusterStatus
-
-
Added new checkers to
memsql-report check:-
delayedThreadLaunches
-
2019-04-22 Version 1. 1. 1
-
Added the
--stopflag tomemsql-admin delete-nodeto stop the nodes before deleting them. -
Added the
--host,--port,--user, and--passwordflags tomemsql-admin queryfor querying a node directly. -
Added new checkers to memsql-report check:
-
disconnectedReplicationSlaves -
interpreterMode -
leafAverageRoundtripLatency -
runningBackup -
secondaryDatabases -
validLicense
-
-
Updated checkers in
memsql-report check:-
blockedQueriesalso looks for sleeping threads with open transactions -
offlineLeavesrenamed toleavesNotOnline
-
-
Added table-based output for some
memsql-reportcollectors. -
Shortened the filenames inside a cluster report to avoid name length limits in archive files.
2019-03-19 Version 1. 1. 0
-
Fixed a bug that prevented NOPASSWD sudo from being considered passwordless sudo.
-
Added the
memsql-admin querycommand. -
Added more properties to
memsql-admin list-nodesandmemsql-admin describe-node. -
Removed the
swappinesschecker.The setting it checked is not required by MemSQL 6. 7. -
Updated the
informationSchemaPipelinescollector to includeinformation_andschema. PIPELINES_ CURSORS information_.schema. PIPELINES_ FILES -
Added new collectors to
memsql-report collect:-
explainOrphanDatabases -
informationSchemaMvQueries -
licenseMetadata
-
-
Added new checkers to
memsql-report check:-
defaultHeartbeatSettings -
defaultKeepaliveSettings -
defaultWorkloadManagement -
defunctProcesses -
duplicatePartitionDatabase -
failedCodegen -
offlineAggregators -
offlineLeaves -
pendingDatabases -
queuedQueries -
userDatabaseRedundancy -
versionHashes
-
-
Updated the report format to include the source paths of copied files.
-
Updated the
envcommands to include the resolvedconfigFilelocation.
2019-01-08 Version 1. 0. 6
-
Updated
memsql-deploy cluster-in-a-boxto set passwords that are required bymemsqlctl create-nodestarting in MemSQL 6.7. 8. -
memsql-admin create-nodenow requires the--passwordflag. -
Added the
--base-install-dirflag tomemsql-admin create-node. -
Updated
memsql-report collect --onlyto also include thememsqlctlInfocollector by default. -
Added a safety check to
memsql-deploy setup-clusterthat prevents enabling High Availability with an odd number of leaves. -
Added the
--skip-disk-checkflag tomemsql-admin enable-high-availability.
2018-12-04 Version 1. 0. 4 (internal only)
-
Added the attempted command string to error messages due to failed command execution.
-
Added support for running commands as a Linux user that is part of an unnamed group.
-
Fixed a bug in
memsql-deploy installthat improperly failed the installation if it was unable to add the target user to thememsqlLinux group. -
Added support for advanced
memsqlctlconfiguration tomemsql-report collect-local. -
Reduced spurious errors from
memsql-report checkwhenmemsqlctlis not installed on the target hosts. -
Added support for changing the SQL root password on all nodes in the cluster with
memsql-admin change-root-password.
2018-11-27 Version 1. 0. 3
-
Added advanced
memsqlctlconfiguration flags tomemsql-toolbox-config register-host. -
Enabled parallelism for
memsql-report collect. -
Added the report file path to the output of
memsql-report collectandmemsql-report collect-local. -
Fixed a bug in
memsql-adminconfirmation messages that incorrectly implied the use of--passwordwhen it was not used.
2018-11-20 Version 1. 0. 2
-
Fixed bug preventing the use of
memsql-admin update-config --all. -
Added
host
field tomemsql-admin describe-nodeoutput. -
Fixed a bug in
memsql-deploy list-versionswhen there are no hosts registered. -
Changed permissions logic to use
memsqlctlconfiguration to determine the correct user and group for remote commands.
Last modified: September 30, 2025