8.0.0, 8.1.0, 8.5.0, 8.12.1, 8.13.0, 9.0.0, 9.2.0, 8.13.26, 8.20.13, 9.3.0
Severity 2 - Major
Atlassian Update – 21 November 2023 Dear Customers, The engineering team is currently working on this bug. Due to the complexity of the work, at this time we are not able to provide a timeline for a fix. Further updates will be posted to this ticket as developments occurs. Best regards Dino Costantini Principal Software Engineer
Generating the initial lexorank can seriously affect issue creation time.
This problem can be observed in 2 ways:
- contention on lexorank lock when initialising rank when creating issue
- some nodes are never able to get the lexorank lock and create the lexorank initial value
This problem will manifests itself by increased issue creation time.
In logs we need to enable DEBUG logging on com.atlassian.greenhopper.service.lexorank.
The failed locks should show up in the atlassian-greenhopper.log log.
The indexing stats (indexing-stats) should also show the Rank custom field as expensive - note the max value as the lower value of the average may be "improved" by the updates which will not trigger the expensive Lexorank initialization.
- Note: avg: 1765.5ms, max: 7199ms
This problem will manifests itself by increased issue creation time in the range of 18-20sec.
Lexorank is unable to get the lexorank lock (and create the lexorank initial value) and the issue is indexed with Lexorank.MAX.
This will be seen in the atlassian-greenhopper.log log as warnings:
- Individual ranking operation has 1500 ms timeout for rank lock. Due to DB contetion and slow operation, issue ranking operation fails to save new rank since rank lock expire.
- See KB for more details regarding Lexorank: Troubleshooting New Ranking System Issues
Currently there is no known workaround for this behavior. A workaround will be added here when available