List of all known Agile Lexorank error
プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Fisheye および Crucible は除く
This page is a compilation of all known Lexorank errors that come from the JIRA Software source code. We have also tried to explain the problem that causes the error to be thrown as well as the action plan to fix it.
See also another page: Troubleshooting LexoRank System Issues
説明
List of all known Agile Lexorank Errors with the brief Problem description and related possible Action.
| エラー | 問題 | 操作 | ||||
|---|---|---|---|---|---|---|
| Rebalancing errors | ||||||
Expected the row to migrate to be in the old bucket [oldBucket=%s, rowBucket=%s] または Expected the row last migrated to be in the new bucket [newBucket=%s, rowBucket=%s] | Value of "Bucket in RANK" doesn't match the value of "BUCKET column" for a specific row eg:
| Data in AO_60DB71_LEXORANK table is corrupted and needs to be fixed, please follow steps from Share_Logs_Data (see Actions section below) | ||||
| Couldn't find rows on balance boundary | JIRA couldn't find 2 rows balance boundary during balancing. | Data in AO_60DB71_LEXORANK table needs to be reviewed, please follow steps from Share_Logs_Data (see Actions section below) | ||||
| Failed to save rank row, retry | Each individual ranking operation has 1500 ms timeout for rank lock. JIRA couldn't save migrated data into DB and will retry. | In most cases problem caused by slow DB. Check DB performance, see possibly related JSWSERVER-16542 - Getting issue details... STATUS | ||||
| Failed to save rank row, aborting | JIRA couldn't save migrated data into DB and stopped. Problem is not clear. | Please follow steps from Share_Logs (see Actions section below) | ||||
| Rank errors | ||||||
WARN [c.a.g.customfield.lexorank.LexoRankCFType] Unable to retrieve rank for field [10600] and issue [2341873] | Future allocated RANK length for issue [2341873] exceeds 254 characters during ranking operation, that operation will not be possible until RANK length gets back to normal. | The problem should be fixed by rebalancing.
See also: Jira Software throws UI error when ranking issues on boards | ||||
com.atlassian.greenhopper.manager.lexorank.LexoRankIntegrityException: Expected exactly one rank row for issue[id=%d] for rank field[id=%d], but found %d rows | There are multiple RANK rows for the same Field with same IssueID | Data in AO_60DB71_LEXORANK table is duplicated and needs to be fixed See articles : | ||||
com.atlassian.greenhopper.manager.lexorank.LexoRankIntegrityException: Expected exactly one minimum marker row for rank field[id=%d], but found %d or similar: Expected exactly one maximum marker row forrankfield[id=%d], but found %d | Correspondingly:
| Data in AO_60DB71_LEXORANK table is corrupted and needs to be fixed
| ||||
| com.atlassian.greenhopper.manager.lexorank.LexoRankIntegrityException: Expected the rank row to be of type %s. Found row[%s] | Problem with "Minimum marker row" (?|000000). Either:
Problem with "Maximum marker row" (?|zzzzzz). Either:
| Data in AO_60DB71_LEXORANK table is corrupted and needs to be fixed 参照先:
| ||||
com.atlassian.greenhopper.manager.lexorank.LexoRankIntegrityException: Expected to find minimum marker row for rank field[id=11960], but found none. or similar: Expected to find maximum marker row forrank field[id=%d], but found none. | Correspondingly:
|
| ||||
com.atlassian.greenhopper.manager.lexorank.LexoRankIntegrityException: Expected exactly 2 rows; the minimum marker row and the highest ranked row forrank field[id=%d] or similar: Expected exactly 2 rows; the maximum marker row and the lowest ranked row for rank field[id=%d] | JIRA couldn't find 2 row in last/first position ORDER BY ASC. Problem is not clear. | Data in AO_60DB71_LEXORANK table is corrupted and needs to be fixed | ||||
com.atlassian.greenhopper.manager.lexorank.LexoRankIntegrityException: | Problem with "Minimum marker row" (?|000000). Either:
Problem with "Maximum marker row" (?|zzzzzz). Either:
| Data in AO_60DB71_LEXORANK table is corrupted and needs to be fixed
| ||||
Enable Additional Logging for LexoRank
By default, the logging of ranking system is disabled. To get detailed logging of what the system is doing add a new logger to JIRA's Logging and Profiling page
Logging for balancing
level: DEBUGpackage:com.atlassian.greenhopper.service.lexorank.balanceLogging for ranking
level: DEBUGpackage:com.atlassian.greenhopper.service.lexorank- Logging for ranking DB operations
level: DEBUG
package: com.atlassian.greenhopper.manager.lexorank - Logging for statistics: every minute logs the activity and performance of the ranking system
level: DEBUG
package:com.atlassian.greenhopper.service.lexorank.LexoRankStatisticsAgent
アクション
| 操作 | 手順 |
|---|---|
| Share_Logs | Please do the following steps:
|
| Share_Logs_Data | Please do the following steps:
|