Sometimes JIRA search results take a minute.

[Jonathan Smith]

Currently we are experiencing sporadic slowness when searching content in JIRA.

Example: Searched printing... took over a minute to load results.

Suggestions on how to speed this up?

[Petr Vaníček]

Hi Jonathan,

can you share your atlassian-jira-slow-queries.log file? If there is something interesting.

[Jonathan Smith]

@Petr Vaníček 

Do you happen to know where we would find that on the server? 

We see catalina, localhost, manager, host-manager, and access_log.

[Petr Vaníček]

You can find this log in HOME (data) folder. 

Did you try make full (lock) reindex?

[Jonathan Smith]

I'll try the lock index approach tonight.

 atlassian-jira-slow-queries.log was not found in the log folder on Home. 

[Jonathan Smith]

@Petr Vaníček 

We found the slow log, however nothing was logged in it since 2018....

The atlassian-jira.log, atlassian-jira-security.log are getting updated, but the slow queries one is not.

Per this post, JIRA should log any queries more than 400ms, The general issues search page took 1.5 minutes to load (https://jira.xxxxxxxx.com/issues/?jql=), but nothing was logged.

I'll try the locked index tonight an let you know if it helps. If not, I may open a case.

[Petr Vaníček]

I just check again your screenshots based on your last log and I think I have suggestion.

How many custom fileds do you have? What about queries where you are asking for project and some value for any custom field? It will be faster I expect.

If you have a log of issues and custom fields then huge queries like "string" or empty JQL can take a long time. What about CPU when you hit someof those queries?

[Jonathan Smith]

Hi @Petr Vaníček ,

• Running the lock index did not resolve.

About the environments:

JIRA UAT - 4580 items
clicking issues, search for issues = 807ms

JIRA PROD - 18642 items 
clicking issues, search for issues = +1 minute

JIRA PROD Dashboard
Test 1: Clicking total of issues statistics (?jql=project%20%3D%20COLLAB%20AND%20resolution%20%3D%20Unresolved) = 5 seconds
Test 2: Clicking total of issues statistics (?jql=project+%3D+LOG+AND+resolution+%3D+Unresolved) = 1.3 minutes

• CPU stayed at 2%
• Custom fields PROD/UAT (including Elements) = 100ish in both environments

Next steps:

We are going to reach out to our SQL dba and see if they can monitor the SQL database to see if there is a long running query behind the scenes. Will report back.

[Jonathan Smith]

SQL database was flawless.

After testing further, seems like I am the only user who is experiencing this. I assume this is due to my admin privileges + the amount of views / content we have in JIRA.

I suppose the only thing I can do is start making projects with the admin service account instead of my account...

- Jonathan

[Lady Di]

Quick Search searches for the entire array of tasks to which the user has access. If it is a lot of tasks, there can be delays.

If we are talking about Jira Server / DC, then it can be diagnosed and treated.

And in any case, it is better to always indicate which project you are searching for: JC test text, where JC - project key.

You can read more about smart search here: https://confluence.atlassian.com/jiracoreserver073/quick-searching-861257204.html#Quicksearching-Smartquerying

[Jonathan Smith]

@Lady Di 

We are running JIRA Core Server; I would like to diagnose because typically we get results within milliseconds. 

For a few weeks now, any search results or clicking on dashboard counts takes a long time to populate results.

Even with a more specified search based on clicking counts in dashboards, it still takes close to a minute to load.

- Jonathan

[Jonathan Smith]

Note: This is a pretty small environment when it comes to data and content. It shouldn't be chugging yet ;)