Details
-
Bug
-
Resolution: Fixed
-
Low
-
6.4.0.6
-
None
-
6.04
-
Description
Summary
JIRA Agile should not allow duplicate ISSUE_ID to be created in AO_60DB71_LEXORANK table. Some customers encounter indexing issues after upgrade to JIRA Agile 6.4.0.x with the new LexoRank introduced.
This duplicate ISSUE_ID caused the re-indexing to fail when JIRA Agile is enabled.
The following error found in the log:
2014-06-11 19:08:51,399 IssueIndexer:thread-5 WARN admin 1148x497x1 xxxxx 127.0.0.1 /secure/admin/IndexReIndex.jspa [jira.issue.index.DefaultIssueDocumentFactory] Error indexing issue ABC-90: Dropping 'customfield_11530'
java.lang.RuntimeException: Expected exactly one rank for 11530 / 21202 but found 2
at com.atlassian.greenhopper.manager.lexorank.LexoRankDaoImpl.findByFieldAndIssueId(LexoRankDaoImpl.java:271)
at com.atlassian.greenhopper.service.lexorank.LexoRankOperation.rankInitially(LexoRankOperation.java:141)
Expected Behaviour
JIRA Agile should check if there are duplicates ISSUE_ID in AO_60DB71_LEXORANK and decides to either replace or not add new.
Workaround
Please see KB article: https://confluence.atlassian.com/display/AGILEKB/Indexing+Failed+with+RuntimeException+Expected+exactly+one+rank