Bug #20442 NDB API: scans with exclusive lock and update of one record cause a deadlock
Submitted: 13 Jun 2006 21:52 Modified: 2 Feb 2007 4:07
Reporter: Anatoly Pidruchny (Candidate Quality Contributor) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: NDB API Severity:S3 (Non-critical)
Version:5.0.22-max OS:Any (all)
Assigned to: Jon Stephens CPU Architecture:Any

File: Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

[13 Jun 2006 21:54] Anatoly Pidruchny
Test program

Attachment: scan_update1_deadlock.cpp (application/octet-stream, text), 7.67 KiB.

[13 Jun 2006 21:54] Anatoly Pidruchny
Cluster configuration file

Attachment: config.ini (application/octet-stream, text), 448 bytes.

[14 Jun 2006 1:05] Anatoly Pidruchny
The test program with added NdbScanOperation::SF_OrderBy parameter in readTuples.

Attachment: scan_update1_deadlock.cpp (application/octet-stream, text), 7.69 KiB.