Jira 9.12.11 full re-index fails

Ekaterina Berezutskaya February 14, 2025

 

 

I'm trying to run the full re-index with Jira 9.12.11 but I'm always getting the following error:

Screenshot_12.jpg

The logs are only showing some errors: 

025-02-12 13:13:42,886+0300 JiraTaskExecutionThread-1 ERROR evberez     [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:88)

    at com.atlassian.jira.util.index.CompositeIndexLifecycleManager.reIndexAll(CompositeIndexLifecycleManager.java:51)

 

Also, there is "NonUniqueResultException" in the logs:

 

2025-02-12 11:43:45,403+0300 JiraTaskExecutionThread-1 WARN xxx_user     [c.a.jira.index.AccumulatingResultBuilder] java.util.concurrent.ExecutionException: com.querydsl.core.NonUniqueResultException: Only one result is allowed for fetchOne calls

java.lang.RuntimeException: java.util.concurrent.ExecutionException: com.querydsl.core.NonUniqueResultException: Only one result is allowed for fetchOne calls

    at com.atlassian.jira.index.FutureResult.await(FutureResult.java:29)

    at com.atlassian.jira.index.AccumulatingResultBuilder.collectResult(AccumulatingResultBuilder.java:93)

......

I tried all solutions from this article 

https://confluence.atlassian.com/jirakb/troubleshoot-a-reindex-failure-in-jira-server-429917142.html

 

 

 

 

but nothing helps.

  

Has anyone had the same problem?

1 answer

0 votes
Matt Doar _Adaptavist_
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.
February 14, 2025

I would dig into step 5 about a plugin. In a test instance, disable all customer installed plugins and run a reindex. See if it fails. If it does, then there is corrupted data in the database. If it works, then re-enable the plugins one at a time and run a reindex after each one is re-enabled. This is very tedious, but is one way to narrow down the problematic plugin.

If the error is in the DB, then look at increasing the log level around reindexing to see if you can work out which issue (or DB table and field) is the problem. I think I'd follow up with Atlassian support after that.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events