tags: mariadb, mysql, database replication I have upgraded the MariaDB server with a replicated database from 10.3.12 to 10.3.29. When I started replication I got an error:
2021-06-21 07:09:32 0x7f77400ab700 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.3.29/storage/innobase/row/row0ins.cc line 221
InnoDB: Failing assertion: !cursor->index->is_committed()
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/
InnoDB: about forcing recovery.
2021-06-21 7:09:32 0 [ERROR] InnoDB: Unable to find a record to delete-mark
210621 7:09:32 [ERROR] mysqld got signal 6 ;
InnoDB: tuple This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
DATA TUPLE: 2 fields;
To report this bug, see https://mariadb.com/kb/en/reporting-bugs
0:We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
Server version: 10.3.29-MariaDB-log
SQL NULLkey_buffer_size=16777216
;read_buffer_size=2097152
max_used_connections=1
1:max_threads=502
len 4; hex thread_count=9
80It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 17505319 K bytes of memory
42Hope that's ok; if not, decrease some variables in the equation.
fdThread pointer: 0x7f54b40012a8
2dAttempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
; asc B -;;
SHOW SLAVE STATUS after restart of mysqld
*************************** 1. row ***************************
Slave_IO_State:
Master_Host: eggplant.***
Master_User: replication
Master_Port: 3306
Connect_Retry: 60
Master_Log_File: eggplant-bin.031680
Read_Master_Log_Pos: 542851065
Relay_Log_File: mysql-relay-bin.000002
Relay_Log_Pos: 306
Relay_Master_Log_File: eggplant-bin.031675
Slave_IO_Running: No
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:
Skip_Counter: 0
Exec_Master_Log_Pos: 4
Relay_Log_Space: 74965917
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:
Replicate_Ignore_Server_Ids:
Master_Server_Id: 0
Master_SSL_Crl:
Master_SSL_Crlpath:
Using_Gtid: Slave_Pos
Gtid_IO_Pos:
Replicate_Do_Domain_Ids:
Replicate_Ignore_Domain_Ids:
Parallel_Mode: conservative
SQL_Delay: 0
SQL_Remaining_Delay: NULL
Slave_SQL_Running_State:
Slave_DDL_Groups: 0
Slave_Non_Transactional_Groups: 0
Slave_Transactional_Groups: 0
1 row in set (0.000 sec)
SHOW MASTER STATUS (on replica)
+------------------+----------+--------------+------------------+
| File | Position | Binlog_Do_DB | Binlog_Ignore_DB |
+------------------+----------+--------------+------------------+
| mango-bin.000002 | 328 | | |
+------------------+----------+--------------+------------------+
I tried to set GTID or binlog file and position. I tried to change master (version 10.3.12 or cascade over 10.3.29)
But when I set log-slave-updates = 1 then replication starts without errors.
START SLAVEcommand after the MariaDB service being started or the error (or MariaDB crashed) when you start the service? - FaNo_FNmaster (10.3.12)->slave (10.3.29)I just tried another one master with version 10.3.29 with scheme:master (10.3.12)->New master (10.3.29)->Replica (10.3.29)- Dmitry Romanovlog-slave-updates = 1that makes the replication successfully start? - FaNo_FN