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 vote

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
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Kesha Thillainayagam
Posted Apr 13, 2018 in Confluence

We want to hear how your non-technical teams are using Confluence!

Hi Community! Kesha (kay-sha) from the Confluence marketing team here! Can you share stories with us on how your non-technical (think Marketing, Sales, HR, legal, etc.) teams are using Confluen...

355 views 20 10
Join discussion

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