Details
-
Suggestion
-
Status: Gathering Interest (View Workflow)
-
Resolution: Unresolved
-
None
-
3
-
15
-
Description
Problem Definition
Currently when the number of characters on the lengthiest rank field on the AO_60DB71_LEXORANK table exceeds:
- 50 characters: a rebalance operation is scheduled to occur in 12 hours;
- 100 characters: a rebalance operation is immediately started;
See related KB Troubleshooting new ranking system issues
That will lead to the following:
- Lexorank rebalance job will balance whole space for RANK and that means touching all issues.
- For large instance this might take significant time (days).
In some cases, those long RANK values are localised in small area and there is no need to rebalance whole space.
For example, there is a problem only around space hz :
1|zzzzzz: 1|w00000: 1|hzzzzz: 1|hzzzzy:zzzzzzzzzzzzzzzzzzzzzzzzzzzzy 1|hzzzzy:zzzzzzzzzzzzzzzzzzzzzzzzzzzzw 1|hzzzzy:zzzzzzzzzzzzzzzzzzzzzzzzzzzzr 1|i00000:
In majority cases there are problem with a couple of thousands rows only, while whole table has millions rows.
Suggested Solution
Add option for Lexorank rebalancing task for localize those areas and rebalance only them.
That will significantly reduce length of rebalancing (from days to minutes). As a consequence it reduce load for Jira.
Workaround
None
Attachments
Issue Links
- is related to
-
- Closed
- relates to
-
JSWSERVER-16466 Issue rank operations may fail due to reaching the maximum rank length
-
- Closed
-
-
-
- Closed
-
-
- Closed
-
- Closed
-
MNSTR-3342 Loading...
- Mentioned in
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-