Is it safe to terminate stuck DB transactions of Confluence?

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.

1 answer

1 accepted

0 votes
Accepted answer

Hi Oleksiy,

You could specify database query timeout that will automatically terminate database queries which took longer than the specified timeout.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Dec 18, 2018 in Confluence Cloud

Happy holidays from our team to yours!

Hi Community!  2018 was filled with changes for our team, both big and small, and we've taken a lot of time to both celebrate our wins and recognize areas of improvement. One thing that we're a...

456 views 3 18
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you