Instance too slow and reindex extremaly slow

[David Esteve Botella]

Hello,

Yesterday we install the plugin Agile in a production instance, and at the first moment all works fine. Before we test it in the developer instance. But yesterday the jira instance start to work too slow.

We try diferent acctons:
- Disable and disinstall the Agile Plugin
- restart the jira instance.
- restart the machine.
- Execute Integrity Checked.

The instance remain run slow, specialy in some projects.

And we found the big problem when we try to execute reindex. We execute a reindex biweekly and takes arround an hour and a half, but today I ejecute the reindex and after a hour only ejecute a 1%.

We stop it and try diferents actions:
- we Follow the intructions of https://confluence.atlassian.com/jirakb/unable-to-rebuild-jira-application-indexes-228623566.html.\\ - Ejecute a integrity check again.
- Ejecute the querries to check the data:
SELECT id,issuenum,project FROM jiraschema.jiraissue WHERE issuenum IS NULL;
SELECT * FROM jiraschema.issuelink WHERE linktype NOT IN (SELECT id FROM jiraschema.issuelinktype);
select * from jiraschema.changegroup where created is null order by issueid;

But when rerun the index the result is the same, 1% after 25 minutes. 

Cuold anybody help?

[Alexey Matveev]

Try to switch Jira to safe mode and have a look, if Jira works faster. If so, then there is a problem with an add-on or with the configuration of the add-on.

https://confluence.atlassian.com/upm/disabling-and-enabling-add-ons-273875716.html

[Nic Brough -Adaptavist-]

This rings alarm bells:

> We execute a reindex biweekly

Why?

Usually when someone is doing this, it's because they have serious problems that they've decided to ignore.  It's  "plastering over the cracks", and unless you fix the root cause, it's eventually going to go very wrong.

[David Esteve Botella]

Hi Nic,

We have a problem and we know it.

The hardware requirements ara to middle-instance, and now we have a large-instance with more than 250000 issues. We've extended the JVM Heap Size to 4Gb, but we the System Memory continue in 8Gb.

The recurrent trouble is that the issues don't reindex when it change it. For ejample after change the priority, the issueu priority show the previosly priority in the filters and dashoboards. With a reindex this problem resolve for the customers side.

We've working for the customer do two actions, adapt the requirements system and do a upgrade, we're working in 6.4.2. We think that these action resolve the main problema.

But we dont' know why yesterday the JIRA instance work too slow.

The reindex has finished in 7 hours, the first 6 hours to complete 7% and another hour to complete at

[Nic Brough -Adaptavist-]

>The recurrent trouble is that the issues don't reindex when it change it.

Right, that is textbook "you have a broken Jira, but have ignored it and covered it up". 

Your regular re-indexing is hiding a deeper problem, and there is a good chance that this is at the root of your performance problems, or that the cause is something that is related.

You need to work out why your issues are not re-indexed at the time of edit, understand it, and fix that.

[Daniel Eads {unmonitored account}]

Hi David,

There are many Agile plugins - can you link to which one on Atlassian Marketplace? Or do you mean Jira Software (used to be called JIRA Agile on Jira 6.4 and lower)?

Based on the trouble you're having, I would encourage you to open a support ticket with Atlassian at https://support.atlassian.com/contact or directly from Jira (see instructions for doing it from Jira here). We try to solve a lot of questions here on Community, but the official product support can get more detailed information about your instance which would help you in this case.

Thanks,
Daniel