Severalnines Support
- Total activity 126
- Last activity
- Member since
- Following 0 users
- Followed by 0 users
- Votes 2
- Subscriptions 61
Posts
Recent activity by Severalnines Support Sort by recent activity-
CLI: View Server Status
The status.sh script will ping (using both ‘ping’ and ‘mysqladmin ping’) each mysql server and print out if they are connected or not. [root@clustercontrol scripts]# ./status.sh -a Master hosts ...
-
CLI: Start a MySQL Server
The following command starts a MySQL Server, whether it is a master or a slave. The script will automatically detect if the host is a Master or a Slave and copy out the correct configuration file (...
-
CLI: Stop a Slave
There are two ways of stopping a Slave server. One way is to explicitly stop the Slave: [root@clustercontrol scripts]# ./stop-slave.sh -h app03 app03: Executing '/etc/init.d/mysqld stop' [ok] I...
-
CLI: Stop Replication
The following command stops replication between app02 (master) and app03 (slave). [root@clustercontrol scripts]# ./stop-repl.sh -m app02 -s app03 stopping replication between app02 --> app03 replic...
-
CLI: Start Replication
The following command starts replication between app02 (master) and app03 (slave). [root@clustercontrol scripts]# ./start-repl.sh -m app02 -s app03 starting replication between app02 --> app03 (...
-
CLI: Show Replication Status
Scripts are located on the ClusterControl server, under: s9s-mysql-55/mysql/scripts/ [root@clustercontrol scripts]# ./repl-status.sh master_host -->slave_host status master_status ...
-
Handling of Slave failure
If a slave fails, applications connected to the slave can connect to another slave and continue to operate. When the slave comes up again, it will resynchronize with the master and be available to...
-
Handling of Backup Master failure
In case the backup master fails, the master will still continue to replicate its updates to the slaves. Applications still do their updates on the master. The replication cluster does not need rec...
-
Handling of master server failure
Updates are done on the master server only. If the master fails, replication will stop. Applications doing updates reconnect to the backup master and then continue to operate. Effectively, the bac...
-
Automated fail-over with ClusterControl™
In order to keep the Replication cluster stable and running, it is important for the system to be resilient to failures. Failures are caused by either software bugs or hardware problems, and can ha...