Bug #8324 | AUTOCOMMIT=ON causes Lock wait timeout with small Cluster table | ||
---|---|---|---|
Submitted: | 4 Feb 2005 18:38 | Modified: | 14 Feb 2005 13:57 |
Reporter: | Alexander Keremidarski | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
Version: | 4.1.9-max-log | OS: | HP/UX (HP-UX B.11.23 U ia64) |
Assigned to: | Martin Skold | CPU Architecture: | Any |
[4 Feb 2005 18:38]
Alexander Keremidarski
[14 Feb 2005 13:57]
Martin Skold
This behaviour cannot be reproduced. If some transactions have been run that are not properly committed/aborted they could hold locks causing this behaviour. Please note that the default transaction timeout is very high, please lower this and verify again on a freshly started cluster. Parameter is TransactionInactiveTimeout, unit is milliseconds. If problem still occurs, please send exact configuration.