Cannot reindex jira after problematic indexing operation

Hasan Doğan November 26, 2013

We performed background indexing but we got the following message from server : JIRA is unable to perform a background re-index at this time because the index files are either missing or corrupted. Although we are able to reach the issue detail directly via issue URLs , we cannot list or seach the issues after this problematic indexing operation. PS. Please keep in the mind that , the last issue we updated before the problematic issue (JCON-80) has a different problems than the others.While we can update other issues, we cannot make any change on this issue now. Now , the system forces to use 'Lock JIRA and rebuild index' but we get the following problem : Indexing completed with 216 errors Task completed in 1 second with unexpected error. Started Today 12:56 PM. Finished Today 12:56 PM. com.atlassian.jira.index.IndexingFailureException: Indexing completed with 216 errors at com.atlassian.jira.index.AccumulatingResultBuilder$CompositeResult.await(AccumulatingResultBuilder.java:147) at com.atlassian.jira.issue.index.DefaultIndexManager.doIndexIssuesInBatchMode(DefaultIndexManager.java:877) at com.atlassian.jira.issue.index.DefaultIndexManager.doStopTheWorldReindex(DefaultIndexManager.java:844) at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexAll(DefaultIndexManager.java:307) at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexAll(DefaultIndexManager.java:272) at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexAll(DefaultIndexManager.java:267) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.atlassian.util.profiling.object.ObjectProfiler.profiledInvoke(ObjectProfiler.java:83) at com.atlassian.jira.config.component.SwitchingInvocationHandler.invoke(SwitchingInvocationHandler.java:28) at com.sun.proxy.$Proxy144.reIndexAll(Unknown Source) at com.atlassian.jira.util.index.CompositeIndexLifecycleManager.reIndexAll(CompositeIndexLifecycleManager.java:56) at com.atlassian.jira.web.action.admin.index.ReIndexAsyncIndexerCommand.doReindex(ReIndexAsyncIndexerCommand.java:28) at com.atlassian.jira.web.action.admin.index.AbstractAsyncIndexerCommand.call(AbstractAsyncIndexerCommand.java:54) at com.atlassian.jira.web.action.admin.index.ReIndexAsyncIndexerCommand.call(ReIndexAsyncIndexerCommand.java:16) at com.atlassian.jira.web.action.admin.index.AbstractAsyncIndexerCommand.call(AbstractAsyncIndexerCommand.java:23) at com.atlassian.jira.task.TaskManagerImpl$TaskCallableDecorator.call(TaskManagerImpl.java:374) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at com.atlassian.jira.task.ForkedThreadExecutor$ForkedRunnableDecorator.run(ForkedThreadExecutor.java:250) at java.lang.Thread.run(Unknown Source) We stopped the JIRA instance and delete the index folder and started it again. But the problem still exists

2 answers

1 accepted

3 votes
Answer accepted
Tiago Comasseto
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.
November 26, 2013

Hi Hasan, index issues are usually related to plugins. Have you tried to reindex on plugin safe mode?

Cheers

Hasan Doğan December 3, 2013

Hi Tiago,

In safe mode, I perfomed reindxing issue successfully. I investigated which plugin causes this problem by enabling one by one and find out it : The behaviour plugin (https://marketplace.atlassian.com/plugins/com.onresolve.jira.plugin.Behaviours)

thank you for your recommendation,

BTW, I had installed this plug in 2 months ago and performed a lot of reindexing while it was enabled. that's what I confused.

Best,

0 votes
Alejandro Conde Carrillo
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.
November 26, 2013

May be there is a problem with your data. Did you try Using the Database Integrity Checker?

Hasan Doğan December 3, 2013

Yes I did, everything was fine

Suggest an answer

Log in or Sign up to answer