Bug #40479 | deleting rows from disk-based cluster after altering table crashes data node | ||
---|---|---|---|
Submitted: | 3 Nov 2008 16:26 | Modified: | 3 Nov 2008 20:09 |
Reporter: | Monty Taylor | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Cluster: Disk Data | Severity: | S2 (Serious) |
Version: | mysql-5.1-telco-6.3 | OS: | Linux |
Assigned to: | CPU Architecture: | Any | |
Tags: | 6.3.16, mysql-5.1-telco-6.3 |
[3 Nov 2008 16:26]
Monty Taylor
[3 Nov 2008 20:09]
Jonathan Miller
I will attach a script to reproduce this. I have not taken the time to break it down any from the attached script. Time: Friday 31 October 2008 - 22:18:05 Status: Temporary error, restart node Message: System error, node killed during node restart by other node (Internal error, programming error or missing error message, please report a bug) Error: 2303 Error data: Node 2 killed this node because GCP stop was detected Error object: NDBCNTR (Line: 249) 0x00000002 Program: /data0/cr_autotest/libexec/ndbd Pid: 20321 Trace: ./ndb_2_trace.log.1 Version: mysql-5.1.29 ndb-6.3.19-RC ***EOM***
[3 Nov 2008 20:13]
Jonathan Miller
Reproduction shell scipt
Attachment: test_paggo.sh (application/x-shellscript, text), 778 bytes.