Bug #16550 | Cluster Replication: rpl_create_database.test cause core on slave MySQLD | ||
---|---|---|---|
Submitted: | 16 Jan 2006 22:09 | Modified: | 17 Jan 2006 8:39 |
Reporter: | Jonathan Miller | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S1 (Critical) |
Version: | 5.1.6-alpha | OS: | Linux (Linux) |
Assigned to: | Tomas Ulin | CPU Architecture: | Any |
[16 Jan 2006 22:09]
Jonathan Miller
[17 Jan 2006 6:46]
Tomas Ulin
can't repeat this by running the test standalone
[17 Jan 2006 7:03]
Tomas Ulin
also cannot repeat when run the whole rpl test suite
[17 Jan 2006 8:39]
Tomas Ulin
I've run all rpl tests with ndb storage engine Failed 60/122 tests, 50.81% were successful. many seem to be just order problem in result set in debug mode I get 2 slave cores - one is a known bug with "create table like", which only will be detected in debug mode - the other is a safe_mutex_lock in process alarm which seems unrelated to replication #10 0x40239e60 in abort () from /lib/libc.so.6 #11 0x08674913 in safe_mutex_lock (mp=0x88e7aa0, file=0x87b9700 "thr_alarm.c", line=298) at thr_mutex.c:104 #12 0x0867182a in process_alarm (sig=14) at thr_alarm.c:298 #13 0x40040d69 in __pthread_clock_settime () from /lib/libpthread.so.0 #14 <signal handler called> #15 0x40238d8f in sigsuspend () from /lib/libc.so.6 #16 0x4003e8fa in sigwait () from /lib/libpthread.so.0 marking as can't repeat
[17 Jan 2006 9:12]
Tomas Ulin
also could not make out anything from the core other that that a commit on a transaction is attempted on the slave, although the ndb handler has no recollaction of an ongoing transaction