Error in Reindex Jira

Question

Hi

We launch a new jira, and used clone of  previous 'DB and jira'. After launched, I done Re-Index Jira(Lock Jira and Reindex) and below error shown every time in atlassian-log:

2021-08-14 08:48:02,215 JiraTaskExectionThread-2 ERROR
JiraAdmin 525x619x1 pzhypu 172.30.22.111 /secure/admin/IndexReIndex!reindex.jspa
[c.a.jira.task.TaskManagerImpl] Task 'Jira Indexing' failed.
com.atlassian.jira.index.IndexingFailureException: Indexing completed with 1 errors
at com.atlassian.jira.util.index.CompositeIndexLifecycleManager.reIndexAll(CompositeIndexLifecycleManager.java:83)
at com.atlassian.jira.util.index.CompositeIndexLifecycleManager.reIndexAll(CompositeIndexLifecycleManager.java:49)
at com.atlassian.jira.web.action.admin.index.ReIndexAsyncIndexerCommand.doReindex(ReIndexAsyncIndexerCommand.java:27)
at com.atlassian.jira.web.action.admin.index.AbstractAsyncIndexerCommand.call(AbstractAsyncIndexerCommand.java:63)
at com.atlassian.jira.web.action.admin.index.ReIndexAsyncIndexerCommand.call(ReIndexAsyncIndexerCommand.java:18)
at com.atlassian.jira.web.action.admin.index.AbstractAsyncIndexerCommand.call(AbstractAsyncIndexerCommand.java:26)
at com.atlassian.jira.task.TaskManagerImpl$TaskCallableDecorator.call(TaskManagerImpl.java:523)
at com.atlassian.jira.task.TaskManagerImpl$TaskCallableDecorator.call(TaskManagerImpl.java:485)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at com.atlassian.jira.task.ForkedThreadExecutor$ForkedRunnableDecorator.run(ForkedThreadExecutor.java:216)
at java.lang.Thread.run(Thread.java:745)

How do I fix it?

Thanks

Nic Brough -Adaptavist- · Answer

Those are still not actual indexing errors.  Without the error message, we're a bit stuck.

All I can really do is suggest a run throughhttps://confluence.atlassian.com/jirakb/troubleshoot-a-reindex-failure-in-jira-server-429917142.html

Marzi Goodarzian · Answer

Hi @Nic Brough -Adaptavist-

Thanks

Yes, there are many line that approximately 90% of them are same to another and like as:

2021-08-14 08:48:02,148 JiraTaskExectionThread-2 INFO JiraAdmin 525x619x1 pzhypu 172.30.22.111
/secure/admin/IndexReIndex!reindex.jspa [c.a.jira.index.MonitoringIndexWriter] [lucene-stats]
flush stats: snapshotCount=2, totalCount=2, periodSec=0, flushIntervalMillis=6,
indexDirectory=/home/jira_home8.2.3/caches/indexesV1/entities/portalpage,
indexWriterId=com.atlassian.jira.index.MonitoringIndexWriter@2b91aed6,
indexDirectoryId=MMapDirectory@/home/jira_home8.2.3/caches/indexesV1/entities/portalpage
lockFactory=org.apache.lucene.store.NativeFSLockFactory@68278f60

2021-08-14 08:48:02,148 JiraTaskExectionThread-2 INFO JiraAdmin 525x619x1 pzhypu 172.30.22.111 /secure/admin/IndexReIndex!reindex.jspa [c.a.j.w.a.admin.index.IndexAdminImpl] Re-indexing is 1% complete. Current index: PortalPage

2021-08-14 08:48:02,215 JiraTaskExectionThread-2 INFO JiraAdmin 525x619x1 pzhypu 172.30.22.111 /secure/admin/IndexReIndex!reindex.jspa [c.a.j.util.index.CompositeIndexLifecycleManager] Reindex took: 624ms. Indexer: SharedEntityIndexManager: paths: []

2021-08-14 08:48:02,215 JiraTaskExectionThread-2 INFO JiraAdmin 525x619x1 pzhypu 172.30.22.111 /secure/admin/IndexReIndex!reindex.jspa [c.a.j.index.ha.DefaultNodeReindexService] Starting node re-index service

2021-08-14 08:48:02,215 JiraTaskExectionThread-2 INFO JiraAdmin 525x619x1 pzhypu 172.30.22.111 /secure/admin/IndexReIndex!reindex.jspa [c.a.j.w.a.admin.index.IndexAdminImpl] Re-indexing finished

Nic Brough -Adaptavist- · Answer

This isn't really a direct error.  I mean, it is an error, but it's not the log of the actual error.

The indexing is a long-running process which does a whole pile of stuff.  As it runs, it may have errors that are a problem (maybe as small as one issue or field that's not indexed correctly, could be a failure to index the entire system) but do not stop the process.  It accumulates a record of these and carries on indexing.

When it finishes, it then reports "I've indexed, but I had errors".   That's the bit of the log you have shown us, but we're missing the log of the underlying error that happened.

Are there more records of errors below the segment you have shown us?  Or, are there errors above it that mention indexing?