MySQL Bugs: #60669: optimize a big ndb table take so much time ,tree days is not finished

Bug #60669	optimize a big ndb table take so much time ,tree days is not finished
Submitted:	28 Mar 2011 1:52	Modified:	23 Nov 2017 20:34
Reporter:	zhang xiuyun	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Cluster: Disk Data	Severity:	S3 (Non-critical)
Version:	mysql-5.1.51 ndb-7.1.10	OS:	Linux (CentOS release 5.5 64bit)
Assigned to:		CPU Architecture:	Any
Tags:	optimize a big ndb table takes so much time, tree days is not finished

Description:
   I use optimize table command to optimize the table after REORGANIZE PARTITION,but it takes me tree days to optimize a big ndb table and now it still not finish.I don't know what's happent ,I ask question on the cluster forum,they tell me to report a bug here .
   There are 1619411 recorders in that table ,the table's size is 1.9G,there are 6 nodes in my ndb cluster ,It contains one mgm node ,one SQL node and 4 ndb nodes ,so could you tell me what lead to optimize table so slowly ?

  I don't know how to put up my log file and config file as a attachment here .if you want any file please tell me .thank you ,my email account is jimo291@gmail.com

How to repeat:
optimize a big ndb table after you use 
ALTER ONLINE TABLE table_name REORGANIZE PARTITION

optimize a big ndb table take so much time

Attachment: ndb_error_report_20110328012409.tar.bz2 (application/octet-stream, text), 398.38 KiB.

the table's description is :
mysql> DESC gps_areaalertreport;
+------------------------+--------------+------+-----+---------+-------+
| Field                  | Type         | Null | Key | Default | Extra |
+------------------------+--------------+------+-----+---------+-------+
| RecordID               | char(36)     | NO   | PRI | NULL    |       |
| VehicleCode            | char(36)     | NO   | MUL | NULL    |       |
| GPSCode                | varchar(20)  | YES  | MUL | NULL    |       |
| Longitude              | decimal(8,5) | NO   |     | NULL    |       |
| Latitude               | decimal(8,5) | NO   |     | NULL    |       |
| VehiclePosition        | varchar(100) | YES  |     | NULL    |       |
| GPSReporttime          | datetime     | YES  | MUL | NULL    |       |
| ReceiveMobileList      | varchar(200) | YES  |     | NULL    |       |
| ReceiveUserList        | varchar(200) | YES  |     | NULL    |       |
| MobileReceiveBeginTime | bigint(20)   | YES  |     | NULL    |       |
| MobileReceiveEndTime   | bigint(20)   | YES  |     | NULL    |       |
| UserReceiveBeginTime   | bigint(20)   | YES  |     | NULL    |       |
| UserReceiveEndTime     | bigint(20)   | YES  |     | NULL    |       |
| TenantCode             | varchar(20)  | NO   |     | NULL    |       |
| AreaID                 | char(36)     | YES  | MUL | NULL    |       |
| StayTime               | bigint(20)   | YES  |     | NULL    |       |
| IsInArea               | tinyint(1)   | YES  |     | NULL    |       |
| InAreaID               | char(36)     | YES  | MUL | NULL    |       |
| DelayDuration          | bigint(20)   | YES  |     | NULL    |       |
| IsDelayStay            | tinyint(1)   | YES  |     | NULL    |       |
+------------------------+--------------+------+-----+---------+-------+

Thank you for the bug report. Please try major release version than 5.1 which is EOL.

https://www.mysql.com/support/eol-notice.html