[MDEV-14354] rpl-tokudb tests fail massively with tcmalloc Created: 2017-11-10  Updated: 2022-09-08

Status: Open
Project: MariaDB Server
Component/s: Storage Engine - TokuDB, Tests
Affects Version/s: 10.0
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-14383 tokudb_bugs. tests failed in buildbot... Closed

 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-rpm-centos73-amd64/builds/2805/steps/mtr/logs/stdio

rpl-tokudb.rpl_set_null_tokudb 'mix'     w4 [ fail ]
        Test ended at 2017-11-10 10:24:00
 
CURRENT_TEST: rpl-tokudb.rpl_set_null_tokudb
 
 
The server [mysqld.2 - pid: 14057, winpid: 14057, exit: 256] crashed while running 'check warnings'
Server log from this test:
----------SERVER LOG START-----------
171110 10:23:58 [Note] /usr/sbin/mysqld (mysqld 10.0.34-MariaDB) starting as process 14059 ...
171110 10:23:58 [Note] Plugin 'FEDERATED' is disabled.
171110 10:23:58 [Note] Plugin 'ARCHIVE' is disabled.
171110 10:23:58 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
 
171110 10:23:58 [Note] InnoDB: Using mutexes to ref count buffer pool pages
171110 10:23:58 [Note] InnoDB: The InnoDB memory heap is disabled
171110 10:23:58 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
171110 10:23:58 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
171110 10:23:58 [Note] InnoDB: Compressed tables use zlib 1.2.7
171110 10:23:58 [Note] InnoDB: Using Linux native AIO
171110 10:23:58 [Note] InnoDB: Not using CPU crc32 instructions
171110 10:23:58 [Note] InnoDB: Initializing buffer pool, size = 8.0M
171110 10:23:58 [Note] InnoDB: Completed initialization of buffer pool
171110 10:23:58 [Note] InnoDB: Highest supported file format is Barracuda.
171110 10:23:58 [Note] InnoDB: 128 rollback segment(s) are active.
171110 10:23:58 [Note] InnoDB: Waiting for purge to start
171110 10:23:58 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 1629415
171110 10:23:58 [Note] Plugin 'XTRADB_READ_VIEW' is disabled.
171110 10:23:58 [Note] Plugin 'XTRADB_INTERNAL_HASH_TABLES' is disabled.
171110 10:23:58 [Note] Plugin 'XTRADB_RSEG' is disabled.
171110 10:23:58 [Note] Plugin 'INNODB_TRX' is disabled.
171110 10:23:58 [Note] Plugin 'INNODB_LOCK_WAITS' is disabled.
171110 10:23:58 [Note] Plugin 'INNODB_CMP_RESET' is disabled.
171110 10:23:58 [Note] Plugin 'INNODB_CMPMEM' is disabled.
171110 10:23:58 [Note] Plugin 'INNODB_CMPMEM_RESET' is disabled.
171110 10:23:58 [Note] Plugin 'INNODB_CMP_PER_INDEX_RESET' is disabled.
171110 10:23:58 [Note] Plugin 'INNODB_BUFFER_PAGE' is disabled.
171110 10:23:58 [Note] Plugin 'INNODB_BUFFER_PAGE_LRU' is disabled.
171110 10:23:58 [Note] Plugin 'INNODB_BUFFER_POOL_STATS' is disabled.
171110 10:23:58 [Note] Plugin 'INNODB_METRICS' is disabled.
171110 10:23:58 [Note] Plugin 'INNODB_FT_DEFAULT_STOPWORD' is disabled.
171110 10:23:58 [Note] Plugin 'INNODB_FT_DELETED' is disabled.
171110 10:23:58 [Note] Plugin 'INNODB_FT_BEING_DELETED' is disabled.
171110 10:23:58 [Note] Plugin 'INNODB_FT_CONFIG' is disabled.
171110 10:23:58 [Note] Plugin 'INNODB_FT_INDEX_CACHE' is disabled.
171110 10:23:58 [Note] Plugin 'INNODB_FT_INDEX_TABLE' is disabled.
171110 10:23:58 [Note] Plugin 'INNODB_SYS_TABLES' is disabled.
171110 10:23:58 [Note] Plugin 'INNODB_SYS_TABLESTATS' is disabled.
171110 10:23:58 [Note] Plugin 'INNODB_SYS_INDEXES' is disabled.
171110 10:23:58 [Note] Plugin 'INNODB_SYS_COLUMNS' is disabled.
171110 10:23:58 [Note] Plugin 'INNODB_SYS_FIELDS' is disabled.
171110 10:23:58 [Note] Plugin 'INNODB_SYS_FOREIGN' is disabled.
171110 10:23:58 [Note] Plugin 'INNODB_SYS_FOREIGN_COLS' is disabled.
171110 10:23:58 [Note] Plugin 'INNODB_SYS_TABLESPACES' is disabled.
171110 10:23:58 [Note] Plugin 'INNODB_SYS_DATAFILES' is disabled.
171110 10:23:58 [Note] Plugin 'INNODB_CHANGED_PAGES' is disabled.
171110 10:23:58 [Note] Plugin 'BLACKHOLE' is disabled.
171110 10:23:58 [Note] Plugin 'FEEDBACK' is disabled.
171110 10:23:58 [Note] Plugin 'partition' is disabled.
171110 10:23:58 [Warning] /usr/sbin/mysqld: unknown variable 'loose-feedback-debug-startup-interval=20'
171110 10:23:58 [Warning] /usr/sbin/mysqld: unknown variable 'loose-feedback-debug-first-interval=60'
171110 10:23:58 [Warning] /usr/sbin/mysqld: unknown variable 'loose-feedback-debug-interval=60'
171110 10:23:58 [Warning] /usr/sbin/mysqld: unknown variable 'loose-debug-sync-timeout=300'
171110 10:23:58 [Note] Server socket created on IP: '127.0.0.1'.
171110 10:23:58 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.0.34-MariaDB'  socket: '/dev/shm/var/tmp/4/mysqld.2.sock'  port: 16061  MariaDB Server
171110 10:23:59 [Note] 'CHANGE MASTER TO executed'. Previous state master_host='', master_port='3306', master_log_file='', master_log_pos='4'. New state master_host='127.0.0.1', master_port='16060', master_log_file='master-bin.000001', master_log_pos='4'.
171110 10:23:59 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000001' at position 4, relay log './slave-relay-bin.000001' position: 4
171110 10:23:59 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16060',replication started in log 'master-bin.000001' at position 4
171110 10:23:59 [Note] Error reading relay log event: slave SQL thread was killed
171110 10:23:59 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000001' at position 313
171110 10:23:59 [Note] Slave I/O thread exiting, read up to log 'master-bin.000001', position 313
171110 10:23:59 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './slave-relay-bin.000001' position: 4
171110 10:23:59 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16060',replication started in log 'FIRST' at position 4
171110 10:23:59 [Note] Error reading relay log event: slave SQL thread was killed
171110 10:23:59 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000001' at position 1065
171110 10:24:00 [Note] Slave I/O thread exiting, read up to log 'master-bin.000001', position 1065
171110 10:24:00 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './slave-relay-bin.000001' position: 4
171110 10:24:00 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16060',replication started in log 'FIRST' at position 4
171110 10:24:00 [Note] Error reading relay log event: slave SQL thread was killed
171110 10:24:00 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000001' at position 1059
171110 10:24:00 [Note] Slave I/O thread exiting, read up to log 'master-bin.000001', position 1059
171110 10:24:00 [Note] 'CHANGE MASTER TO executed'. Previous state master_host='127.0.0.1', master_port='16060', master_log_file='master-bin.000001', master_log_pos='1059'. New state master_host='127.0.0.1', master_port='16060', master_log_file='', master_log_pos='1059'.
171110 10:24:00 [ERROR] mysqld got signal 11 ;
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.0.34-MariaDB
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=4
max_threads=153
thread_count=3
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 62794 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x0
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 = 0x0 thread_stack 0x48000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0xbd3dbe]
/usr/sbin/mysqld(handle_fatal_signal+0x3b6)[0x73d4b6]
/lib64/libpthread.so.0(+0xf370)[0x7f1e986bc370]
/lib64/libpthread.so.0(pthread_mutex_lock+0x0)[0x7f1e986b6bd0]
/usr/sbin/mysqld[0xc610b6]
/usr/sbin/mysqld[0xc619d4]
/usr/sbin/mysqld[0xc61c33]
/lib64/libpthread.so.0(+0x7bc2)[0x7f1e986b4bc2]
/lib64/libpthread.so.0(+0x7dd3)[0x7f1e986b4dd3]
/lib64/libc.so.6(clone+0x6d)[0x7f1e96f2d73d]
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.
Writing a core file
----------SERVER LOG END-------------
mysqltest failed but provided no output
The result from queries just before the failure was:
< snip >
include/rpl_reset.inc
CREATE TABLE t1 (c1 BIT, c2 INT) Engine=TokuDB;
INSERT INTO `t1` VALUES ( 1, 1 );
UPDATE t1 SET c1=NULL where c2=1;
include/diff_tables.inc [master:t1, slave:t1]
DELETE FROM t1 WHERE c2=1 LIMIT 1;
include/diff_tables.inc [master:t1, slave:t1]
DROP TABLE t1;
include/rpl_reset.inc
CREATE TABLE t1 (c1 CHAR) Engine=TokuDB;
INSERT INTO t1 ( c1 ) VALUES ( 'w' ) ;
SELECT * FROM t1;
c1
w
UPDATE t1 SET c1=NULL WHERE c1='w';
include/diff_tables.inc [master:t1, slave:t1]
DELETE FROM t1 LIMIT 2;
include/diff_tables.inc [master:t1, slave:t1]
DROP TABLE t1;
include/rpl_end.inc

Failing test(s): rpl-tokudb.rpl_set_null_tokudb rpl-tokudb.rpl_parallel_tokudb rpl-tokudb.rpl_deadlock_tokudb rpl-tokudb.rpl_tokudb_insert_id rpl-tokudb.rpl_tokudb_multi_update2 rpl-tokudb.rpl_tokudb_multi_update rpl-tokudb.rpl_tokudb_multi_update3 rpl-tokudb.rpl_truncate_3tokudb rpl-tokudb.rpl_tokudb_row_log rpl-tokudb.rpl_extra_col_slave_tokudb

http://buildbot.askmonty.org/buildbot/builders/kvm-rpm-centos73-amd64/builds/2784/steps/mtr/logs/stdio

Failing test(s): rpl-tokudb.rpl_set_null_tokudb rpl-tokudb.rpl_tokudb_mixed_ddl rpl-tokudb.rpl_parallel_tokudb rpl-tokudb.rpl_tokudb_multi_update2 rpl-tokudb.rpl_deadlock_tokudb rpl-tokudb.rpl_tokudb_insert_id rpl-tokudb.rpl_tokudb_multi_update rpl-tokudb.rpl_tokudb_multi_update3 rpl-tokudb.rpl_truncate_3tokudb rpl-tokudb.rpl_tokudb_row_log


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