Watch the 7.3 Webinar On-Demand
This new release brings updates to Universal Storage, query optimization, and usability that you won’t want to miss.
Please follow this guide to learn how to migrate to SingleStore tools.
The changelog for key MemSQL Ops releases is listed here. To verify and download the latest GA version of Ops, see http://versions.singlestore.com/memsql-ops/latest-v6.
transaction_bufferon the Master Aggregator would fail if the Master Aggregator and the Ops Primary Agent were not on the same host
agent-uninstallreturns when it cannot uninstall the agent because there are still SingleStore nodes managed by the agent. Now, the error message includes the agent ID and the MemSQL IDs of the nodes that are blocking the uninstall.
memsql-topfrom MemSQL Ops
EXPLAIN CLEAR ORPHAN DATABASESappears in the cluster report
sql_modeengine variable, when used globally, could break some queries that MemSQL Ops runs
memsql-ops memsql-update-root-passwordno longer needs to remove/add leaf
SHOW VARIABLES LIKE '%'
SHOW RESOURCE POOLS
SHOW WORKLOAD MANAGEMENT STATUS
SELECT * FROM information_schema.MV_EVENTS
sysctl -aand Transparent Huge Pages information to Cluster Report
agent-upgradecommand will check for the latest version of MemSQL Ops over the Internet if the user supplies a version or tarball path
timeoutargument has been added to the MEMSQL-STOP command.
_BTduring cluster reports by default
SKIP ... ERRORSmodes in the Pipelines interface. See LOAD DATA for more information.
mountto cluster reports
In Progressbatches were being incorrectly cached by Ops, which means they would not disappear from the interface
High Availabilitynotifications over
Deploy MemSQLmodal would go two steps back instead of one
UNREACHABLEwhich indicates that Ops cannot connect to the SingleStore DB instance
--limitto job-list to limit the number of jobs listed
information_schema.processlistto cluster report