Removing master status
Not sure how it happened, I copyied a KVM VPS while shut down where there was a MySQL 5.7 database I want to test upgrade to 8.0 on FreeBSD 13.2. While it also has a jailed mysql process running on port 3307 setup as a slave to another master, the database running on the default port 3306 is a standalone database with no replication set up at all.
After getting the copied QEMU disk booted with its own IP address and the jail disabled on boot, I find in phpmyadmin where the Replication is set as a master and slave configurations. I went back and checked the source VPS to confirm it has no Replication configuration at all. I did the following to stop and reset the slave...
STOP SLAVE;
RESET SLAVE;
RESET SLAVE ALL;
That removed the slave configuration, but the master remains...
root@localhost [(none)]> show master status;
+---------------+----------+--------------+------------------+---------------------------------------------+
| File | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |
+---------------+----------+--------------+------------------+---------------------------------------------+
| binlog.000003 | 157 | | | ca3f72cd-03be-11ed-97ff-5254006b63d5:1-9387 |
+---------------+----------+--------------+------------------+---------------------------------------------+
I found this should work? But not...
root@localhost [(none)]> CHANGE MASTER TO MASTER_HOST='';
ERROR 1210 (HY000): Incorrect arguments to SOURCE_HOST
root@localhost [(none)]> show master status;
Not sure how this Replication got configured with this mysqld config? I tried to comment out the relay-log, sync_binlog and sync_relay_log.
[mysqld]
user = mysql
port = 3306
socket = /tmp/mysql.sock
bind-address = *
basedir = /usr/local
datadir = /www/db/mysql
tmpdir = /www/db/mysql_tmpdir
secure-file-priv = /www/db/mysql_secure
relay-log = /www/db/log/mysql-relay-bin.log
log-output = FILE
general-log = 1
general-log-file = /www/db/log/general.log
relay-log-recovery = 1
slow-query-log = 1
sync_binlog = 1
sync_relay_log = 1
binlog_cache_size = 16M
expire_logs_days = 30
default_password_lifetime = 0
enforce-gtid-consistency = 1
gtid-mode = OFF
safe-user-create = 1
lower_case_table_names = 1
explicit-defaults-for-timestamp = 1
myisam-recover-options = BACKUP,FORCE
open_files_limit = 32768
table_open_cache = 16384
table_definition_cache = 8192
net_retry_count = 16384
key_buffer_size = 256M
max_allowed_packet = 64M
query_cache_type = 0
query_cache_size = 0
long_query_time = 0.5
innodb_buffer_pool_size = 1G
innodb_data_home_dir = /www/db/mysql
innodb_log_group_home_dir = /www/db/mysql
innodb_data_file_path = ibdata1:128M:autoextend
innodb_temp_data_file_path = ibtmp1:128M:autoextend
innodb_flush_method = O_DIRECT
innodb_log_file_size = 256M
innodb_log_buffer_size = 16M
innodb_write_io_threads = 8
innodb_read_io_threads = 8
innodb_autoinc_lock_mode = 2
skip-symbolic-links
tls_version = TLSv1.2
Any other pointers regarding the upgrade are much appreciated.
Subject
Views
Written By
Posted
Removing master status
543
December 01, 2023 01:08PM
Sorry, only registered users may post in this forum.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.