slowness jira

[ebenothmen]

Hello Community,

Who had a problem with this request and how you resolved the issue please!

SELECT CG.ID, CG.issueid, CG.AUTHOR, CG.CREATED, CI.ID, CI.groupid, CI.FIELDTYPE, CI.FIELD, CI.OLDVALUE, CI.OLDSTRING, CI.NEWVALUE, CI.NEWSTRING FROM dbo.changegroup CG INNER JOIN dbo.changeitem CI ON CG.ID = CI.groupid WHERE CG.issueid=@P0 AND CI.FIELD=@P1 ORDER BY CG.CREATED ASC, CI.ID ASC

Best regrads,

Eya

[Peter DeWiit]

@ebenothmen , we are having this exact issue. @Nic Brough -Adaptavist- the SQL query shared is the deadlock observed on the SQL side. Attempting to trace this back to Jira is the question being asked.

We are working with Atlassian support to figure out the root cause of this, other that restarting the servers.

I'll make sure to update this thread as we learn more.

-pjd

[Peter DeWitt]

@ebenothmen , The root cause for our issue was a problem with the index of those tables: dbo.changeitem. Our DBA re-created both indexes and all is well.

These are the SQL commands that were used. I am not a DBA so I am sharing this as-is and can not commit to this working on any other DB. 

Please consult a real DBA. :)

CREATE UNIQUE INDEX CHANGEGROUP_SCX1
 ON dbo.CHANGEGROUP
(ISSUEID, ID)
--TABLESPACE JIRA_DATA;

CREATE INDEX CHANGEITEM_SCX1
 ON dbo.CHANGEITEM
 (GROUPID, FIELD)
--TABLESPACE JIRA_DATA;

 -pjd

[Nic Brough -Adaptavist-]

What problem are you having here?

Why are you using SQL to report?

[ebenothmen]

Hello @Nic Brough -Adaptavist- 

There is sluggishness on Jira, glancing at "Foglight" to see if there is a request that is disturbing the server, It seems to have been caused by the following request:

SELECT CG.ID, CG.issueid, CG.AUTHOR, CG.CREATED, CI.ID, CI.groupid, CI.FIELDTYPE, CI.FIELD, CI.OLDVALUE, CI.OLDSTRING, CI.NEWVALUE, CI.NEWSTRING FROM dbo .changegroup CG INNER JOIN dbo.changeitem CI ON CG.ID = CI.groupid WHERE CG.issueid=@P0 AND CI.FIELD=@P1 ORDER BY CG.CREATED ASC, CI.ID ASC

[Nic Brough -Adaptavist-]

Ok, but could you explain what the actual problem you are trying to solve is?

What do you think is the problem experienced by the end users here?  Why have you decided to look at the database connections?

[ebenothmen]

it's been several times that JIRA slowed down for all users and every time we have this request coming out as the most consuming request according to the DBAs through the Foglight tool
We are on Jira version 8.13 and SQL Server (2016)
And our only workaround at the moment is to restart the JIRA service.

thank you in advance

[Nic Brough -Adaptavist-]

If you're having to restart the service to get it to work again, it's not a database problem.  The database query activity is a symptom, like slowness for the users, it is not the cause of the problem.

You will need to start looking at what the service is doing overall why it is being slow.  What are the users triggering that leads to the slowness?  Or automated services, or external access over REST APIs? 

Run through https://confluence.atlassian.com/jirakb/troubleshoot-performance-issues-in-jira-server-336169888.html to get started on where to look.