My JIRA index is newer than database - how to fix?

Chad@ Norwood

My jira failed a health check, and says the following under "Indexing Lucene" on this page: JIRA.EXAMPLE.COM/plugins/servlet/troubleshooting/view/?source=notification

"The issue index is inconsistent with the database state. The last issue update recorded in the database was at (10/27/17 9:10 AM) but the last issue update recorded in the index was at (10/30/17 11:59 AM).

In other words, the database has old data, the Lucene index has newer data.

Note this was probably a result of database port being blocked.

How do i force database to update from jira index?

I have jira 7.5.1 and postgres 9.4 all running on linux, one host.

 

Andy Heinzer

There is no process to take index data and move it to the database.  Database data and Index data is not a two-way street, so to speak.   The indexes are created solely upon the content in the database.

When you update/create issues in Jira, the database is actually being updated first, and then Jira is triggering an incremental index update to grab that new value and add it to your existing indexes.   Jira does not source data from the indexes to be then placed into the database.

It is unusual that the indexes would state their update is newer than the database, I grant you that.  Usually when we see this health check warning in support, it is the other way around, with the indexes being significantly older than the database.  Which usually indicates that the indexes are corrupted and in turn have to be rebuilt from scratch.  

Since you mentioned there was a blocked port to the database, I think it more than reasonable that the healthcheck Jira is running was simply unable to update this value which in turn is generating this error.

I am curious to see if perhaps just restarting Jira can kickstart this healthcheck into being able to reestablish this check correctly once more.  If that doesn't work, then recreating the indexes is another valid means to troubleshoot this as Alexey suggested.   I wouldn't expect this problem to happen again, unless there is something preventing Jira from reaching that database periodically.