Bug #38190 Rollback behavior on NDB is not documented well enough.

• Submitted: 17 Jul 2008 0:12
• Modified: 21 Jul 2008 13:10
• Reporter: Mikiya Okuno
• Status: Closed
• Category: MySQL Server: Documentation
• Severity: S4 (Feature request)
• OS: Any
• Assigned to: Jon Stephens
• CPU Architecture: Any

[17 Jul 2008 0:12] Mikiya Okuno

Description:
While the following page describes limitations regarding to transactions on NDB, I could not figure out what users should do against rollbacks:
http://dev.mysql.com/doc/refman/5.1/en/mysql-cluster-limitations-transactions.html

The document simply says like this:
"Rollbacks.   There is no partial rollback of transactions. A duplicate key or similar error rolls back the entire transaction."

This lacks some explanations. At least we should state that subsequent statements will result in the error like below:

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

And then, we should also state that ROLLBACK command should be issued and the entire transaction should be retried from the beginning. This behavior is different from other transactional storage engines like InnoDB.

How to repeat:
n/a

Suggested fix:
see above

[21 Jul 2008 13:10] Jon Stephens

Updated as suggested by the submitter.