Jira Issue Status and Resolution- inconsistent at different place

[Srini Srini]

1. Issue View Screen -> Status - Closed and Resolution - Fixed

2. Issue Change History -> Status - Closed and Resolution - Fixed

3. Jira DB -> Status - Closed and Resolution - Fixed

4. Issue Navigator -> Status - Open and Resolution - null

5. Issue Calendar -> Status - Open and Resolution - null

I did run the Index Optimize job and that did not fix it.

Will a full re-index fix this?

-Srini

[Dieter · Accepted solution]

a full reindex should fix that. It will look at all issues and recreate the index from the data the db. Everything should go well unless there is a severe problem in the indexing process but this would be logged in atlassian-jira.log. So if full rendexing should not help (what i don't expect) you should check for errors in atlassian-jira.log and post them here.

[Dieter]

The index optimize run just reorganizes the storage layout of the indexes to improve performance but does not reconstruct them. Indexes and db can get out of synch on runtime exceptions or flaws in plugins that cause issues not to be reindexed after changes in the DB.

[Srini Srini]

This is what I found in the logs, does this mean some thing?

Could not reindex: com.atlassian.jira.issue.util.IssueGVsIssueIterable (1 items): [xxxxxxxxxx]

2012-04-10 00:00:46,397 JiraQuartzScheduler_Worker-3 ERROR [jira.issue.index.DefaultIndexManager] Lock attempt timed out - waited 30000 milliseconds

com.atlassian.jira.issue.index.IndexException: Lock attempt timed out - waited 30000 milliseconds

[Dieter]

This kind of error is not unusual if it occurs during during the index optimize job at midnight. See some more explanation here: http://confluence.atlassian.com/display/JIRAKB/Lock+timout+-+Waited+30000+Milliseconds+Error+Message But in your case it seems only one issue has been affected but if this happens more often you should consider to increase the parameter described in the link.

[Srini Srini]

Thanks, the link was very informative and got what I was looking for, we are actually 100,000+ issue now.

-Srini