Bug #89131 OPTIMIZE TABLE returns unusable warning/error message
Submitted: 8 Jan 2018 11:13 Modified: 6 Nov 2020 4:50
Reporter: László Németh Email Updates:
Status: Verified Impact on me:
Category:MySQL Server: Errors Severity:S4 (Feature request)
Version:5.6.37-ndb-7.3.18 OS:CentOS (Linux version 3.10.0-693.5.2.el7.x86_64)
Assigned to: CPU Architecture:Any
Tags: ndb

[8 Jan 2018 11:13] László Németh

Responding to my question on the Cluster email-list[1] Jesper Wisborg Krogh suggested me to open this feature request.

OPTIMIZE TABLE returned a 'strange' warning/error message:

| Table                  | Op       | Msg_type | Msg_text                                      |
| databasetst.attributes | optimize | Warning  | Got error 0 'No error' from NDB               |
| databasetst.attributes | optimize | error    | Unknown - internal error 122 during operation | 


- Why any warning or error is returned at all when there was 'No error' ?
- Why an error is returned together with a 'No error' Warning ?
- 'Unknown - internal error 122 during operation' => I could not find this error number either in the Server, or in the Client error number lists.
  I expect the textual description of the error, something more reasonable, like: "Out of disk space" or "Database full".


[1] https://lists.mysql.com/cluster/8735

How to repeat:
I'm not sure how to reproduce this (see [1])
I think something like this could do:

- Setup an NDB cluster (I guess minimal configuration is enough).
- Fill a table until ~80% DataMemory is used.
[8 Jan 2018 11:15] László Németh
I found an old similar bug, though which is not the same:
[16 Jan 2018 11:25] Guga Man
Also happens with version 5.6.29-ndb-7.4.11
[6 Nov 2020 4:50] MySQL Verification Team

Thanks for the request

all best