[MDEV-17125] InnoDB: Assertion failure in file mariadb-10.2.14/plugin/semisync/semisync_master.cc:754 Created: 2018-09-03  Updated: 2019-05-01

Status: Open
Project: MariaDB Server
Component/s: Replication
Affects Version/s: 10.2.14
Fix Version/s: 10.2

Type: Bug Priority: Major
Reporter: Juan Assignee: Andrei Elkin
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-19376 Repl_semi_sync_master::commit_trx ass... Closed
relates to MDEV-7591 master crashed when slave specfied a ... Closed

 Description   

On a master running 10.2.14 build 20620 customer sees this assertion failure switching from async to semi-sync replication at semisync_master.cc line 754

2018-09-03 20:33:56 140064990877440 [Note] Semi-sync replication switched OFF.
2018-09-03 22:33:03 140058246366976 [Note] Semi-sync replication switched ON with slave (server_id: 1) at (bin_log.000368, 4)
2018-09-03 22:33:03 140058246366976 [Note] Start semi-sync binlog_dump to slave (server_id: 1), pos(bin_log.000368, 4)
mysqld: /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.2.14/plugin/semisync/semisync_master.cc:754: int ReplSemiSyncMaster::commitTrx(const char*, my_off_t): Assertion `(thd_kill_statement_service->thd_kill_level_func(_current_thd()) == THD_ABORT_ASAP) || !active_tranxs_ || !active_tranxs_->is_tranx_end_pos(trx_wait_binlog_name, trx_wait_binlog_pos)' failed.
180903 22:35:04 [ERROR] mysqld got signal 6 ;
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.
 
To report this bug, see https://mariadb.com/kb/en/reporting-bugs
 
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.2.14-MariaDB-log
key_buffer_size=67108864
read_buffer_size=131072
max_used_connections=63
max_threads=302
thread_count=70
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 729244 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x7f61840009c8
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 = 0x7f635c3f0d80 thread_stack 0x49000
/usr/sbin/mysqld(my_print_stacktrace+0x38)[0x55e6ed5558bd]
/usr/sbin/mysqld(handle_fatal_signal+0x3d7)[0x55e6ecf890f2]
/lib64/libpthread.so.0(+0xf5e0)[0x7f6373ec15e0]
/lib64/libc.so.6(gsignal+0x37)[0x7f63723ce1f7]
/lib64/libc.so.6(abort+0x148)[0x7f63723cf8e8]
/lib64/libc.so.6(+0x2e266)[0x7f63723c7266]
/lib64/libc.so.6(+0x2e312)[0x7f63723c7312]
/var/lib/mysql/lib64/mysql/plugin/semisync_master.so(_ZN18ReplSemiSyncMaster9commitTrxEPKcy+0x785)[0x7f636e0936c1]
/var/lib/mysql/lib64/mysql/plugin/semisync_master.so(repl_semi_report_commit+0x6f)[0x7f636e094f41]
/usr/sbin/mysqld(_ZN14Trans_delegate12after_commitEP3THDb+0x10c)[0x55e6ece3cf42]
/usr/sbin/mysqld(_Z15ha_commit_transP3THDb+0x622)[0x55e6ecf8c108]
/usr/sbin/mysqld(_Z17trans_commit_stmtP3THD+0x63)[0x55e6ece49489]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x923d)[0x55e6ecd1b460]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x2bb)[0x55e6ecd1f48c]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0xedb)[0x55e6ecd0ee2d]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x54c)[0x55e6ecd0da79]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x1bd)[0x55e6ece36860]
/usr/sbin/mysqld(handle_one_connection+0x30)[0x55e6ece365c0]
/lib64/libpthread.so.0(+0x7e25)[0x7f6373eb9e25]
/lib64/libc.so.6(clone+0x6d)[0x7f637249134d]
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f618400fb10): INSERT INTO metrics_data (MetricTimestamp, MetricGroupID, MetricTypeID, TimeWindowTypeID, Value)  VALUES('2018-09-03 22:30:00',15,22,1,0)
Connection ID (thread ID): 46
Status: NOT_KILLED

The assertion looks like jira.mariadb.org/browse/MDEV-7591


Generated at Thu Feb 08 08:34:06 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.