What is the best way to deal with too long database transactions in Confluence?
Periodically we have situations when some page/attachment updates fail and DB locks stay for an hours held by additional background threads. Is 15 minutes enough for average Confluence query to its own DB? Is it good practice to terminate longer transactions forcibly?
This way we release DB locks and close waste threads that sometimes overconsume CPU resources.
Hi Oleksiy,
You could specify database query timeout that will automatically terminate database queries which took longer than the specified timeout.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.