| Bug #44286 | Ndbd crashes after update query | ||
|---|---|---|---|
| Submitted: | 15 Apr 12:38 | Modified: | 23 Apr 16:02 |
| Reporter: | Laurent Bigonville | ||
| Status: | Open | ||
| Category: | Server: Cluster | Severity: | S3 (Non-critical) |
| Version: | mysql-5.1-telco-6.3 | OS: | Linux (Centos 5.3) |
| Assigned to: | Gustaf Thorslund | Target Version: | |
| Tags: | crash, mysql-5.1-telco-6.3.20 | ||
| Triage: | Triaged: D3 (Medium) / R6 (Needs Assessment) / E6 (Needs Assessment) | ||
[15 Apr 12:38]
Laurent Bigonville
[15 Apr 12:38]
Laurent Bigonville
ndb logs
Attachment: ndb_error_report_20090415103852.tar.bz2 (application/x-bzip, text), 426.22 KiB.
[23 Apr 15:12]
Jonathan Miller
Easy workaround is to batch the updates using "where" clause on a PK.
[23 Apr 15:16]
Jonathan Miller
Shows to be due to a GCP Stop. Need to know about schema, was it using disk data Might be duplicate of: http://bugs.mysql.com/bug.php?id=37227 http://bugs.mysql.com/bug.php?id=39498 http://bugs.mysql.com/bug.php?id=43882
[23 Apr 16:01]
Laurent Bigonville
mysql> describe channel_2004;
+-------------+------------------+------+-----+-------------------+-----------------------------+
| Field | Type | Null | Key | Default | Extra
|
+-------------+------------------+------+-----+-------------------+-----------------------------+
| TS | int(11) unsigned | NO | PRI | 0 |
|
| Frame | int(6) unsigned | NO | PRI | 0 |
|
| Interval | int(6) unsigned | NO | | 0 |
|
| Modemid | int(11) unsigned | NO | MUL | 0 |
|
| FirstFrame | int(6) unsigned | NO | | 0 |
|
| Timeslot | int(4) unsigned | NO | | 0 |
|
| Kind | int(1) unsigned | NO | MUL | 0 |
|
| Msgtype | int(1) unsigned | NO | | 0 |
|
| Msn | int(2) unsigned | NO | | 0 |
|
| Deleted | int(1) unsigned | NO | | 0 |
|
| Lastupdated | timestamp | NO | | CURRENT_TIMESTAMP | on update
CURRENT_TIMESTAMP |
+-------------+------------------+------+-----+-------------------+-----------------------------+
[23 Apr 16:02]
Laurent Bigonville
The table was in memory not in disk tablespace
