SQL calls made by a Kanban board

Question

We have an user who Kanban's board is returning timeouts on our prod server. But in our staging server, which contains our prod data from two weeks ago, we see the issues in 10 seconds for the same board...

I enabled the SQL logging to see what SQL calls are made to get the data from this board, so that I can connect to our (Oracle 12) database and execute the query on both servers to see if the problem lies in the database or elsewere.

But I didn't see anything useful. Does something knows which SQL are made to see that? At least the table names so I can try to grep the lines in the log.

BTW, if the JQL associated to the board is using ORDER BY, is this done on the database side or in memory in Jira?

Nic Brough -Adaptavist- · Answer

This is going to be very hard to diagnose.  A timeout implies that the server is working on digging up the data for so long, the client is giving up waiting.  Without an error in the log, we can't say more than "the server is still working on it".

I would start with a look at the board settings - what is the board query first - if you run that in the issue navigator, how many issues does it return?  Then combine the "sub filter" (the one that hides "done" issues from the board - it's usually something about excluding issues that have a fix version).

I'd also want to test it with that user and another one - is it just that person having the issue?  If it is, then do they get it if they use another browser or someone else's machine?

Pascal Robert_uh6yju · Answer

We only get "Error Request timed out" in  the browser, no errors in the log.

Also looked at iostat and support-tools.jar to see if the file system was busy, and that's not the case. Never saw usage more than 45% with iostat.

Nic Brough -Adaptavist- · Answer

There is little or no SQL being used on boards, Jira is reading the index mainly.  The problem is not the database

Same for the order-by - it's read from the index and sorted in memory

I'm afraid you're going to need to go into more depth - what do the logs say when it times out?