Deployment of new Databse servers in cluster control
-
Official comment
Hi,
The error you saw in the cmon.log has nothing to do with MariaDB Replication. It indicates cmon process couldn't save the entry into CMON database because of the limit in "max_allowed_packet". Please increase the max_allowed_packet value inside my.cnf on ClusterControl node. Try to double it up if you have suffiecient RAM.
1. do replication needs to be inplace before using cluster control?
- Yes, if you are importing an existing cluster into ClusterControl. The replication cluster must not be in degraded state because ClusterControl needs to see the whole topology correctly in the first import attempt.
- Otherwise, you would want to use "Deploy Cluster" feature, and then modify the my.cnf file to suit your needs right after the deployment completes.
2. what version of cluster control supports mariadb 5.5?
- IIRC, the last version that supports new deployment of MariaDB 5.5 was 1.2.11 (Dec 11th, 2015). If you insist to run a new MariaDB 5.5 on the latest version of ClusterControl, you have to install them manually, setup the replication link and then import them into ClusterControl. Otherwise, use 10.1 or 10.2. Note that we are talking about new deployment here, not importing an existing cluster. ClusterControl supports MariaDB 5.5 for existing setup.
3. i made slave database as a readonly database to deploy into the cluster, the node is failing after adding into cluster when i change it to writable its working but no data is replicating. so here the master and slave which should be writable and read-only
- Have you tried to use "Rebuild Replication Slave" or "Change Replication Master" on the old master? I'd like to see the MySQL error log to understand what was going on and how to assist you further. I believe you've created a support ticket for this issue. Please generate an error report by going to ClusterControl -> pick the cluster -> Logs -> Error Reports -> Create Error Report and attach the generated tarball in the support ticket.Regards,
AshrafComment actions -
I have an application running from two sites, i tried to replicate them using clustercontrol. i made some changes in my.cnf file on both the servers. i am using Clustercontrol 1.6 community version as of now.
On master:
log-bin=/var/log/mariadb/mariadb-bin.log
binlog-do-db=mysql
binlog-do-db=nagios
binlog-do-db=nagiosxi
binlog-do-db=nagiosql
binlog-do-db=test
binlog-do-db=performance_schema
binlog-do-db=information_schema
replicate-ignore-db = mysql
replicate-ignore-table=nagiosxi.xi_auditlog
server-id=1
binlog_format='MIXED'
max_allowed_packet=500M
on slave:
server_id=2
binlog_format='MIXED'
relay-log=/var/log/mariadb/mariadb-relay-bin.log
replicate-wild-do-table=nagios.%
replicate-wild-do-table=nagiosxi.%
replicate-wild-do-table=nagiosql.%
replicate-wild-do-table=test.%
replicate-wild-do-table=mysql.%
replicate-wild-do-table=information_schema.%
replicate-wild-do-table=performance_schema.%
replicate-ignore-table=nagiosxi.xi_auditlog
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
max_allowed_packet=500M
Installed Cluster control on a different server other than the two and tried to replicate the both. i tried with importing server and added the servers.
i tried to change some data on master but i didn't see any data on the slave.
i saw couple of errors on cmon.log
(WARNING) failed command: "REPLACE INTO cmon_host_log (cid, hostname, filename, jobid, result, result_len, hostid) VALUES(25, "master_server_ip", "/var/log/mariadb/mariadb.log", 0, "180523 9:57:50 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT... ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO nagios_programstatus SET instance_id=\'1\', status_update_time=FROM_UNIXTIME(1527083870), program_start_time=FROM_UNIXTIME(1527008042), is_currently_running=\'1\', process_id=\'13786\', daemon_mode=\'1\', last_command_check=FROM_UNIXTIME(0), last_log_rotation=FROM_UNIXTIME(1527047999), notifications_enabled=\'1\', active_service_checks_enabled=\'1\', passive_service_checks_enabled=\'1\', active_host_checks_enabled=\'1\', passive_host_checks_enabled=\'1\', event_handlers_enabled=\'1\', flap_detection_enabled=\'1\', failure_prediction_enabled=\'0\', process_performance_data=\'1\', obsess_over_hosts=\'0\', obsess_over_services=\'0\',": Got a packet bigger than 'max_allowed_packet' bytes
(ERROR) Connecting to mail server failed: poll timeout (30s) on socket 34.
2018-06-08 10:05:58 : (WARNING) Sending with server mx1.comcast.net failed: poll timeout (30s) on socket 34.
(ERROR) Connecting to mail server failed: poll timeout (30s) on socket 30.
2018-06-08 10:52:59 : (WARNING) Sending with server mx2.comcast.net failed: poll timeout (30s) on socket 30.
2018-06-08 10:52:59 : (WARNING) Sending mail with SMTP failed.
i have a couple o questions
1. do replication needs to be inplace before using cluster control?
2. what version of cluster control supports mariadb 5.5
3. i made slave database as a readonly database to deploy into the cluster, the node is failing after adding into cluster when i change it to writable its working but no data is replicating. so here the master and slave which should be writable and read-only -
Hi,
we are on to opt Cluster control 1.2.11 (Dec 11th, 2015). But I see only 1.2.12, does it support mariadb 5.5? if not can you please provide us the path to version 1.2.11 and also can you please provide me steps on how to install version 1.2.11 and deploy servers to MYSQL Replication.
Thanks,
Mohan
-
Hi,
currently I have mariadb 5.5, does control cluster 1.6 supports it, I see only Mariadb 10.1 and 10.2 in control cluster 1.6. Can you please provide me steps on how to deploy new servers/databses to cluster control for MYSQL Replication.ERROR LOG:
[15:12:09] master-server: There is a mysqld server running. It must be uninstalled first, or you can also add it to ClusterControl.
[15:12:08]:master-server::3306: Checking if host already exists in another cluster.
[15:12:08]:All 2 hosts are accessible by SSH.
[15:12:08]:Using sudo password for further communication.
[15:12:08]:slave_server: Access with ssh/sudo granted.
[15:12:08]:master-server:: Access with ssh/sudo granted.
[15:12:08]:Checking ssh/sudo on 2 hosts.
[15:12:08]:Verifying job parameters.Thanks,
Mohan
Please sign in to leave a comment.
Comments
5 comments