Tag Info

New answers tagged

0

BlogArticleGetBlogArticlesByFiltersWithPagingCount selects from ContentPages three times, and from Versions in the middle query. VersionInsert ran first, though, and for some reason already has a lock on ContentPages - it's impossible to tell if that's code from the procedure but that you haven't shown, code from a trigger somewhere, or code called from ...


1

The deadlock happens of course because one process is reading Versions table (to add rows into @taggedBlogs) and other is inserting new rows into it. You can figure out from the details if the deadlock happens in the table itself or in index. Normal things I do when trying to reduce deadlocks is to check both of the processes if the amount of pages they ...


0

SHOW CREATE TABLE E_CUST; I'm guessing that R_CUST is a VIEW, and the underlying E_CUST does not have a good INDEX for the UPDATE. Keep in mind that VIEWs do not optimize well. I would guess from the number of locks, that M_ID is not indexed.


2

In short: SHOW INNODB STATUS will give you the last detected deadlock. use SHOW ENGINE INNODB STATUS for MySQL 5.x Line 1 gives the time when the deadlock happened. If your application code catches and logs deadlock errors,which it should, then you can match this timestamp with the timestamps of deadlock errors in application log. You would have the ...


1

What does it cost your stakeholders ? What will it cost to "fix" ? Deadlocks will happen. We design as much as possible to eliminate them. A timeout is not quite the same thing, as we may need to perform some maintenance that will involve an extended lock. The impact will depend upon the type of transaction. Batch processes and asynchronous processes ...


0

Yes Deadlock is a serious problem and it should be dealt accordingly as Deadlocks are sometimes called a deadly embrace. Deadlocks can kill an application’s performance. Users will complain about the app being slow or broken. Developers will ask the DBA to fix the problem, DBAs will push the problem back on developers. Count cannot tell you the impact, ...


15

It's typically not the count of deadlocks that can cause a serious problem, but the reason to investigate would be to find out what workloads are deadlocking on each other. After all, in a deadlock there is a victim. So now you have a process that didn't complete the work that it intended to complete. And, in good theory applications should have some sort ...


2

Deadlock is quite a heavy operation from performance point of view because it takes some time to figure out that there is a deadlock, choose which one to kill, roll back all the changes it has made -- and most likely then try to do the operation again. Also the end users might get frustrated especially if they get error messages they don't understand or have ...


2

This is not a deadlock. One transaction will simply block -- waiting to acquire the lock. The other transaction will proceed. As soon as the other transaction is done -- either by commit or rollback, the first transaction will proceed. A deadlock happens when a transaction has acquired a lock on object A, and attempts to acquire a lock on object B at the ...



Top 50 recent answers are included