[MDEV-13719] Assertion `bit < (map)->n_bits' failed in bitmap_is_set Created: 2017-09-02  Updated: 2017-12-23  Resolved: 2017-12-23

Status: Closed
Project: MariaDB Server
Component/s: Replication
Affects Version/s: 10.2
Fix Version/s: 10.2.12

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Michael Widenius
Resolution: Fixed Votes: 0
Labels: None


 Description   

Note: The test case is for 10.3, because it was easy to make, but I suppose 10.2 should be also affected, if there are any error codes above 2000 which can be written to the binary log. ER_UNKNOWN_SEQUENCES==4088

Run with --mysqld=--slave-skip-errors=1051 or other non-empty value

--source include/master-slave.inc
 
create sequence a;
--error ER_UNKNOWN_SEQUENCES
drop sequence a, b;
 
--sync_slave_with_master
 
# Cleanup
--connection master
--source include/rpl_end.inc

10.3 016c35a7f2f4a288

mysqld: /data/src/10.3/include/my_bitmap.h:131: uint bitmap_is_set(const MY_BITMAP*, uint): Assertion `bit < (map)->n_bits' failed.
170903  1:51:49 [ERROR] mysqld got signal 6 ;
 
#7  0x00007f4e3492aee2 in __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6
#8  0x0000555642e93499 in bitmap_is_set (map=0x5556441639a0 <slave_error_mask>, bit=4088) at /data/src/10.3/include/my_bitmap.h:131
#9  0x0000555642eb51c3 in ignored_error_code (err_code=4088) at /data/src/10.3/sql/log_event.cc:441
#10 0x0000555642e9ca59 in Query_log_event::do_apply_event (this=0x7f4dcc01b400, rgi=0x7f4dcc000a90, query_arg=0x7f4dcc01b5ab "DROP SEQUENCE `a`,`b` /* generated by server */", q_len_arg=47) at /data/src/10.3/sql/log_event.cc:5082
#11 0x0000555642e9c5c3 in Query_log_event::do_apply_event (this=0x7f4dcc01b400, rgi=0x7f4dcc000a90) at /data/src/10.3/sql/log_event.cc:4968
#12 0x0000555642a04171 in Log_event::apply_event (this=0x7f4dcc01b400, rgi=0x7f4dcc000a90) at /data/src/10.3/sql/log_event.h:1473
#13 0x00005556429f8ab5 in apply_event_and_update_pos_apply (ev=0x7f4dcc01b400, thd=0x7f4dcc001550, rgi=0x7f4dcc000a90, reason=0) at /data/src/10.3/sql/slave.cc:3791
#14 0x00005556429f8f7f in apply_event_and_update_pos (ev=0x7f4dcc01b400, thd=0x7f4dcc001550, rgi=0x7f4dcc000a90) at /data/src/10.3/sql/slave.cc:3939
#15 0x00005556429f96eb in exec_relay_log_event (thd=0x7f4dcc001550, rli=0x555646f1b4a8, serial_rgi=0x7f4dcc000a90) at /data/src/10.3/sql/slave.cc:4226
#16 0x00005556429fcd28 in handle_slave_sql (arg=0x555646f197e0) at /data/src/10.3/sql/slave.cc:5373
#17 0x000055564307d1dc in pfs_spawn_thread (arg=0x7f4dd0040700) at /data/src/10.3/storage/perfschema/pfs.cc:1862
#18 0x00007f4e3686f494 in start_thread (arg=0x7f4e2c429700) at pthread_create.c:333
#19 0x00007f4e349e793f in clone () from /lib/x86_64-linux-gnu/libc.so.6

No visible effect on a non-debug build.



 Comments   
Comment by Michael Widenius [ 2017-12-23 ]

Fixed MAX_SLAVE_ERROR to cover all ranges

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