← Back to team overview

maria-developers team mailing list archive

Re: Fix for TokuDB and parallel replication


When running the server in debug, I hit the following assert :

2016-12-09 18:12:03 140057763633920 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.001445' at position 4, relay log './sql-slave-relay-bin.000001' position: 4; GTID position '0-1-483188364' mysqld: /home/jfournier/server/sql/rpl_parallel.cc:210: void finish_event_group(rpl_parallel_thread*, uint64, rpl_parallel_entry*, rpl_group_info*): Assertion `!tmp_gco->next_gco || tmp_gco->last_sub_id > sub_id' failed.
161209 18:12:06 [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.1.19-MariaDB-debug
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 6183865 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x7f60fc016070
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 = 0x7f61e08f61b8 thread_stack 0x48400

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


Jocelyn Fournier
M : +33 6 51 21 54 10
Softizy - At your side to Optimize your PHP / MySQL applications

Le 09/12/2016 à 15:16, Kristian Nielsen a écrit :
jocelyn fournier <jocelyn.fournier@xxxxxxxxxxx> writes:

It seems the entry corresponds to a table having a trigger, don't know
if it could have an impact on the parallel replication ?
Triggers should work ok, otherwise it would be a bug.

But it's hard to tell what is going on without a way to reproduce...
I don't recall seeing before the SQL "stopping by itself". Even if parallel
replication worker threads would somehow end up killing the SQL thread
instead of a conflicting parallel transaction, I would expect something in
the log...

  - Kristian.

Follow ups