Jira working slow, probably because of LexoRank

[Adrian Kaczmarek]

Hello
I have a problem with jira 7.3.6. Last week we restarted our instance. After that, we have some problems with working on issues. Sometimes, we cannot delete issues, or create issues because of time out. I observed in logs some new warnings:
[c.a.g.customfield.lexorank.LexoRankCFType] Unable to retrieve rank for field [10005] and issue [279725]
[c.a.g.customfield.lexorank.LexoRankCFType] gh.lexorank.service.error.retrytimeout
[c.a.g.customfield.lexorank.LexoRankIndexer] Could not retrieve LexoRank value for issue[id=279725]. Indexing max LexoRank value instead.

I've searched internet and found this: https://jira.atlassian.com/browse/JSWSERVER-10873. We checked the suggestions posted in the comments but none of them works.

[somethingblue · Accepted solution]

Hi,

There is a knowledge base article titled Issue ranking failed due to LOCK_HASH is not null that may help:

1. Enable Lexorank debugging packages below to DEBUG level:

   com.atlassian.greenhopper.service.lexorank.balance
   com.atlassian.greenhopper.service.lexorank
   com.atlassian.greenhopper.service.lexorank.LexoRankStatisticsAgent

2. Identify the "LOCK_HASH" column that has null entries:

   select * from "AO_60DB71_LEXORANK" where "TYPE" in ('0','2') and "LOCK_HASH" is not null;

   Expected output should be

    FIELD_ID | ID |       ISSUE_ID       | LOCK_HASH | LOCK_TIME |   RANK    | TYPE
   ----------+----+----------------------+-----------+-----------+-----------+------
       10000 |  7 | -9223372036854775808 |           |           | 0|000000: |    0
       10000 |  8 |  9223372036854775807 |           |           | 0|zzzzzz: |    2

   If the output is not what we seen like above, please move to the resolution.

Take a look at the above mentioned knowledge base if the above instructions come out as expected.  If the query is empty take a look at Several actions such as issue ranking, move, export are failing.

Cheers,

Branden