Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

JIRA is unable to perform a background re-index at this time because the index files are either miss

Pradeep Kumar
Contributor
June 8, 2018

 

We are not able to run indexing and getting below error.

JIRA is unable to perform a background re-index at this time because the index files are either missing or corrupted.

 

The issue index is inconsistent with the database state. The last issue update recorded in the database was at (5/10/18 6:40 AM) but the last issue update recorded in the index was at (6/9/18 1:06 AM).

3 answers

6 votes
Moses Thomas
Community Champion
June 9, 2018

@Pradeep KumarJust  re-index again after  restart, should fix problem, just  fixed mine :)

 

 

best!

Pradeep Kumar
Contributor
June 9, 2018

It's not working 

Gibson Simon August 7, 2019

Worked for me. Had to try it about 4 times but it got it done

Like # people like this
Andrey Kolesnikov October 26, 2020

Yes, really it worked from the 4th time. Magic.

Moses Thomas
Community Champion
October 26, 2020

@Andrey Kolesnikov @Gibson Simon  if it work for you both, please mark solution as accepted so others could use  :)

 

Kind regards,

Moses.

Marcliff Fountaine
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 1, 2022

Strange, but repeated re-index attempts worked.

1 vote
Yogesh Mude
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 8, 2018

HI @Pradeep Kumar

please check the disk space this also might be the issue as here is the same issue happened with users and he has been solved.

1 vote
Vickey Palzor Lepcha
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 8, 2018

Rename the index folder - restart JIRA , it will rebuild a fresh new index , will take time to restart depending on your environment and index size.

I ask you to rename instead of delete as it will act like a backup - instead of completely deleting the folder.

Let me know if that works.

Pradeep Kumar
Contributor
June 9, 2018

I am getting below error in log after restart jira.

2018-06-09 01:35:18,791 ajp-bio-8009-exec-9 WARN localadmin 95x165x1 103syij 10.36.24.115 /secure/admin/IndexAdmin.jspa [jira.issue.index.IndexConsistencyUtils] Index consistency check failed for index 'Issue': expectedCount=22536; actualCount=55


2018-06-09 01:37:18,857 ajp-bio-8009-exec-4 WARN localadmin 97x265x1 103syij 10.36.24.115 /rest/plugins/1.0/installed-marketplace [atlassian.upm.pac.PacClientImpl] Update check request may take longer because of the number of add-ons


2018-06-09 01:41:15,511 ajp-bio-8009-exec-5 WARN localadmin 101x354x1 103syij 10.36.24.115 /secure/admin/IndexAdmin.jspa [jira.issue.index.IndexConsistencyUtils] Index consistency check failed for index 'Issue': expectedCount=22536; actualCount=55

Vickey Palzor Lepcha
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 9, 2018

Did the full retart complete ?

By the way, these aren't ERROR - they are warning.

Pradeep Kumar
Contributor
June 9, 2018

yes, Full Restart completed. But we are seeing same error.

Vickey Palzor Lepcha
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 9, 2018

Do a foreground reindex with a lock.

Suggest an answer

Log in or Sign up to answer