Database locks

[David]

Hello,

we have a problem with JIRA and DB.

We are using JIRA version 8.12.3 and DB Postgresql 9.4.

So once a month it happens that JIRA response time is extended in terms of loading tickets.

If we look in the DB we can see the locks are set, if I search the JIRA log I can't trace why or what caused it.

Can we please advise me how best to decipher this problem. Thank you

[Radek Dostál]

The connections are idle, and returned the results in ms. Why are you looking in the DB? That's usually the least likely problem in the app. It would typically only be a problem if you severely underspec'd the db server, or severely cut down it's settings to make it non-performant by intention, or ran out of connection pool (which Jira natively generally won't do, but some 3rd party apps can suck and exhaust connection pool). In any case, the entire instance would crumble, not just issue view. Nothing in those snippets suggest DB to be any problem.

I would reckon you first want to look at a HAR file (or just network tab in browser dev tools if you can reproduce it) to identify which of the requests takes the time, alternatively take some thread dumps to see where the thread itself is (maybe it's waiting to acquire a lock or something), or it could even be a reverse proxy problem where it's not able to serve the requests in time (maybe it's being spammed by someone, maybe there are no available connections to use). Too many things, but DB shouldn't be it.

[David]

The connection pool is not depleted, I checked.

The reason we are looking at the database is because there are still locks currently.

This problem was bothering us back on 8.5.3, so we updated JIRA to 8.12.3 + updated the plugins, but the problem still occurs after some time.

[Radek Dostál]

What do you mean by locks? Of course there are locks.

[David]

Okay, I understand, thanks for the help, I'll check the proxy.