Bug #30661 | Purging data can cause deadlocks | ||
---|---|---|---|
Submitted: | 28 Aug 2007 2:05 | Modified: | 28 Aug 2007 16:06 |
Reporter: | Bill Weber | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Enterprise Monitor: Server | Severity: | S2 (Serious) |
Version: | 1.2.0.7296 | OS: | Any |
Assigned to: | Sloan Childers | CPU Architecture: | Any |
[28 Aug 2007 2:05]
Bill Weber
[28 Aug 2007 16:06]
Bill Weber
Nothing to see here, move along...the "retry" mechanism we built into DC writing took care of this, we just logged the first failure attempt. Deadlocking w/ InnoDB in a highly-concurrent system is a fact of life, Merlin-1.2 deals with it now, at least for DC writes (1.1 did not). The error message was confusing, as it was inserted the 1000-line "SHOW INNODB STATUS" in between two components, so I went ahead and changed that. The message will now look like this while retrying: "Encountered deadlock, Retrying n time (or times as appropriate, it's dynamic). Exception was: [innodb gobbledy gook here]" _If_ the transaction ultimately fails, you'll get the following in the logs: ""Encountered deadlock, retried transaction n time (or times as appropriate). Giving up. Exception was: [innodb gobbledy gook here]"