LexoRank error while deleting issues

Anil January 2, 2020
java.lang.RuntimeException: Could not find suitable distance for rank.
java.lang.RuntimeException: Could not find suitable distance for rank.
	at com.atlassian.greenhopper.model.lexorank.LexoRank.findSpacing(LexoRank.java:217) [?:?]
	at com.atlassian.greenhopper.model.lexorank.LexoRank.between(LexoRank.java:185) [?:?]
	at com.atlassian.greenhopper.model.lexorank.LexoRank.between(LexoRank.java:146) [?:?]
	at com.atlassian.greenhopper.model.lexorank.LexoRank.genNext(LexoRank.java:108) [?:?]
	at com.atlassian.greenhopper.service.lexorank.LexoRankOperation.rankInitially(LexoRankOperation.java:216) [?:?]
	at com.atlassian.greenhopper.service.lexorank.LexoRankOperation.execute(LexoRankOperation.java:114) [?:?]
	at com.atlassian.greenhopper.manager.lexorank.LexoRankManagerImpl.performRankOperation(LexoRankManagerImpl.java:300) [?:?]
	at com.atlassian.greenhopper.manager.lexorank.LexoRankManagerImpl.getRankOrRankInitially(LexoRankManagerImpl.java:86) [?:?]
	at com.atlassian.greenhopper.customfield.lexorank.LexoRankCFType.getValueFromIssue(LexoRankCFType.java:121) [?:?]
	at com.atlassian.greenhopper.customfield.lexorank.LexoRankCFType.getValueFromIssue(LexoRankCFType.java:29) [?:?]
	at com.atlassian.jira.issue.fields.ImmutableCustomField.getValue(ImmutableCustomField.java:350) [classes/:?]
	at com.atlassian.jira.issue.managers.DefaultIssueDeleteHelper$DeletedIssueEventData.collectCustomFieldValues(DefaultIssueDeleteHelper.java:288) [classes/:?]
	at com.atlassian.jira.issue.managers.DefaultIssueDeleteHelper$DeletedIssueEventData.<init>(DefaultIssueDeleteHelper.java:275) [classes/:?]
	at com.atlassian.jira.issue.managers.DefaultIssueDeleteHelper.deleteIssue(DefaultIssueDeleteHelper.java:120) [classes/:?]
	at com.atlassian.jira.issue.managers.DefaultIssueManager.deleteIssue(DefaultIssueManager.java:723) [classes/:?]
	at com.atlassian.jira.issue.managers.RequestCachingIssueManager.deleteIssue(RequestCachingIssueManager.java:232) [classes/:?]
	at com.atlassian.jira.bc.issue.DefaultIssueService.delete(DefaultIssueService.java:402) [classes/:?]
	at com.atlassian.jira.bc.issue.DefaultIssueService.delete(DefaultIssueService.java:378) [classes/:?]
	at 

2 answers

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 3, 2020

This can happen when you've been re-ranking a lot and have used up too many spaces or put a huge distance between some issues.  It's more likely to happen when something has gone wrong with ranking somewhere, and you're hitting a broken one.

Best bet is to go through the options over at https://confluence.atlassian.com/jirakb/understand-the-lexorank-managment-page-in-jira-server-779159218.html

Anil January 3, 2020

@Nic Brough -Adaptavist-  Thanks for your reply.

We are seeing this error after Re-indexing as part of weekly maintenance. 

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 3, 2020

Generally, you don't reindex weekly, it should not be needed on a well-set-up Jira.

Have you worked through the steps on the document I gave?

Anil January 3, 2020

Yes. I worked on that document yesterday. 

We have 14 fields in all.

Balance status check - Failed for most of the Fields.

Duplicate ranks check - Failed for half of the fields.

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 3, 2020

And did you apply the fixes for those?

Anil January 3, 2020

I did "balance"  to custom fields.  I am not sure how to fix.

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 5, 2020

Did you read all the links in the "how to fix this" columns in the error message table?

Anil January 6, 2020

Yes. 

The following error is in logs.:

Exception: 'Could not find suitable distance for rank.'

Like sh w likes this

Suggest an answer

Log in or Sign up to answer