You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@diosmosis I don't 100% remember anymore why the ArchivingStatus lock was needed?
However, I see we often get heaps of lock timeouts. And these locks often take a considerable amount of load on our DB servers. Eg
Often even more than any other query. Often causing a lot of lock wait timeout, and potentially even deadlocks.
Should this lock really still be needed (looked at code again and wasn't sure where it was actually used).
Maybe in ArchivingDbAdapter it could be a start to not reexpire the lock on every DB query but maybe every 10 minutes or 30 minutes considering the lock is valid for up to 7200s by default?
The text was updated successfully, but these errors were encountered:
@diosmosis I don't 100% remember anymore why the ArchivingStatus lock was needed?
However, I see we often get heaps of lock timeouts. And these locks often take a considerable amount of load on our DB servers. Eg
Often even more than any other query. Often causing a lot of lock wait timeout, and potentially even deadlocks.
Should this lock really still be needed (looked at code again and wasn't sure where it was actually used).
Maybe in
ArchivingDbAdapter
it could be a start to not reexpire the lock on every DB query but maybe every 10 minutes or 30 minutes considering the lock is valid for up to 7200s by default?The text was updated successfully, but these errors were encountered: