Index failures when trying to transition or delete certain issues after upgrade from 8.5.1 to 8.13.1

Stephen Letch November 25, 2020

Error received when trying to transition certain tickets or even delete them

 

Technical details

Log's referral number: 4faf5a6d-63d0-49f4-a4ed-8ca6809e1607

Cause

Referer URL: 

com.atlassian.jira.index.IndexingFailureException: Indexing completed with 1 errors
com.atlassian.jira.index.IndexingFailureException: Indexing completed with 1 errors
	at com.atlassian.jira.index.AccumulatingResultBuilder$CompositeResult.await(AccumulatingResultBuilder.java:189) [classes/:?]
	at com.atlassian.jira.issue.index.DefaultIndexManager.obtain(DefaultIndexManager.java:863) [classes/:?]
	at com.atlassian.jira.issue.index.DefaultIndexManager.await(DefaultIndexManager.java:843) [classes/:?]
	at com.atlassian.jira.issue.index.DefaultIndexManager.executeWithIndexLock(DefaultIndexManager.java:830) [classes/:?]
	at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexIssues(DefaultIndexManager.java:618) [classes/:?]
	at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexIssueObjects(DefaultIndexManager.java:494) [classes/:?]
	at com.atlassian.jira.issue.index.DefaultIndexManager.reIndex(DefaultIndexManager.java:540) [classes/:?]
	at com.atlassian.jira.issue.index.DefaultIndexManager.reIndex(DefaultIndexManager.java:523) [classes/:?]
	at sun.reflect.GeneratedMethodAccessor2012.invoke(Unknown Source) [?:?]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [?:1.8.0_171]
	at java.lang.reflect.Method.invoke(Method.java:498) [?:1.8.0_171]
	at com.atlassian.jira.config.component.SwitchingInvocationHandler.invoke(SwitchingInvocationHandler.java:38) [classes/:?]
	at com.sun.proxy.$Proxy17.reIndex(Unknown Source) [?:?]
	at com.atlassian.jira.issue.link.DefaultIssueLinkManager.reindexLinkedIssues(DefaultIssueLinkManager.java:121) [classes/:?]
	at com.atlassian.jira.issue.link.DefaultIssueLinkManager.removeIssueLinkInternal(DefaultIssueLinkManager.java:194) [classes/:?]
	at com.atlassian.jira.issue.link.DefaultIssueLinkManager.deleteIssueLinksFromIssue(DefaultIssueLinkManager.java:261) [classes/:?]
	at com.atlassian.jira.issue.link.DefaultIssueLinkManager.removeIssueLinksInternal(DefaultIssueLinkManager.java:243) [classes/:?]
	at com.atlassian.jira.issue.link.DefaultIssueLinkManager.removeIssueLinksNoChangeItems(DefaultIssueLinkManager.java:230) [classes/:?]
	at com.atlassian.jira.issue.managers.DefaultIssueDeleteHelper.removeIssueLinks(DefaultIssueDeleteHelper.java:198) [classes/:?]
	at com.atlassian.jira.issue.managers.DefaultIssueDeleteHelper.deleteIssue(DefaultIssueDeleteHelper.java:145) [classes/:?]
	at com.atlassian.jira.issue.managers.DefaultIssueManager.deleteIssue(DefaultIssueManager.java:743) [classes/:?]
	at com.atlassian.jira.issue.managers.RequestCachingIssueManager.deleteIssue(RequestCachingIssueManager.java:247) [classes/:?]
	at com.atlassian.jira.bc.issue.DefaultIssueService.delete(DefaultIssueService.java:427) [classes/:?]
	at com.atlassian.jira.bc.issue.DefaultIssueService.delete(DefaultIssueService.java:403) [classes/:?]
	at com.atlassian.jira.web.action.issue.DeleteIssue.doExecute(DeleteIssue.java:23) [classes/:?]
	at webwork.action.ActionSupport.execute(ActionSupport.java:165) [webwork-1.4-atlassian-30.jar:?]
	at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:63) [jira-api-8.13.1.jar:?]
	at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:39) [webwork-1.4-atlassian-30.jar:?]
	at webwork.interceptor.NestedInterceptorChain.proceed(NestedInterceptorChain.java:31) [webwork-1.4-atlassian-30.jar:?]

 

 

When trying to individually index via scriptrunner:

com.atlassian.jira.index.IndexingFailureException: Indexing completed with 1 errors at com.atlassian.jira.index.AccumulatingResultBuilder$CompositeResult.await(AccumulatingResultBuilder.java:189) at com.atlassian.jira.issue.index.DefaultIndexManager.obtain(DefaultIndexManager.java:863) at com.atlassian.jira.issue.index.DefaultIndexManager.await(DefaultIndexManager.java:843) at com.atlassian.jira.issue.index.DefaultIndexManager.executeWithIndexLock(DefaultIndexManager.java:830) at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexIssues(DefaultIndexManager.java:618) at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexIssues(DefaultIndexManager.java:597) at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexIssues(DefaultIndexManager.java:581) at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexIssues(DefaultIndexManager.java:449) at com.atlassian.jira.issue.index.DefaultIndexManager.reIndex(DefaultIndexManager.java:547) at com.atlassian.jira.config.component.SwitchingInvocationHandler.invoke(SwitchingInvocationHandler.java:38) at com.sun.proxy.$Proxy17.reIndex(Unknown Source) at com.atlassian.jira.issue.index.IssueIndexManager$reIndex.call(Unknown Source) at com.onresolve.scriptrunner.canned.jira.admin.ReindexIssues$_doScript_closure1.doCall(ReindexIssues.groovy:103) at com.sun.proxy.$Proxy3986.accept(Unknown Source) at java_util_function_Consumer$accept.call(Unknown Source) at com.onresolve.jira.groovy.jql.AbstractPagerExecutor$_forEachInternal_closure2.doCall(AbstractPagerExecutor.groovy:68) at com.onresolve.jira.groovy.jql.AbstractPagerExecutor.forEachInternal(AbstractPagerExecutor.groovy:67) at com.onresolve.jira.groovy.jql.PagerExecutor.forEachIssue(PagerExecutor.groovy:26) at com.onresolve.scriptrunner.canned.jira.admin.ReindexIssues.doScript(ReindexIssues.groovy:99)  

 

1 answer

1 accepted

2 votes
Answer accepted
Daniel Ebers
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 28, 2020

Hi Stephen,

have you already tried to Re-Index the instance?

Have you made sure Script Runner is on a compatible version after upgrade - along with all other Apps updated?

Have you per chance also had the time to look into log file for further errors despite the existing one with indexing?

Cheers,
Daniel

Stephen Letch November 30, 2020

Yes :)

 

Even tried safe mode with the same results

Daniel Ebers
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.
December 1, 2020

Sad enough but I only can come up with a general article on how to debug indexing issues.
Whilst you are upgrading from an Long Term Support Release (they are known to be stable) to a more recent one you should not run into trouble in theory - but, anyway, further inspection now will be needed.

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

When you say it is happening when trying to transition "some" issues - do they all have something in common? A special validator, condition, post function or so?

Stephen Letch December 9, 2020

Let me post what Atlassian gave me that worked. :)

 

They attributed the bug to deleting issues while this wonky new version of 'Email this issue' is installed. Here's the fix via the DB.

 

----------------------

Therefore, I would like to clear the table of that problematic Issue. 
Please run this SQL query:

delete from issue_version where issue_id = 74030 and deleted = 'Y';

Once done, Kindly run a full Lock & Rebuild on the Index.  

I believe that after disabling the app, new issues can be deleted.
Could you please check and confirm?

Also, for the old issues created before disabling/downgrading the add-on, the following SQL should be executed:

 
update issue_version set DELETED = 'N' where DELETED ='Y' and ISSUE_ID in (Select ID from jiraissue);
Stephen Letch December 9, 2020

See above

Suggest an answer

Log in or Sign up to answer