Bug #55199 Change error message to be more specific to the lack of execution threads

• Submitted: 12 Jul 2010 23:12
• Modified: 12 Jul 2010 23:13
• Reporter: Jonathon Coombes
• Status: Verified
• Category: MySQL Cluster: Cluster (NDB) storage engine
• Severity: S4 (Feature request)
• Version: mysql-5.1-telco-7.0
• OS: Any
• Assigned to: Assigned Account
• CPU Architecture: Any
• Tags: cluster, errorm 5.1.35-ndb-7.0.7, ndb

[12 Jul 2010 23:12] Jonathon Coombes

Description:
The following error is rather unhelpful as to the real issue:

ERROR 1296 (HY000): Got error 4350 'Transaction already aborted' from NDBCLUSTER

This feature request is to consider turning this error message into something that's not-so-cryptic, that the real problem was we ran out of threads to execute the change in. 

A suggested error message would say something like:

"NDBCluster configured with a maximum of (x) concurrent threads but it needed (y) threads to complete this transaction successfully. Transaction aborted."
 

How to repeat:
N/A

Suggested fix:
A suggested error message would say something like:

"NDBCluster configured with a maximum of (x) concurrent threads but it needed (y) threads to complete this transaction successfully. Transaction aborted."

[25 Oct 2010 6:52] Kevin Benton

This also happens during an update as follows:

Error Code: 1296
Got error -1 'Unknown error code' from NDBCLUSTER