How the bug appears: an editor opens several browser windows to enter several nodes at the same time. Then, he saves them and quickly translates. Means, we have several saving processes at the same time.
Expected result: nodes will be saved within several seconds, the worst, minutes.
Real result: after saving about 5 bi-lingual nodes, nobody(!) can access site for about 30 (!) minutes.
Details: the site is big; over 50,000 nodes, each on 2 languages. Cache is set for 3 hours maximum age.
I suspect the cache component but not exactly sure.
Comments
Comment #2
k3n CreditAttribution: k3n commentedComment #3
k3n CreditAttribution: k3n commentedComment #4
cilefen CreditAttribution: cilefen commentedIs there a non-database cache backend on this site?
Comment #5
Wim LeersComment #14
cilefen CreditAttribution: cilefen commentedThere have been no comments in a few years.