innodb-track-changed-pages=TRUE crashes XtraDB when new log files have to be created

Bug #1359182 reported by Alexey Kopytov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Invalid
Undecided
Unassigned
5.1
Invalid
Undecided
Unassigned
5.5
Triaged
Low
Unassigned
5.6
Invalid
Undecided
Unassigned

Bug Description

XtraDB crashes with changed pages tracking enabled if new log files have to be created. For some reasons this only occurs in Jenkins on CentOS 6 32-bit slaves and only PS 5.5 (tested on 5.5.38-35.2).

Error log:
---
140820 5:54:28 InnoDB: The InnoDB memory heap is disabled
140820 5:54:28 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140820 5:54:28 InnoDB: Compressed tables use zlib 1.2.3
140820 5:54:28 InnoDB: Using Linux native AIO
140820 5:54:28 InnoDB: Initializing buffer pool, size = 128.0M
140820 5:54:28 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
140820 5:54:28 InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
140820 5:54:28 InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 48 MB
InnoDB: Database physically writes the file full: wait...
140820 5:54:29 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 48 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: starting tracking changed pages from LSN 8204
09:54:29 UTC - mysqld got signal 11 ;
...
---

gdb backtrace:
---
(gdb) bt
#0 log_close ()
    at /home/jenkins/workspace/percona-server-5.5-binaries-opt-yassl/label_exp/centos5-32/percona-server-5.5.38-35.2/storage/innobase/log/log0log.c:627
#1 0x08611a07 in mtr_log_reserve_and_write (mtr=0xbfffbb84)
    at /home/jenkins/workspace/percona-server-5.5-binaries-opt-yassl/label_exp/centos5-32/percona-server-5.5.38-35.2/storage/innobase/mtr/mtr0mtr.c:255
#2 mtr_commit (mtr=0xbfffbb84)
    at /home/jenkins/workspace/percona-server-5.5-binaries-opt-yassl/label_exp/centos5-32/percona-server-5.5.38-35.2/storage/innobase/mtr/mtr0mtr.c:302
#3 0x0852ebc3 in innobase_start_or_create_for_mysql ()
    at /home/jenkins/workspace/percona-server-5.5-binaries-opt-yassl/label_exp/centos5-32/percona-server-5.5.38-35.2/storage/innobase/srv/srv0start.c:1840
#4 0x084e6de9 in innobase_init (p=0x8b52b48)
    at /home/jenkins/workspace/percona-server-5.5-binaries-opt-yassl/label_exp/centos5-32/percona-server-5.5.38-35.2/storage/innobase/handler/ha_innodb.cc:3238
#5 0x082fca6e in ha_initialize_handlerton (plugin=0x8b4fcd0)
    at /home/jenkins/workspace/percona-server-5.5-binaries-opt-yassl/label_exp/centos5-32/percona-server-5.5.38-35.2/sql/handler.cc:577
#6 0x081c58f7 in plugin_initialize (plugin=0x8b4fcd0)
    at /home/jenkins/workspace/percona-server-5.5-binaries-opt-yassl/label_exp/centos5-32/percona-server-5.5.38-35.2/sql/sql_plugin.cc:1100
#7 0x081c9c8c in plugin_init (argc=0x8af0f5c, argv=0x8b1d258, flags=<value optimized out>)
    at /home/jenkins/workspace/percona-server-5.5-binaries-opt-yassl/label_exp/centos5-32/percona-server-5.5.38-35.2/sql/sql_plugin.cc:1386
#8 0x0812dec7 in init_server_components ()
    at /home/jenkins/workspace/percona-server-5.5-binaries-opt-yassl/label_exp/centos5-32/percona-server-5.5.38-35.2/sql/mysqld.cc:4022
#9 0x0812f2f5 in mysqld_main (argc=16, argv=0x8b1d258)
    at /home/jenkins/workspace/percona-server-5.5-binaries-opt-yassl/label_exp/centos5-32/percona-server-5.5.38-35.2/sql/mysqld.cc:4757
#10 0x08123c62 in main (argc=0, argv=0x0)
    at /home/jenkins/workspace/percona-server-5.5-binaries-opt-yassl/label_exp/centos5-32/percona-server-5.5.38-35.2/sql/main.cc:25
---

Tags: bitmap
tags: added: bitmap
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

Do you have a link to the full Jenkins log? This somewhat reminds, but probably is not a duplicate, of bug 1244573

Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3176

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.