| Bug #25493 | Data Node Shutdown Initiated by signal 0. Caused by error 2341 | ||
|---|---|---|---|
| Submitted: | 9 Jan 2007 13:56 | Modified: | 8 May 2007 5:02 |
| Reporter: | Thomas NULL ! | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S1 (Critical) |
| Version: | 5.0.27 | OS: | Linux (Debian) |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
| Tags: | 2341, 64bit, amd64, cluster, Debian | ||
[9 Jan 2007 13:56]
Thomas NULL !
[10 Jan 2007 1:16]
Jonas Oreland
Hi, these tracefiles look really "interesting", is this in any way reproducable? /Jonas
[10 Jan 2007 8:16]
Thomas NULL !
Hello Jonas, no sorry. I asked every body but they all are doing normal querys on the database. When I should knew the way to repreduce this error, then I will inform you. Regards Thomas
[10 Jan 2007 10:46]
Thomas NULL !
I still investigating in this issue. Unfortunately nobody can help me. Do you have any clue from the trace files? All help is appreciated. /Thomas
[10 Jan 2007 11:42]
Jonas Oreland
Hi, It looks like it's somthing related to auto-increment. Maybe it helps.... /Jonas jonas notes: It looks like a really rare combination of TUPKEY_REF and LCP start. The table used is 0 -> using auto-increment.
[8 May 2007 5:02]
Jonas Oreland
closing as duplicate of 27437
