http://gyazo.com/6e3b2f39362a1b4378a9d5b86d8f208a
Was deleting two spam comments and both errored out. One comment got deleted, one didn't.
The deadlock happens in a write intensive environment. I ended up not using views_content_cache due to those issues (and some other issues) if I recall correctly.
Comments
Comment #1
nnewton commentedYa, I'm going to have to open an issue with the module. It really isn't setup correctly at all. It is a nice module, but close to not usable in high performance environments because of this, which is somewhat amusing considering its purpose.
Comment #2
hefox commentedThe issue in views content cache has been patched and a new alpha release pushed.
On the codebase I was using it for, I through it out and did my own caching using wildcard clearing. e.g. cache for view blogs with cid blog_xx, update a blog call cache_clear_all('blog_*', 'cache_views_data', TRUE). If simple enough clearing roles, works nicely.
Comment #3
tvn commentedThe latest alpha3 release is on D.o now, but it didn't help with the massive deadlocks a few days ago. Tagging and bumping priority, we still need to do something about this module.
Comment #4
jonathan1055 commentedComment #5
tvn commentedIt seems we had no troubles with this one lately. Is this still an issue? Should be downgrade priority / postpone it?
Comment #6
tvn commentedThere were no problems with this recently. Query killer might be mitigating this though. Untagging from immediate D7 upgrade follow ups. Infrastructure team will deal with this if/when the problem appears again.
Comment #8
sebaz commentedIt looks like the problem is still happening on sites with this module: views_content_cache
Comment #9
drummThis hasn’t been a problem lately.