Deadlock detection and long running queries: introduces db_long_query_time_alarm (specify in cmon.cnf), if a query takes longer than db_long_query_time_alarm to execute an alarm will be raised containing detailed information about blocked and long running transactions. db_long_query_time_alarm = 0 (disable), default value 5.
Changes in ClusterControl v1.2.8
Sep 17th, 2014
Create Single DB Node. Launch/provision a single MySQL Galera node or MongoDB ReplicaSet member node to a host.
Create MySQL DB Users and Privileges across several DB clusters at once.
LDAP improvements. Better support for AD. Added member+dn support. Groups and Users can be on different baseDN.
Support for Alerts and Incident tracking with external providers using a new Alarm/Events plugin system. PagerDuty plugin/integration available.
Unified Event Viewer. Show merged log entries (entries from multiple log sources) correlated with alarms/events occurrences.
New alarms/email notification system. Daily alarm digests (summary). Fine-tune email delivery of different alarms/events.
"Capacity Planner" (ALPHA). Add this constant to the UI's bootstrap.php file, define('RPC_PORT','9500'); to enable access to it.
Three new default MySQL dashboards. InnoDB IO, Query Performance and Galera Flow Control graphs.
Audit logging. User activity tracking. Username and originating IP is logged in the Job log.
Add Node (MySQL/MongoDB) improvements.
yum/apt repo server for ClusterControl! See this blog post for details.
Changes in ClusterControl v1.2.6
Apr 22nd, 2014
LDAP Authentication (BETA)
User Role based access to ClusterControl functions
OpenStack: Launch OST instances & Deploy a Galera Cluster (BETA)
Manage multiple Galera Clusters with a single ClusterControl Controller host
Show Master and Slaves added to a Galera Cluster
Manage/Monitor MySQL Servers (auto detects if replication is enabled)
Embedded Classic DB Configurations Wizard deprecated/removed!
Changes in ClusterControl v1.2.5
Feb 11th, 2014
Support for Galera 3.x builds (Codership & PXC 5.6)
AWS VPC (Create/Delete and Deploy) BETA
Custom Expressions (User defined alerts/alarms)
Support for agent-less monitoring
Minor UI changes
Changes in ClusterControl v1.2.4c (maintenance release)
Dec 13th, 2013
Updated s9s_sw_update to reflect changes in Percona Repositories for Ubuntu.
Bug: Invalid clear of wsrep_cluster_addresses on controller startup.
Changes in ClusterControl v1.2.4
Nov 19th, 2013
Online backup storage in AWS S3 and Glacier
Multi-cluster support. Share one Controller Node with multiple clusters
Add existing Galera cluster via ClusterControl to monitor and manage
Galera database configurator facelift
Automatically deploy Galera and MongoDB cluster from ClusterControl
Time shift stats/graphs
MongoDB ReplicaSet AWS Deployment for Dev/Test env.
AWS deployments now use our web site to generate a database configuration. Deploy the latest GA version of Galera/MongoDB.
Mongodb: auth support (mongodb_user and mongodb_password)
Changes in ClusterControl v.1.2.3
July 15th, 2013
Clone Galera Cluster via the GUI (s9s_clone)
Deploy HAProxy and Keepalived with VIP via the GUI
User defined "dashboards" in the Overview page (quickly select your favorite graphs to show)
New Overview page for Galera clusters
MySQL Query Histogram added to the Performance page
New view for DB variables and status (MySQL) added to the Performance tab. Easier to view and compare status/variables across all nodes
Execute external/user made scripts (on the controller node)
Customizable refresh rate (DB variables and status)
Start/stop and rebuild MySQL replication slave for MySQL 5.6
Reboot host from UI
Improved sampling of statistics (better resolution)
[MONGODB] Replica set support
[MONGODB] Backups with mongodump
[MONGODB] Tokumx support
[MONGODB] Arbiter support (add/remove from cmd line)
Changes in ClusterControl v.1.2.2 May 16th, 2013
Deploy Galera cluster nodes on multi AZs and regions on AWS (great for test/dev)
The Job log is available now in the 'Logs' view
Simple database schema and user management (feature set from our classic cmon gui)
Activate/deactivate monitoring of external processes (Mangage-Process)
Add node for MariaDB
Logfile Analyzer - automatically checks and detects problems found in mysql error logs.
Changes in ClusterControl v.1.2.1 May 2nd, 2013
Added support for MongoDB backup
New database growth graph
MySQL status time machine table (show status value differences over time)
Deploy Galera cluster on AWS (only on a single AZ). Great for test/dev.
Moved settings (Configurations, Hosts, Processes, Software Packages, Upgrade, Schema graphs) views to new 'Manage' tab
Fixed bugs in add node
centralized backup, store backup data on controller by using s9s_backupc
replication 5.6 aware (GTID)
s9s_backup was changed, upgrade of s9s_backup on all nodes is required.
email bug for SMTP notifications.
recovery improvements in galera (refuse to recover cluster if a majority of the nodes cannot be reached), and recovery will be retried for a much long period of time (to avoid Galera node recovery blocked messages).
s9s-admin tools (on controller do: git clone git://github.com/severalnines/s9s-admin.git ) for more details.
check /usr/lib64/ for libgalera_smm.so
Changes in ClusterControl v.1.2.0
March 14, 2013
Improvements to support ClusterControl GUI
Changes in ClusterControl v1.1.33
August 1st, 2012
Notes: - Controller: Added alarms for Replication, in case a MySQL Server crashes - Controller: Alarms for Galera, in case a MySQL Server crashes - Controller: Removed redundant messages and newlines from log messages - Controller: Persisting db|host_stats_collection interval to cmon db - Query Monitor: log_queries_not_using_indexes now settable from the Web Interface - Query Monitor: Set long query time via Web interface. Setting upper bound (1MB) on query size to be parsed. - Query Monitor: Possibility to override CMON settings in favor for local my.cnf settings - WWW + Controller: Reworked Configuration Management + web interface - WWW + Controller: Last mysql error now saved in mysql_server table - RRD: Optimized rrd graph creation, optimized galera stats collection to reduce db writes - WWW: Added ‘clear all jobs’ button - MySQL Cluster: Display an error in the Web UI if an SQL Node is not connected to the cluster - Galera: Improvements in availability handling, in case createPrimary fails
Bug fixes: - Replication: serverid + autoincrement sedding fixed - Replication: Fixed MaxConnection bug in Replication - MySQL Cluster: Fixed Index/DataMemory collection problem if MemoryReportFrequency is not set - MySQL Cluster: Fixed bug in MGM status info, preventing rolling restarts - MySQL Cluster: Fixed bug in stop node (SQL/Data node) - Galera: Make node statistics less jumpy during restarts/recovery - Controller: Clear MySQL replication links when a MySQL Server is removed from the cluster - Controller: fixed bug causing multiple email messages to be sent in case of an alarm - Controller: Fixed ProcessList bug if pidfile already had a path to prevent concatenation with datadir - Controller: Added printout to error log if a pidfile could not be opened by the Process Manager - Controller: Prevent autorestart of failed agents from happening too fast - Backup: Fixes in length of file issue (backup file size was 0 sometimes)
Notes: - Added load averages in ClusterControl Web interface - Removed unnecessary log messages - Added new configuration parameter to cmon.cnf: enable_autorecovery=1 (default 1 == enabled, 0 means disabled - only manual recovery). - Galera: It is now possible to manually recover a non-Primary Galera node from the ClusterControl web interface. - Galera: Improved handling of cluster recovery. Pass 1: find the best node to recover from and make it the new Primary. Pass 2: Recover the remainder of the nodes from the new Primary
- Galera: Cleaned up redundant table galera_status_history
Bug fixes: - Fixed buffer overrun in query profiling and anonymizing queries (affects agents only) - Disable autorestart of failed agents from happening too fast - Galera: Handling of existing provider_options when setting pc.bootstrap - Buffer overrun in log message - Backups: Fixed issue with a stale mysql connection - Added error handling to process stat collection (a process could have existed when a vector of pids were assembled, but process terminated before being used) - RRD: Fixed "ERROR: /var/lib/cmon//cluster_1_stats.rrd: expected 9 data source readings (got 1) from N"