| Bug #15240 | NDBD is aborted in MySQL Cluster | ||
|---|---|---|---|
| Submitted: | 25 Nov 2005 2:35 | Modified: | 14 Dec 2005 16:48 |
| Reporter: | mantani shigeki | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S1 (Critical) |
| Version: | 5.0.15-0 | OS: | Linux (Red Hat Linux 4 AS EM64T) |
| Assigned to: | Jonas Oreland | CPU Architecture: | Any |
[14 Dec 2005 10:12]
Jonas Oreland
same bug as #15682
[14 Dec 2005 13:24]
Jonas Oreland
Pushed into 5.0.18
[14 Dec 2005 16:48]
Jon Stephens
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.
If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information
about accessing the source trees is available at
http://www.mysql.com/doc/en/Installing_source_tree.html
Additional info:
Documented in 5.0.18 changelog. Closed.
Description: [Verification environment] - Server: Dell PowerEdge 1800 (2CPU, DRAM:1GB) - Disk: 80GB (Internal disk drive ) - OS: RedHatLinux AS4.0 - DBMS: MySQL5.0.15 - Application: Several SQL statements used in the system. - Data: 10,000 records in the each tables MGM, NDBD, SQLNODE and Client are in the same machine. [Installed packages] MySQL-Max-5.0.15-0.glibc23.x86_64.rpm MySQL-client-5.0.15-0.glibc23.x86_64.rpm MySQL-devel-5.0.15-0.glibc23.x86_64.rpm MySQL-ndb-extra-5.0.15-0.glibc23.x86_64.rpm MySQL-ndb-management-5.0.15-0.glibc23.x86_64.rpm MySQL-ndb-storage-5.0.15-0.glibc23.x86_64.rpm MySQL-ndb-tools-5.0.15-0.glibc23.x86_64.rpm MySQL-server-5.0.15-0.glibc23.x86_64.rpm MySQL-shared-5.0.15-0.glibc23.x86_64.rpm [Configuration] - my.cnf - config.ini Please refer to the attached file. [DB data] Four tables were used. - CONTRACT_INFO - GLOBAL_EXTENSION - GLOBAL_NUMBER - SESSION_TABLE How to repeat: Please create the database from 4tables.sql, and issue the UPDATE using "WHERE" phrase which specifies "contract_id" column like this UPDATE GLOBAL_EXTENSION SET busy_info = 1 WHERE contract_id = '6000';