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

Replicating just one database, "The use of replication filters with XA transactions is not supported" error (no replies)

$
0
0
I have a master that contains a dozen or so databases, and want to replicate just one of them to another server.

I've configured both servers as per these pages in the docs:
17.1.2 Setting Up Binary Log File Position Based Replication
17.3.6 Replicating Different Databases to Different Slaves

However, I get this error in the slave's log:

2019-07-07T20:56:09.157115Z 5 [ERROR] [MY-013175] [Repl] Slave SQL for channel '': Error in Xid_log_event: Commit could not be completed, 'The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replication slave.', Error_code: MY-013175
2019-07-07T20:56:09.157130Z 5 [Warning] [MY-010584] [Repl] Slave: The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replication slave. Error_code: MY-013175
2019-07-07T20:56:09.157141Z 5 [ERROR] [MY-010586] [Repl] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'binlog.000007' position 28430722

None of my code is using "XA transactions" directly, however it seems like newer versions of InnoDB do not allow this functionality to be disabled.

I've tried both the "replicate_do_db" setting and the "replicate_wild_do_table" setting, neither of which worked properly.

How can I configure replication the way that I want - Only replicating one database?

Annoying typo in MySQL Replication documentation (no replies)

$
0
0
Was not sure where to post this but it caused me a fair amount of pain today so hopefully someone can fix it.

The instructions for enabling GTID replication without going offline https://dev.mysql.com/doc/refman/8.0/en/replication-mode-change-online-enable-gtids.html has the typo.

The very last step (9) says "On each server, add gtid-mode=ON to my.cnf."

This is wrong. gtid-mode is not a valid command. It should be gtid_mode=ON with an underscore instead of a dash.

I believe also that enforce_gtid_consistency=ON should also be added.

Group replication 8.0 change primary (no replies)

$
0
0
HELLO

we test MYSQL GROUP REPLICATION 8.0 on a single box(VM)
use port 3306、3307、3308

Group replication use primary mode
3306 is primary

we use sysbench 1 table 100w data,32 thread testing
then MGR Primary 3306 port crash and change Primary to 3307 port

then we restart 3306 and join the group

this is status
mysql> select * from performance_schema.replication_group_members;
+---------------------------+--------------------------------------+----------------+-------------+--------------+-------------+----------------+
| CHANNEL_NAME | MEMBER_ID | MEMBER_HOST | MEMBER_PORT | MEMBER_STATE | MEMBER_ROLE | MEMBER_VERSION |
+---------------------------+--------------------------------------+----------------+-------------+--------------+-------------+----------------+
| group_replication_applier | 0c523b04-9e41-11e9-b205-005056b24f36 | test1 | 3306 | RECOVERING | SECONDARY | 8.0.16 |
| group_replication_applier | 9be07697-9efe-11e9-8ab2-005056b24f36 | test1 | 3307 | ONLINE | PRIMARY | 8.0.16 |
| group_replication_applier | d1fd6698-9f06-11e9-be3b-005056b24f36 | test1 | 3308 | ONLINE | SECONDARY | 8.0.16 |
+---------------------------+--------------------------------------+----------------+-------------+--------------+-------------+----------------+

generally the 3307 is primary,it can insert data,but its got the error
mysql> insert into test values (3,'cc');
ERROR 1290 (HY000): The MySQL server is running with the --super-read-only option so it cannot execute this statement

then we check performance_schema.replication_group_member_stats
we note the COUNT_TRANSACTIONS_REMOTE_IN_APPLIER_QUEUE numbere is decrement

then we wait the COUNT_TRANSACTIONS_REMOTE_IN_APPLIER_QUEUE return to zero
the primary 3307 can insert

but why ? is this normal phenomenon ?


thx

Malformed GTID set encoding.; mysql_error: 1773 (no replies)

$
0
0
I am receiving this error from mysql 8.0.16.

However, there isn't anything about how to resolve this error. Has anyone had this error or know how to resolve it?

MySQL 8.0.17: Replication Enhancements (no replies)

MySQL 8.0.17: mysqlbinlog: support for protocol compression (no replies)

Binary Log Encryption: Encryption of Temporary Capture Files (no replies)

Error=1236 Error reading packet from server for channel 'group_replication_recovery': The slave is connecting using CHANGE MASTER TO MASTER_AUTO_POSITION = 1 (no replies)

$
0
0
When the user commit the transaction for some functions (not all), the following error appears at our application server (Tomcat),

Could not commit JDBC transaction; nested exception is java.sql.SQLException: Plugin instructed the server to rollback the current transaction.

Besides, the following error appears at 1st node of MYSQL server. We have 3 nodes of MYSQL Server, where 1st node is hot standby server, 2nd node and 3rd node are active servers

[ERROR] Error reading packet from server for channel 'group_replication_recovery': The slave is connecting using CHANGE MASTER TO MASTER_AUTO_POSITION = 1, but the master has purged binary logs containing GTIDs that the slave requires. (server_errno=1236)
[ERROR] Slave I/O for channel 'group_replication_recovery': Got fatal error 1236 from master when reading data from binary log: 'The slave is connecting using CHANGE MASTER TO MASTER_AUTO_POSITION = 1, but the master has purged binary logs containing GTIDs that the slave requires.', Error_code: 1236



1. Why not all function with commit transaction do not has problem?
2. We have found that the cause of the problem may be the binary log was deleted, but we have not deleted the binary log. As the 1st node was removed from the group owing to network issue, is that any relation on it>
3. How can we fix it and prevent at future?

Exec_Master_Log_Pos Not Updating (no replies)

$
0
0
Our DBA left without any backfill aside from me (who is not really a DBA). Yesterday I noticed that the slave has been lagging and up to today, the value of Exec_Master_Log_Post has not been updating at all. Seconds_Behind_Master has been increasing.

Reading articles online, I tried to resolve it by running the script below -

STOP SLAVE;
CHANGE MASTER TO MASTER_LOG_FILE='mysql-bin.001267',MASTER_LOG_POS=305073261;
START SLAVE;

In the online content that I have read, the Master_Log_File and Relay_Master_Log_File are the same. However you can see on my slave status that the master already has a new log file. Is there any other way to resolve this aside from doing a mysqldump?

Thank you all for your help!


*************************** 1. row ***************************
Slave_IO_State: Waiting for master to send event
Master_Host: <master ip>
Master_User: v_reply
Master_Port: 3306
Connect_Retry: 60
Master_Log_File: mysql-bin.001270
Read_Master_Log_Pos: 225827119
Relay_Log_File: V-S36-relay-log.000002
Relay_Log_Pos: 320
Relay_Master_Log_File: mysql-bin.001267
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: 305073261
Relay_Log_Space: 3492173806
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: 72250
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: 35
Master_UUID: 4c067d2f-8c8f-11e7-816c-000d3ae00c4f
Master_Info_File: S:\wamp64\bin\mysql\mysql5.7.14\data\master.info
SQL_Delay: 0
SQL_Remaining_Delay: NULL
Slave_SQL_Running_State: Reading event from the relay log
Master_Retry_Count: 86400
Master_Bind:
Last_IO_Error_Timestamp:
Last_SQL_Error_Timestamp:
Master_SSL_Crl:
Master_SSL_Crlpath:
Retrieved_Gtid_Set:
Executed_Gtid_Set:
Auto_Position: 0
Replicate_Rewrite_DB:
Channel_Name:
Master_TLS_Version:

Mysql wsrep reeplication (no replies)

$
0
0
Hi!
Where to find examples of mysql with wsrep replication.
With all the settings of my.cnf and other cnf files.(FreeBSD only)
Thank you.

[ERROR] This server will now block all updates. The server will remain blocked until contact with the majority is restored. (no replies)

$
0
0
The following error appears for group replication and the variables read_only and super_read_only has been changed to enable at this moment. As a result, databases cannot be updated and event cannot be run. How to prevent this problem appear?

[ERROR] Plugin group_replication reported: 'This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked until contact with the majority is restored. It is possible to use group_replication_force_members to force a new group membership.'

Replication problem (1 reply)

$
0
0
Hi..
I am using replication to backup many databases in one slave, but i am facing this problem:
slave status:
Slave_IO_State: Waiting for master to send event
Master_Host: 192.168.232.11
Master_User: replicador
Master_Port: 3306
Connect_Retry: 60
Master_Log_File: 2-0221-bin.000001
Read_Master_Log_Pos: 511

Master status:
File: 2-0221-bin.000001
Position: 511

I maded a reset of master and slave, they are on the same log position, but if i include some information in master database table they dont appear no slave.

What i am doing wrong?

Setting up multi-source replication (MySQL 8.0) with GTID based replication (no replies)

Urgent Replication error 13114 and error 1236 (no replies)

$
0
0
Failing to configure Replication getting that error on one node.


Last_IO_Errno: 13114
Last_IO_Error: Got fatal error 1236 from master when reading data from binary log: 'Could not find first log file name in binary log index file'

Connecting client applications to Single-Primary Group Replication set without InnoDB cluster (1 reply)

$
0
0
I have a working 3 server Single-primary Group Replication set humming away nicely. However, my website cannot connect unless I manually set the target database server to the current Primary.

How do I handle client-side fail-over with Single-primary group replication?

MySQL Router seems to only allow round-robin or first-available/next-available which is fine for multi-primary, but there’s no way to set it up to query the group to determine which server is primary in a Single-primary setup.

The only way seems to be setting an InnoDB cluster to manage server metadata, which I have no interest in doing.

Round-robin is fine for handling reads, but how do I get MySQL Router to query any member of the group to determine which is primary, without setting up an InnoDB cluster? (and the query would be different for MySQL 5.7.x vs 8.x)

I have googled everything under the sun, to no avail.

start group replication fails - /usr/sbin/mysqld: File '/home/mysql/server/data/relay_log-group_replication_applier.000036' not found (Errcode: 2 - No such file or directory) (1 reply)

$
0
0
2019-10-08T15:47:14.076730+10:00 0 [ERROR] /usr/sbin/mysqld: File '/home/mysql/server/data/relay_log-group_replication_applier.000036' not found (Errcode: 2 - No such file or directory)
2019-10-08T15:47:14.076799+10:00 0 [ERROR] Failed to open log (file '/home/mysql/server/data/relay_log-group_replication_applier.000036', errno 2)
2019-10-08T15:47:14.076815+10:00 0 [ERROR] Could not open log file
2019-10-08T15:47:14.076857+10:00 0 [ERROR] /usr/sbin/mysqld: File '/home/mysql/server/data/relay_log-group_replication_applier.000035' not found (Errcode: 2 - No such file or directory)
2019-10-08T15:47:14.076871+10:00 0 [ERROR] Failed to open log (file '/home/mysql/server/data/relay_log-group_replication_applier.000035', errno 2)
2019-10-08T15:47:14.076882+10:00 0 [ERROR] Could not open log file

How to fix this?

MySQL 8.0.18 Replication Enhancements (no replies)

MySQL Replication with restricted privileges (no replies)

Support for TLS 1.3 in Group Replication (no replies)

Replication Issue - Slave (Duplicate Entry) (1 reply)

$
0
0
We are running master slave replication on mysql 5.7 it was running fine from last 1 year but now we are facing issue and found some serious data syncing issue. I found some serious data difference in one of our main table and mysqld.log is showing following errors repetitively:

2019-10-18T14:31:46.343746Z 606179825 [Note] Slave SQL for channel '': Could not execute Update_rows event on table so.sns_cods_logs; Duplicate
entry '7108207-4129' for key 'index_unique', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log master_bin.000581, end_log_pos 5593918
83, Error_code: 1062

2019-10-18T14:31:46.871730Z 606179825 [Note] Slave SQL for channel '': Could not execute Update_rows event on table so.sns_cods_logs; Duplicate
entry '7108207-4126' for key 'index_unique', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log master_bin.000581, end_log_pos 5596572
30, Error_code: 1062

My replication settings are as follow:

server-id = 236
slave-skip-errors = 1062,1032,1146,1539,1022
innodb_flush_log_at_trx_commit = 2

I have performed a test on master server and manually update a row then find the row on slave side but once I again update the same row I didn't find and see above errors in mysqld.log file. What
Viewing all 1561 articles
Browse latest View live


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