Indexing or Cloning Issues in JIRA Throws Indexing Completed with 1 errors

Still need help?

The Atlassian Community is here for you.

Ask the community

Problem

Symptom 1:

  • When cloning a specific issue, JIRA throws error "Exception: com.atlassian.jira.index.IndexingFailureException: Indexing completed with 1 errors" . However, the clone issue is created successfully
  • The same issue have a  number of action in the History tab was marked as "Just Now" instead of the expected date and time
  • The following appears in the atlassian-jira.log:

    2015-03-03 09:48:31,927 http-bio-7615-exec-18 WARN sysadmin 588x145x1 1yymjr3 127.0.0.1 /secure/CloneIssueDetails.jspa [atlassian.jira.index.AccumulatingResultBuilder] Indexing failed for Issue - '213918'
    2015-03-03 09:48:31,927 http-bio-7615-exec-18 WARN sysadmin 588x145x1 1yymjr3 127.0.0.1 /secure/CloneIssueDetails.jspa [atlassian.jira.index.AccumulatingResultBuilder] com.atlassian.jira.util.dbc.Assertions$NullArgumentException: parameter should not be null!
    java.lang.RuntimeException: com.atlassian.jira.util.dbc.Assertions$NullArgumentException: parameter should not be null!
    	at com.atlassian.jira.index.DefaultIndex$Failure.<init>(DefaultIndex.java:123)
    	at com.atlassian.jira.issue.index.DefaultIssueIndexer$2.perform(DefaultIssueIndexer.java:208)
    	at com.atlassian.jira.issue.index.DefaultIssueIndexer$4$1.get(DefaultIssueIndexer.java:337)
    	at com.atlassian.jira.issue.index.DefaultIssueIndexer$4$1.get(DefaultIssueIndexer.java:333)
    	at com.atlassian.jira.index.SimpleIndexingStrategy.get(SimpleIndexingStrategy.java:9)
    	at com.atlassian.jira.index.SimpleIndexingStrategy.get(SimpleIndexingStrategy.java:5)
    ...
     
    Caused by: com.atlassian.jira.util.dbc.Assertions$NullArgumentException: parameter should not be null!
    	at com.atlassian.jira.util.dbc.Assertions.notNull(Assertions.java:38)
    	at com.atlassian.jira.issue.changehistory.ChangeHistoryItem$Builder.on(ChangeHistoryItem.java:440)
    	at com.atlassian.jira.issue.changehistory.DefaultChangeHistoryManager.getAllChangeItems(DefaultChangeHistoryManager.java:204)
    	at com.atlassian.jira.issue.index.DefaultChangeHistoryRetriever.apply(DefaultChangeHistoryRetriever.java:44)



Symptom 2:

  • Re-indexing JIRA throws IndexingFailureException

The following appears in the atlassian-jira.log

2015-02-19 19:37:30,778 JiraTaskExectionThread-1 WARN sysadmin 1048x628x1 pkp67f 127.0.0.1 /secure/admin/IndexReIndex.jspa [atlassian.jira.index.AccumulatingResultBuilder] com.atlassian.jira.util.dbc.Assertions$NullArgumentException: parameter should not be null!
2015-02-19 19:38:31,244 JiraTaskExectionThread-1 ERROR sysadmin 1048x628x1 pkp67f 127.0.0.1 /secure/admin/IndexReIndex.jspa [jira.util.index.CompositeIndexLifecycleManager] Reindex All FAILED.  Indexer: DefaultIndexManager: paths: [/opt/jira/jira_home/caches/indexes/comments, /opt/jira/jira_home/caches/indexes/issues, /opt/jira/jira_home/caches/indexes/changes]
com.atlassian.jira.index.IndexingFailureException: Indexing completed with 99 errors
	at com.atlassian.jira.index.AccumulatingResultBuilder$CompositeResult.await(AccumulatingResultBuilder.java:192)
	at com.atlassian.jira.issue.index.DefaultIndexManager.doIndexIssuesInBatchMode(DefaultIndexManager.java:1021)
	at com.atlassian.jira.issue.index.DefaultIndexManager.doStopTheWorldReindex(DefaultIndexManager.java:988)
	at com.atlassian.jira.issue.index.DefaultIndexManager.access$300(DefaultIndexManager.java:92)

...
 
 

Cause

Changegroup table has empty CREATED column.

Diagnostic Steps:

Symptom 1:If the  query below, return entry the instance is affected by this problem

  • Run SQL query to verify if the following return any entry:
select * from changegroup where CREATED is null and issueid in (select id from jiraissue where issuenum=ISSUENUM and project in (select id from project where pkey='PKEY'));

(info) replace the ISSUENUM and PKEY with the correct Issue Key and PKEY of the project. Notice that "Issue - '213918'" record in the log snippet above corresponds to issue ID in the jiraissue table

Symptom 2: If the SQL query below returns any entries, the instance is affected by this problem

select distinct issueid from changegroup where CREATED is null;


Resolution or Workaround

  • Backup the Database so that changes can be roll back if problem happened

  • Stop JIRA
  • Manually update the database by updating the changegroup table manually with any date value to keep the history. For example:

update changegroup set CREATED='2015-01-01 00:00:00'  where CREATED is null;
  • Start JIRA after performing the database change
  • Re-index JIRA if required

Last modified on Aug 14, 2019

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.