Quantcast
Channel: MySQL Forums - Replication
Viewing all 1561 articles
Browse latest View live

Slave Replication lag in time (2 replies)

$
0
0
Hi All,

Having a problem with MySQL 5.5.35 Master / Slave replication.

Using InnoDB engine.

Root problem:

Seconds_behind_the_master - keeps growing up and unable to catch-up the master until it loss last bin-log.

Slave I/O / Slave_SQL - shows status as YES.
Statement update mode: Mixed
Both Master and Slave having the same hardware configuration

Tried many different advices to resolve, among them:

1) Timesync verification
2) Setting new replication.
3) Reseting master.
4) Stoping Slave_SQL_THREAD
5) innodb_flush_log_at_trx_commit = 0
6) Creating a new fresh instance.


Below is myL:

Master status:

mysql> show master status;
+-------------------+-----------+--------------+------------------+
| File | Position | Binlog_Do_DB | Binlog_Ignore_DB |
+-------------------+-----------+--------------+------------------+
| mysql2-bin.031682 | 300009048 | | |
+-------------------+-----------+--------------+------------------+
1 row in set (0.00 sec)


Slave status:

Slave_IO_State: Waiting for master to send event
Master_Host: 10.253.1.23
Master_User: slave
Master_Port: 3306
Connect_Retry: 60
Master_Log_File: mysql2-bin.031682
Read_Master_Log_Pos: 315893523
Relay_Log_File: mysql-relay-bin.000002
Relay_Log_Pos: 119851712
Relay_Master_Log_File: mysql2-bin.031676
Slave_IO_Running: Yes
Slave_SQL_Running: Yes
Replicate_Do_DB:
Replicate_Ignore_DB:
Replicate_Do_Table:
Replicate_Ignore_Table:
Replicate_Wild_Do_Table:
Replicate_Wild_Ignore_Table:
Last_Errno: 0
Last_Error:
Skip_Counter: 0
Exec_Master_Log_Pos: 362358490
Relay_Log_Space: 3219895040
Until_Condition: None
Until_Log_File:
Until_Log_Pos: 0
Master_SSL_Allowed: No
Master_SSL_CA_File:
Master_SSL_CA_Path:
Master_SSL_Cert:
Master_SSL_Cipher:
Master_SSL_Key:
Seconds_Behind_Master: 39865
Master_SSL_Verify_Server_Cert: No
Last_IO_Errno: 0
Last_IO_Error:
Last_SQL_Errno: 0
Last_SQL_Error:
Replicate_Ignore_Server_Ids:
Master_Server_Id: 1
1 row in set (0.00 sec)

process list:

+-----+-------------+-----------+------+---------+-------+----------------------------------+------------------+
| Id | User | Host | db | Command | Time | State | Info |
+-----+-------------+-----------+------+---------+-------+----------------------------------+------------------+
| 141 | system user | | NULL | Connect | 345 | Waiting for master to send event | NULL |
| 142 | system user | | NULL | Connect | 39975 | Reading event from the relay log | NULL |
| 144 | root | localhost | NULL | Query | 0 | NULL | show processlist |
+-----+-------------+-----------+------+---------+-------+----------------------------------+------------------+
3 rows in set (0.00 sec)


Any other advice, what else can be possible to done?

Replication Setup Not Working (no replies)

$
0
0
I am trying to set up some replication. the story so far..
GRANT REPLICATION SLAVE ON *.* TO 'replicator'@'%' IDENTIFIED BY 'eV4ng311C4L';
Query OK, 0 rows affected (0.00 sec)

FLUSH TABLES WITH READ LOCK;

SHOW MASTER STATUS;

and on slave...
STOP SLAVE;
CHANGE MASTER TO MASTER_HOST = '10.0.2.38', MASTER_USER = 'replicator', MASTER_PASSWORD = 'my_password', MASTER_LOG_FILE = 'mysql-bin.000004', MASTER_LOG_POS =1782;

Back to master and...
UNLOCK TABLES;
Query OK, 0 rows affected (0.00 sec)

And on slave

START SLAVE;

SHOW FULL PROCESSLIST;

+-----+-------------+-----------+------+---------+------+-----------------------------------------------------------------------------+-----------------------+
| Id | User | Host | db | Command | Time | State | Info |
+-----+-------------+-----------+------+---------+------+-----------------------------------------------------------------------------+-----------------------+
| 234 | root | localhost | NULL | Query | 0 | NULL | SHOW FULL PROCESSLIST |
| 243 | system user | | NULL | Connect | 84 | Waiting for master to send event | NULL |
| 244 | system user | | NULL | Connect | 84 | Slave has read all relay log; waiting for the slave I/O thread to update it | NULL |
+-----+-------------+-----------+------+---------+------+-----------------------------------------------------------------------------+-----------------------+

> SHOW SLAVE STATUS\G;
*************************** 1. row ***************************
Slave_IO_State: Waiting for master to send event
Master_Host: 10.0.2.38
Master_User: replicator
Master_Port: 3306
Connect_Retry: 60
Master_Log_File: mysql-bin.000004
Read_Master_Log_Pos: 1782
Relay_Log_File: mysqld-relay-bin.000002
Relay_Log_Pos: 253
Relay_Master_Log_File: mysql-bin.000004
Slave_IO_Running: Yes
Slave_SQL_Running: Yes
Replicate_Do_DB:
Replicate_Ignore_DB:
Replicate_Do_Table:
Replicate_Ignore_Table:
Replicate_Wild_Do_Table:
Replicate_Wild_Ignore_Table:
Last_Errno: 0
Last_Error:
Skip_Counter: 0
Exec_Master_Log_Pos: 1782
Relay_Log_Space: 410
Until_Condition: None
Until_Log_File:
Until_Log_Pos: 0
Master_SSL_Allowed: No
Master_SSL_CA_File:
Master_SSL_CA_Path:
Master_SSL_Cert:
Master_SSL_Cipher:
Master_SSL_Key:
Seconds_Behind_Master: 0
Master_SSL_Verify_Server_Cert: No
Last_IO_Errno: 0
Last_IO_Error:
Last_SQL_Errno: 0
Last_SQL_Error:
Replicate_Ignore_Server_Ids:
Master_Server_Id: 1
1 row in set (0.00 sec)


How many things am I doing wrong here?

Kind regards
Kevin

Many values for Executed_Gtid_Set (no replies)

$
0
0
When I run show slave status, there are many values returned for Executed_Gtid_Set.

GTID variables:
enforce_gtid_consistency:ON gtid_executed:
gtid_mode: ON
gtid_next: AUTOMATIC
gtid_owned:
gtid_purged: 45fc3ac6-b6b9-11e2-a509-00163e00215f:1-720909539,
f13859a5-b6d9-11e2-a5de-00163e002160:1-8371

mysql version:5.6.13-log

Executed_Gtid_Set: 45fc3ac6-b6b9-11e2-a509-00163e00215f:1-720912678:720912680-720912681:720912683-720912684:720912686:720912688-720914434:720914436-720914437:720914439-720914440:7...
This goes on with hundereds of values.

What can I set to put this back to the normal 1 value per replication server in the group?

how to tell if the GTID is working fine (no replies)

$
0
0
Hi everyone,

I'm currently setting up a GTID replication on my test VMs.
here is my conf related to the GTID.

my hostnames and IP addresses:
mysql56-1.wrx4.vm 192.168.1.103
mysql56-2.wrx4.vm 192.168.1.104


my.cnf in mysql56-1
-------------------
binlog-format=ROW
log-slave-updates=true
gtid-mode=on
enforce-gtid-consistency=true
master-info-repository=TABLE
relay-log-info-repository=TABLE
sync-master-info=1
slave-parallel-workers=2
binlog-checksum=CRC32
master-verify-checksum=1
slave-sql-verify-checksum=1
binlog-rows-query-log_events=1
server-id=1
report-port=3306
port=3306
log-bin=mysql56-1-bin.log
report-host=mysql56-1.wrx4.vm


my.cnf in mysql56-2
-------------------
binlog-format=ROW
log-slave-updates=true
gtid-mode=on
enforce-gtid-consistency=true
master-info-repository=TABLE
relay-log-info-repository=TABLE
sync-master-info=1
slave-parallel-workers=2
binlog-checksum=CRC32
master-verify-checksum=1
slave-sql-verify-checksum=1
binlog-rows-query-log_events=1
server-id=2
report-port=3306
port=3306
log-bin=mysql56-2-bin.log
report-host=mysql56-2.wrx4.vm



then the next step was to start the replication:
mysqlreplicate --master=root:'password'@192.168.1.103:3306 --slave=root:'password'@192.168.1.104:3306


mysqlrplshow --master=root:'password'@192.168.1.103 --discover-slaves-login=root:'password'
# master on 192.168.1.103: ... connected.
# Finding slaves for master: 192.168.1.103:3306

# Replication Topology Graph
192.168.1.103:3306 (MASTER)
|
+--- mysql56-2.wrx4.vm:3306 - (SLAVE)



however, why does the mysqlfailover command does not show my slave?

mysqlfailover --master=root:'password'@192.168.1.103 --discover-slaves-login=root:'password'@192.168.1.104 --rediscover

WARNING: There are slaves that had connection errors.
# Checking privileges.
# Discovering slaves for master at 192.168.1.103:3306
Error connecting to a slave as root@mysql56-2.wrx4.vm: Cannot connect to the slave server.
Error Access denied for user 'root'@'mysql56-2.wrx4.vm' (using password: YES)

WARNING: There are slaves that had connection errors.

MySQL Replication Failover Utility
Failover Mode = auto Next Interval = Fri Feb 28 00:16:32 2014

Master Information
------------------
Binary Log File Position Binlog_Do_DB Binlog_Ignore_DB
mysql56-1-bin.000001 299

GTID Executed Set
dabf96c7-454d-11e3-86c8-080027ce8198:1

Replication Health Status
+----------------+-------+---------+--------+------------+---------+
| host | port | role | state | gtid_mode | health |
+----------------+-------+---------+--------+------------+---------+
| 192.168.1.103 | 3306 | MASTER | UP | ON | OK |
+----------------+-------+---------+--------+------------+---------+




I can login with that password to the mysql56-2.

$ mysql -u root -ppassword -h mysql56-2.wrx4.vm
Warning: Using a password on the command line interface can be insecure.
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 31
Server version: 5.6.14-enterprise-commercial-advanced-log MySQL Enterprise Server - Advanced Edition (Commercial)

Copyright (c) 2000, 2013, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql>





Please help me solving this issue.

Thank you,
Adhika

MySQL 5.5 Replication broke after upgrade (no replies)

$
0
0
I've seen this question, but I am not sure if the solution is right for my particular error (http://dba.stackexchange.com/questions/40377/replication-breaks-after-upgrading-master)

I upgrade my master server's mysql from 5.5.34 to 5.5.35. After doing that, the SQL_THREAD stopped and this is what's in the error log

140225 12:43:40 [ERROR] Slave SQL: Query caused different errors on master and slave. Error on master: message (format)='Cannot load from mysql.%s. The table is probably corrupted' error code=1548 ; Error on slave: actual message='no error', error code=0. Default database: 'performance_schema'. Query: 'DROP DATABASE IF EXISTS performance_schema', Error_code: 0
140225 12:43:40 [Warning] Slave: Cannot load from mysql.proc. The table is probably corrupted Error_code: 1548
140225 12:43:40 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'mysql-bin.000127' position 17538

I have since upgraded the slave as well and tried running mysql_upgrade on both and trying to start the SQL_THREAD, but it won't start.

What can I do to fix this while keeping the slave's copy accurate?

Here is the show slave status:

*************************** 1. row ***************************
Slave_IO_State: Waiting for master to send event
Master_Host: 10.0.40.20
Master_User: slave_user
Master_Port: 3306
Connect_Retry: 60
Master_Log_File: mysql-bin.000133
Read_Master_Log_Pos: 34984217
Relay_Log_File: mysqld-relay-bin.000061
Relay_Log_Pos: 17684
Relay_Master_Log_File: mysql-bin.000127
Slave_IO_Running: Yes
Slave_SQL_Running: No
Replicate_Do_DB:
Replicate_Ignore_DB:
Replicate_Do_Table:
Replicate_Ignore_Table:
Replicate_Wild_Do_Table:
Replicate_Wild_Ignore_Table:
Last_Errno: 0
Last_Error: Query caused different errors on master and slave. Error on master: message (format)='Cannot load from mysql.%s. The table is probably corrupted' error code=1548 ; Error on slave: actual message='no error', error code=0. Default database: 'performance_schema'. Query: 'DROP DATABASE IF EXISTS performance_schema'
Skip_Counter: 0
Exec_Master_Log_Pos: 17538
Relay_Log_Space: 35137400
Until_Condition: None
Until_Log_File:
Until_Log_Pos: 0
Master_SSL_Allowed: No
Master_SSL_CA_File:
Master_SSL_CA_Path:
Master_SSL_Cert:
Master_SSL_Cipher:
Master_SSL_Key:
Seconds_Behind_Master: NULL
Master_SSL_Verify_Server_Cert: No
Last_IO_Errno: 0
Last_IO_Error:
Last_SQL_Errno: 0
Last_SQL_Error: Query caused different errors on master and slave. Error on master: message (format)='Cannot load from mysql.%s. The table is probably corrupted' error code=1548 ; Error on slave: actual message='no error', error code=0. Default database: 'performance_schema'. Query: 'DROP DATABASE IF EXISTS performance_schema'
Replicate_Ignore_Server_Ids:
Master_Server_Id: 20
1 row in set (0.00 sec)

Master Slave Replication - Got fatal error 1236 from master (no replies)

$
0
0
# Trying to do Master - Slave Replication
# Master is on Website Server, and Slave is on Localhost / Computer
# Slave (Localhost Computer) - TO - Master (Website Server) is successfull
# Master - TO - Slave, is Not successfull - Receiving below error message

Got fatal error 1236 from master when reading data from binary log: 'Slave can not handle replication events with the checksum that master is configured to log; the first event 'mysql-bin.000004' at 4, the last event read from '.\mysql-bin.000004' at 120, the last byte read from '.\mys

Replace replication slave after long downtime (1 reply)

$
0
0
I have a mySQL 5.5 server which was set up to replicate to a remotely located slave several years year ago. The slave hard disk crashed many months ago so the master bin-logs have been growing but not being used by any slave. I now want to set up a new slave, so I expect I will need to reset/clear the bin logs before I do. I figure after all this time it is best just to "start again" with the setup. Is this just a matter of turning off replication and turning off bin-logging, and starting again? Will the logs clear automatically? DO I need to manually delete the bin-logs? If so, how safe is this process for the data on the master?

Master-Master Replication :: master_log_pos changes on each update (no replies)

$
0
0
Using MySQL Master-Master Replication Technique synchronizing the data between two servers.

Upon editing some data in any table, the changes get reflected at other end as well.

MASTER_LOG_POS changes on every change whenever an update is done at either end. Both Databases are not in sync after the position changes.

Please help to correct this problem ??

Problem with slave filtering.. (no replies)

$
0
0
Hi,
I have filtered out slave as below
replicate-wild-do-table=DB1.%
replicate-wild-ignore-table=DB2.norep%

means i want to execute all statements on tables related to DB1 database and all tables except table names starting with norep from DB2. After configuring this , DB1 replication is fine but slave ignoring all transaction on DB2 even table names are not starting with norep.

MYSQL Replication (1 reply)

$
0
0
Hi,

I have got mysql replication setup. Everything looks fine. There is no lag at all. However my slave doesnt show the latest updates from the master.

MySQL master/slave on the same host (1 reply)

$
0
0
Hi,

I'm testing the MySQL master/slave replication setup procedure; on one single linux host.
I use the Raw Data Files to clone the master database to the slave database. The master/slave database setup work well. But I get the following error message from "show slave status":

Fatal error: The slave I/O thread stops because master and slave have equal MySQL server UUIDs; these UUIDs must be different for replication to work.

The auto.cnf is copied from master to slave without change, so I kind of understand the error message from the slave instance.

My question is, can I change the server-uuid in auto.cnf in the slave instance? How does it affect the database data?

Harry

Real-Time Data Loading from MySQL to Hadoop with New Tungsten Replicator 3.0 (no replies)

$
0
0
Launch webinar, March 27th. Register at https://www1.gotomeeting.com/register/225780945.

Hadoop is an increasingly popular means of analyzing transaction data from single MySQL or multiple MySQL servers. Up until now mechanisms for moving data between MySQL and Hadoop have been rather limited. The new Continuent Tungsten Replicator 3.0 provides enterprise-quality replication from MySQL to Hadoop. Tungsten Replicator 3.0 is 100% open source, released under a GPL V2 license, and available for download at https://code.google.com/p/tungsten-replicator/.

Continuent Tungsten handles MySQL transaction types including INSERT/UPDATE/DELETE operations and can materialize binlogs as well as mirror-image data copies in Hadoop. Continuent Tungsten also has the high performance necessary to load data from busy source MySQL systems into Hadoop clusters with minimal load on source systems while retaining control over how the data is viewed and accessed within Hadoop.

We will discuss:

• How Hadoop works and why it's useful for processing transaction data from MySQL
• Setting up Continuent Tungsten replication from MySQL to Hadoop
• Understanding how Hadoop makes data analytics efficient and easy to execute
• Tuning replication to maximize performance.

Presenter:

• MC Brown, Director of Documentation, Continuent

Launch webinar, March 27th. Register at https://www1.gotomeeting.com/register/225780945.

Moving data from master to slave using mysqldump (no replies)

$
0
0
Hi,
I followed the instructions in mysql document 16.1.1.5 Creating a Data Snapshot Using mysqldump to move data from master to slave.

I dumped the master database with the following command without stop the master datase:
mysqldump --all-databases --master-data > master.dmp

Then import the dumped data into the slave with the following command:
mysql < master.dmp

And I get the following error:
ERROR 1062 (23000) at line 6257: Duplicate entry 'indosat-completeserviceegresspacketoctetslogrecorddaily#P#Monthl' for key 'PRIMARY'

I have a partitioned table completeserviceegresspacketoctetslogrecorddaily in indosat schema.But this table is empty. I have other empty partitioned tables in indosat schema as well. But the import always failed on this particular table.

How to start replication over from scratch.... (1 reply)

$
0
0
OK so I totally screwed my master\slave replication setup I had. My question is how do I just stop the replication and start over?

I have already done the "stop slave", then "reset slave all" command on the slave, and removed all replication options from my.cnf However once I reenable replication it appears that replication wants to pick back up and I get errors on the slave like
'table cloud.op_lock' doesn't exist error_code: 1146...

I literally just want to start over...

Err no:1236 : reading header of binary log while looking for the oldest binary log that contains any GTID that is not in the given gtid set' (no replies)

$
0
0
Hi ,
received strange error as
Last_IO_Errno: 1236
Last_IO_Error: Got fatal error 1236 from master when reading data from binary log: 'Error reading header of binary log while looking for the oldest binary log that contains any GTID that is not in the given gtid set'.

In error code 1236 ,this description i have seen for the first time. Any idea.. it is bit urjent.

Master binary log rotation not proper after restarting mysql server? (1 reply)

$
0
0
After restarting mysql master server,it rotates binlog file and update Previous-GTIDs at initial header. but in one of our server it has not updated this value so gotting ": Got fatal error 1236 from master when reading data from binary log: 'Error reading header of binary log while looking for the oldest binary log that contains any GTID that is not in the given gtid set'" at SLAVE.

Here is the contents of binary new binary log file,
/*!50530 SET @@SESSION.PSEUDO_SLAVE_MODE=1*/;
/*!40019 SET @@session.max_insert_delayed_threads=0*/;
/*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;
DELIMITER /*!*/;
# at 4
#140314 18:43:41 server id 1 end_log_pos 120 CRC32 0x2b2ead2b Start: binlog v 4, server v 5.6.16-log created 140314 18:43:41
# Warning: this binlog is either in use or was not closed properly.
BINLOG '
3U0jUw8BAAAAdAAAAHgAAAABAAQANS42LjE2LWxvZwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAEzgNAAgAEgAEBAQEEgAAXAAEGggAAAAICAgCAAAACgoKGRkAASut
Lis=
'/*!*/;
# at 120
#140315 16:35:12 server id 1 end_log_pos 168 CRC32 0x80784e26 GTID [commit=yes]
SET @@SESSION.GTID_NEXT= 'd5146594-ab7d-11e3-a120-90e2ba45437e:118'/*!*/;
# at 168


Could i know the reason in which condition this may occur. I m unbale to trace it.
Thanks

Not able to disable checksum verification at master in mysql5.6.16 GTID based replication (no replies)

$
0
0
Hi ,
I m getting one error and unable to trace it.
In my master server i have disabled master-verify-checksum but still show binlog event not ignoring it..
mysql> show global variables like ‘%check%’;
+—————————+——–+
| Variable_name | Value |
+—————————+——–+
| binlog_checksum | NONE |
| foreign_key_checks | ON |
| innodb_checksum_algorithm | innodb |
| innodb_checksums | ON |
| innodb_file_format_check | ON |
| master_verify_checksum | OFF |
| slave_checkpoint_group | 512 |
| slave_checkpoint_period | 300 |
| slave_sql_verify_checksum | OFF |
| unique_checks | ON |
mysql> show binlog events in ‘mysql225-bin.000002′;
ERROR 1220 (HY000): Error when executing command SHOW BINLOG EVENTS: Wrong offset or I/O error

Monitoring slave status from master (no replies)

$
0
0
Hi, I want to do basic monitoring of the slave status by querying the master.

I've tried "show processlist" and "show slave hosts". They display the information on connected slaves, but seem to have a bit of lag to reflect a disconnected slave, one minute or so in my test. I've also seen that the "show processlist" does not list the replication processes (COMMAND=Binlog Dump), but the updates to the master are replicated to the slaves.

My question is, how reliable it is to use those command for basic monitoring and how fast will a disconnected slave be reflected to their output?

Thanks

Important: Status of master binlog dump thread is not proper it seems? (1 reply)

$
0
0
Hi,
I have one doubt. MysqlBinlog dump thread transfers the packet to slave I/O thread. In below result binlog dum thread is telling that it has sent all events to slave but in slave output you can see ,slave has not read all events. (see show master and slave status below).

My doubt is, binlog dump thread is telling it has transferred all events(fcab0e0a-9796-11e3-9f59-5254006e4bc5:1-387)and since slave I/O is stopped due to some error so it has retrieved only till fcab0e0a-9796-11e3-9f59-5254006e4bc5:1-384. so where remaining events went? is there a packet loss ?


please let me get out from this confusion, suggest me if i m wrong.

AT MASTER SERVER:
mysql> show master status;
+------------------+----------+--------------+------------------+--------------------------------------------+
| File | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |
+------------------+----------+--------------+------------------+--------------------------------------------+
| mysql-bin.000026 | 923 | sile,testdb | | fcab0e0a-9796-11e3-9f59-5254006e4bc5:1-387 |
+------------------+----------+--------------+------------------+--------------------------------------------+
1 row in set (0.00 sec)

mysql> show processlist\G;
Id: 52
User: rehana
Host: 172.20.0.225:49976
db: NULL
Command: Binlog Dump GTID
Time: 121
State: Master has sent all binlog to slave; waiting for binlog to be updated
Info: NULL

No query specified

AT SLAVE SERVER:
Last_IO_Errno: 1595
Last_IO_Error: Relay log write failure: could not queue event from master
Last_SQL_Errno: 0
Last_SQL_Error:
Replicate_Ignore_Server_Ids:
Master_Server_Id: 1
Master_UUID: fcab0e0a-9796-11e3-9f59-5254006e4bc5
Master_Info_File: mysql.slave_master_info
SQL_Delay: 0
SQL_Remaining_Delay: NULL
Slave_SQL_Running_State: Slave has read all relay log; waiting for the slave I/O thread to update it
Master_Retry_Count: 86400
Master_Bind:
Last_IO_Error_Timestamp: 140321 11:09:49
Last_SQL_Error_Timestamp:
Master_SSL_Crl:
Master_SSL_Crlpath:
Retrieved_Gtid_Set: fcab0e0a-9796-11e3-9f59-5254006e4bc5:379-384
Executed_Gtid_Set: 01372b42-a9cc-11e3-9613-525400d8d607:1-15,
fcab0e0a-9796-11e3-9f59-5254006e4bc5:1-384

Structure changes breaking replication on slave (2 replies)

$
0
0
I just set up MySQL replication on two servers (each running 5.6.16), and it seems every time I make a structure change to a table on the master DB, the slave ends up erroring out. The error on the slave is number 1677, and says:

"Column 2 of table 'jove_live.quiz_results' cannot be converted from type 'varchar(600)' to type 'varchar(200)'"

Is there a known bug with this?
Viewing all 1561 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>