-
Bug
-
Resolution: Unresolved
-
Low (View bug fix roadmap)
-
None
-
10.2.0
-
None
-
10.02
-
Severity 3 - Minor
-
Issue Summary
When solving JSWSERVER-16057 we found out that reindexing process prior to Jira 10.2 were failing silently, being not logged anywhere. Since 10.2 those errors will be propagated correctly. This is a bug where you can report issues with rebalancing. You can observer errors/exception in the log files like that:
"Indexing failed for rebalanced issues. Errors:" + remaining part of the error. ---- OR ---- "LexoRank balancer failed," + remaining part of the error.
Be aware that during our investigation, we found an issue with the LexoRank management tab. No errors with rebalancing are propagated to the UI. More about that in this bug -> JSWSERVER-26105
Steps to Reproduce
- TBD
Expected Results
1. No errors in the log
Actual Results
The below exception is thrown in log file:
"Indexing failed for rebalanced issues. Errors:" + remaining part of the error. ---- OR ---- "LexoRank balancer failed," + remaining part of the error.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- is related to
-
JSWSERVER-16057 LexoRank rebalancing may stuck in some cases
- Closed
- relates to
-
JSWSERVER-16057 LexoRank rebalancing may stuck in some cases
- Closed
-
JSWSERVER-26105 Rebalancing errors are silenced and not propagated to UI
- Gathering Impact
Rebalance can fail because of issue with reindexing
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
10.2.0
-
None
-
10.02
-
Severity 3 - Minor
-
Issue Summary
When solving JSWSERVER-16057 we found out that reindexing process prior to Jira 10.2 were failing silently, being not logged anywhere. Since 10.2 those errors will be propagated correctly. This is a bug where you can report issues with rebalancing. You can observer errors/exception in the log files like that:
"Indexing failed for rebalanced issues. Errors:" + remaining part of the error. ---- OR ---- "LexoRank balancer failed," + remaining part of the error.
Be aware that during our investigation, we found an issue with the LexoRank management tab. No errors with rebalancing are propagated to the UI. More about that in this bug -> JSWSERVER-26105
Steps to Reproduce
- TBD
Expected Results
1. No errors in the log
Actual Results
The below exception is thrown in log file:
"Indexing failed for rebalanced issues. Errors:" + remaining part of the error. ---- OR ---- "LexoRank balancer failed," + remaining part of the error.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- is related to
-
JSWSERVER-16057 LexoRank rebalancing may stuck in some cases
- Closed
- relates to
-
JSWSERVER-16057 LexoRank rebalancing may stuck in some cases
- Closed
-
JSWSERVER-26105 Rebalancing errors are silenced and not propagated to UI
- Gathering Impact