Indexes may be corrupt - unable to retriev e component with id=????

Jenin C M September 25, 2011

Hi All,

I am getting below error in my Jira logs:

catalina.out.20110924:2011-09-24 01:02:58,590 Sending mailitem com.atlassian.jira.mail.SubscriptionMailQueueItem owner: 'u005188'
ERROR u005188 Mail Queue Service [jira.issue.statistics.ComponentStatisticsMapper] Indexes may be corrupt - unable to retriev
e component with id '13902'.
catalina.out.20110924:2011-09-24 01:02:58,594 Sending mailitem com.atlassian.jira.mail.SubscriptionMailQueueItem owner: 'u005188'
ERROR u005188 Mail Queue Service [jira.issue.statistics.ComponentStatisticsMapper] Indexes may be corrupt - unable to retriev
e component with id '19754'.

This may be caused due to some deleted components which may still exist in the database. (may be nodeassociation table).

Could this be resolved by running Integrity checker? (We are using Jira 4.2.2)

Any suggestions will be much appreciated.

Thanks and Regards,

Jenin C M

2 answers

1 vote
J Thomas
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.
December 6, 2011

If this is due to https://jira.atlassian.com/browse/JRA-15750 then a re-index wouldn't help - you'll need to delete the records from the nodeassociation table that are linking issues to deleted components. Fair question to ask if the Integrity Checker has been extended to do this for you as JRA-15750 says it should be but the issue isn't clear whether it has been or for which version, hence I guess your question!

It's not mentioned in http://confluence.atlassian.com/display/JIRA/Using+the+Database+Integrity+Checker (latest version) so I guess it's not been implemented yet. JRA-15750 gives SQL to delete the offending records (after backing up of course).

0 votes
David Chan
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 6, 2011

I doubt the integrity checker would help with an index issue. Have you tried performing a manual re-index?

You may also want to considering trying to rebuild the index from scratch, see here:

http://confluence.atlassian.com/display/JIRAKB/Unable+to+Rebuild+JIRA+Index

Just note that re-indexing will lock your system down until it's complete.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events