MySQL Multi-Source Replica с GTID включена в невозможном состоянии при вращающихся журналах реле ⇐ MySql

[Anonymous]

Mysql Multi-Sryce Replica Server restars довольно часто в полночь из-за того, что не нашел файлы журнала ретрансляции. Это также останавливает каналы репликации, и их нужно сбросить, чтобы запустить их снова. Кто -нибудь также столкнулся с этой проблемой? Это ошибка или я что -то неправильно настроил на сервере реплик?

Код: Выделить всё

mysql  Ver 8.0.34 for Linux on x86_64 (MySQL Community Server - GPL)
< /code>
Конфигурация реплики: < /p>
[mysqld]
server-id = 102
replicate-ignore-table = 
replicate-ignore-table = 
...

relay_log = /var/lib/mysql/relaylog/mysql-relay-bin.log
relay_log_index = /var/lib/mysql/relaylog/mysql-relay-bin.log.index

gtid_mode = ON
enforce_gtid_consistency = ON

innodb_io_capacity = 400
open_files_limit = 65535
replica_parallel_workers = 6

innodb_lock_wait_timeout = 1800
replica_transaction_retries = 25

replicate_do_db = 
replicate_do_db = 
...
< /code>
Журнал ошибок: < /p>
2025-02-17T22:01:24.953772Z 0 [ERROR] [MY-010544] [Repl] Failed to open the relay log '/var/lib/mysql/relaylog/mysql-relay-bin.000001' (relay_log_pos 4).
2025-02-17T22:01:24.953853Z 0 [ERROR] [MY-011059] [Repl] Could not find target log file mentioned in applier metadata in the index file '/var/lib/mysql/relaylog/mysql-relay-bin.log' during relay log initialization.
2025-02-17T22:01:24.957128Z 0 [ERROR] [MY-010426] [Repl] Replica: Failed to initialize the connection metadata structure for channel ''; its record may still be present in the applier metadata repository, consider deleting it.
2025-02-17T22:01:24.983553Z 0 [ERROR] [MY-010544] [Repl] Failed to open the relay log '/var/lib/mysql/relaylog/[email protected]' (relay_log_pos 946251129).
2025-02-17T22:01:24.983598Z 0 [ERROR] [MY-011059] [Repl] Could not find target log file mentioned in applier metadata in the index file '/var/lib/mysql/relaylog/mysql-relay-bin.log-server@002d1' during relay log initialization.
2025-02-17T22:01:24.986798Z 0 [ERROR] [MY-010426] [Repl] Replica: Failed to initialize the connection metadata structure for channel 'server-1'; its record may still be present in the applier metadata repository, consider deleting it.
2025-02-17T22:01:25.028376Z 0 [ERROR] [MY-013129] [Server] A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-000029 - File '/var/lib/mysql/relaylog/t.004216' not found (OS errno 2 - No such file or directory)
2025-02-17T22:01:25.028454Z 0 [ERROR] [MY-010958] [Server] Could not open log file.
2025-02-17T22:01:30.884004Z 0 [ERROR] [MY-013129] [Server] A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-000029 - File '/var/lib/mysql/relaylog/t.004216' not found (OS errno 2 - No such file or directory)
2025-02-17T22:01:30.884077Z 0 [ERROR] [MY-010958] [Server] Could not open log file.
2025-02-17T22:01:30.906268Z 0 [ERROR] [MY-010544] [Repl] Failed to open the relay log '/var/lib/mysql/relaylog/[email protected]' (relay_log_pos 965962550).
2025-02-17T22:01:30.906404Z 0 [ERROR] [MY-011059] [Repl] Could not find target log file mentioned in applier metadata in the index file '/var/lib/mysql/relaylog/mysql-relay-bin.log-server@002d3' during relay log initialization.
2025-02-17T22:01:30.909806Z 0 [ERROR] [MY-010426] [Repl] Replica: Failed to initialize the connection metadata structure for channel 'server-3'; its record may still be present in the applier metadata repository, consider deleting it.
2025-02-17T22:01:30.999787Z 5 [Warning] [MY-010897] [Repl] Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.
2025-02-17T22:01:31.013205Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /var/run/mysqld/mysqlx.sock
2025-02-17T22:01:31.013758Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.34'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server - GPL.
2025-02-17T22:01:31.045649Z 8 [System] [MY-014002] [Repl] Replica receiver thread for channel 'server-5': connected to source '[email protected]:3306' with server_uuid=, server_id=1.  Starting GTID-based replication.
2025-02-17T22:01:31.047363Z 7 [System] [MY-014002] [Repl] Replica receiver thread for channel 'server-4': connected to source '[email protected]:3306' with server_uuid=, server_id=5. Starting GTID-based replication.
2025-02-17T22:01:31.049831Z 5 [System] [MY-014002] [Repl] Replica receiver thread for channel 'server-1': connected to source '[email protected]:3306' with server_uuid=, server_id=2. Starting GTID-based replication.
2025-02-17T22:01:31.232349Z 9 [ERROR] [MY-010827] [Server] While rebuilding index file /var/lib/mysql/relaylog/mysql-relay-bin.log-server@002d4: Failed to rename the new index file to the existing index file.
2025-02-17T22:01:31.232479Z 9 [ERROR] [MY-011072] [Server] Binary logging not possible. Message: MySQL server failed to update the binlog.index file's content properly. It might not be in sync with available binlogs and the binlog.index file state is in unrecoverable state. Aborting the server..
2025-02-17T22:01:31Z UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
BuildID[sha1]=0c3c002f0976faf5fa26716e8426fb82503a5ff5
Thread pointer: 0x76f7416045e0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 76f75c1262c8 thread_stack 0x100000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x585e70149cc1]
/usr/sbin/mysqld(print_fatal_signal(int)+0x393) [0x585e6efc3483]
/usr/sbin/mysqld(my_server_abort()+0x76) [0x585e6efc35c6]
/usr/sbin/mysqld(my_abort()+0xe) [0x585e70143c8e]
/usr/sbin/mysqld(+0x201da9f) [0x585e6fd32a9f]
/usr/sbin/mysqld(MYSQL_BIN_LOG::move_crash_safe_index_file_to_index_file(bool)+0x609) [0x585e6fd353e9]
/usr/sbin/mysqld(MYSQL_BIN_LOG::remove_logs_from_index(LOG_INFO*, bool)+0x76) [0x585e6fd39326]
/usr/sbin/mysqld(MYSQL_BIN_LOG::purge_logs(char const*, bool, bool, bool, unsigned long long*, bool)+0x505) [0x585e6fd4efc5]
/usr/sbin/mysqld(Rpl_applier_reader::purge_applied_logs()+0x292) [0x585e6fe3b0b2]
/usr/sbin/mysqld(Rpl_applier_reader::move_to_next_log()+0x2db) [0x585e6fe3c6ab]
/usr/sbin/mysqld(Rpl_applier_reader::read_next_event()+0x747) [0x585e6fe3ce57]
/usr/sbin/mysqld(handle_slave_sql+0x2ad2) [0x585e6fe27d22]
/usr/sbin/mysqld(+0x2bf27cd) [0x585e709077cd]
/lib/x86_64-linux-gnu/libc.so.6(+0x94ac3) [0x76f78b7adac3]
/lib/x86_64-linux-gnu/libc.so.6(+0x126850) [0x76f78b83f850]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 9
Status: NOT_KILLED

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

Я обнаружил несколько аналогичных ошибок, представленных здесь и здесь, но они отмечены как решаемые в предыдущих версиях.

Подробнее здесь: https://stackoverflow.com/questions/794 ... en-rotatin