• Type: Bug
• Resolution: Unresolved
• Priority: Low (View bug fix roadmap)
• Fix Version/s: None
• Affects Version/s: 10.2.0, 9.4.29, 9.12.16
• Component/s: Lexorank
• Labels:

  None

1. 

   image-2024-09-16-10-56-01-865.png

   74 kB

   16/Sep/2024 8:56 AM

2. 

   image-2024-09-16-10-56-59-407.png

   6 kB

   16/Sep/2024 8:56 AM

[JSWSERVER-26105] Rebalancing errors are silenced and not propagated to UI

Oleksandr Tkachenko made changes - 06/Dec/2024 8:41 AM

Labels

Original: FY25NNB NNB3

Oleksandr Tkachenko made changes - 25/Oct/2024 12:48 PM

Labels

Original: FY25NNB

New: FY25NNB NNB3

Oleksandr Tkachenko made changes - 24/Oct/2024 7:02 AM

Labels

New: FY25NNB

Stasiu made changes - 18/Sep/2024 6:18 AM

Status

Original: Needs Triage [ 10030 ]

New: Gathering Impact [ 12072 ]

Bugfix Automation Bot made changes - 16/Sep/2024 9:30 AM

Introduced in Version

New: 9.04

Stasiu made changes - 16/Sep/2024 9:18 AM

Description

Original: h3. Issue Summary This is reproducible on Data Center: (yes) h3. Steps to Reproduce  # Observe any errors in the log files   # Some of the errors could be logged on the warn level  # UI present that rebalancing finished successfully.    Example of the error: {code:java} [service.lexorank.balance.LexoRankBalancer] Indexing Queue for rebalanced issues overflow, reindex stuck or is taking longer than expected >PT320S {code} h3. Expected Results UI should propagate errors to the UI. Additionally errors shouldn't be logged on warn level. h3. Actual Results Rebalancing UI still shows that rebalancing finished successfully. !image-2024-09-16-10-56-01-865.png|width=1248,height=159! After refreshing the page only some of the issues being rebalanced. Issues are redistributed between two buckets.  !image-2024-09-16-10-56-59-407.png|width=225,height=119! h3. Workaround After  fix for this bug [JSWSERVER-16057|https://jira.atlassian.com/browse/]  in Jira 10.2 and later rebalancing shouldn't stuck for infinite amount of time and you can try to trigger rebalancing once again.

New: h3. Issue Summary This is reproducible on Data Center: (yes) h3. Steps to Reproduce  # Observe any errors in the log files   # Some of the errors could be logged on the warn level  # UI present that rebalancing finished successfully.    Example of the error: {code:java} [service.lexorank.balance.LexoRankBalancer] Indexing Queue for rebalanced issues overflow, reindex stuck or is taking longer than expected >PT320S {code} h3. Expected Results UI should propagate errors to the UI. Additionally errors shouldn't be logged on warn level. h3. Actual Results Rebalancing UI still shows that rebalancing finished successfully. !image-2024-09-16-10-56-01-865.png|width=1248,height=159! After refreshing the page only some of the issues being rebalanced. Issues are redistributed between two buckets.  !image-2024-09-16-10-56-59-407.png|width=225,height=119! h3. Workaround After  fix of [JSWSERVER-16057|https://jira.atlassian.com/browse/]  in Jira 10.2 and later, rebalancing shouldn't stuck for infinite amount of time and you can try to trigger rebalancing once again.

Stasiu made changes - 16/Sep/2024 9:18 AM

Description

Original: h3. Issue Summary This is reproducible on Data Center: (yes) h3. Steps to Reproduce  # Observe any errors in the log files   # Some of the errors could be logged on the warn level  # UI present that rebalancing finished successfully.    Example of the error: {code:java} [service.lexorank.balance.LexoRankBalancer] Indexing Queue for rebalanced issues overflow, reindex stuck or is taking longer than expected >PT320S {code} h3. Expected Results UI should propagate errors to the UI. Additionally errors shouldn't be logged on warn level.  sdfasdfasdfa h3. Actual Results Rebalancing UI still shows that rebalancing finished successfully. !image-2024-09-16-10-56-01-865.png|width=1248,height=159! After refreshing the page only some of the issues being rebalanced. Issues are redistributed between two buckets.  !image-2024-09-16-10-56-59-407.png|width=225,height=119! h3. Workaround After  fix for this bug [JSWSERVER-16057|https://jira.atlassian.com/browse/]  in Jira 10.2 and later rebalancing shouldn't stuck for infinite amount of time and you can try to trigger rebalancing once again.

New: h3. Issue Summary This is reproducible on Data Center: (yes) h3. Steps to Reproduce  # Observe any errors in the log files   # Some of the errors could be logged on the warn level  # UI present that rebalancing finished successfully.    Example of the error: {code:java} [service.lexorank.balance.LexoRankBalancer] Indexing Queue for rebalanced issues overflow, reindex stuck or is taking longer than expected >PT320S {code} h3. Expected Results UI should propagate errors to the UI. Additionally errors shouldn't be logged on warn level. h3. Actual Results Rebalancing UI still shows that rebalancing finished successfully. !image-2024-09-16-10-56-01-865.png|width=1248,height=159! After refreshing the page only some of the issues being rebalanced. Issues are redistributed between two buckets.  !image-2024-09-16-10-56-59-407.png|width=225,height=119! h3. Workaround After  fix for this bug [JSWSERVER-16057|https://jira.atlassian.com/browse/]  in Jira 10.2 and later rebalancing shouldn't stuck for infinite amount of time and you can try to trigger rebalancing once again.

Stasiu made changes - 16/Sep/2024 9:17 AM

Description

Original: h3. Issue Summary This is reproducible on Data Center: (yes) h3. Steps to Reproduce  # Observe any errors in the log files   # Some of the errors could be logged on the warn level  # UI present that rebalancing finished successfully.    Example of the error: {code:java} service.lexorank.balance.LexoRankBalancer] Indexing Queue for rebalanced issues overflow, reindex stuck or is taking longer than expected >PT320S {code} h3. Expected Results UI should propagate errors to the UI. Additionally errors shouldn't be logged on warn level.  sdfasdfasdfa h3. Actual Results Rebalancing UI still shows that rebalancing finished successfully. !image-2024-09-16-10-56-01-865.png|width=1248,height=159! After refreshing the page only some of the issues being rebalanced. Issues are redistributed between two buckets.  !image-2024-09-16-10-56-59-407.png|width=225,height=119! h3. Workaround After  fix for this bug [JSWSERVER-16057|https://jira.atlassian.com/browse/]  in Jira 10.2 and later rebalancing shouldn't stuck for infinite amount of time and you can try to trigger rebalancing once again.

New: h3. Issue Summary This is reproducible on Data Center: (yes) h3. Steps to Reproduce  # Observe any errors in the log files   # Some of the errors could be logged on the warn level  # UI present that rebalancing finished successfully.    Example of the error: {code:java} [service.lexorank.balance.LexoRankBalancer] Indexing Queue for rebalanced issues overflow, reindex stuck or is taking longer than expected >PT320S {code} h3. Expected Results UI should propagate errors to the UI. Additionally errors shouldn't be logged on warn level.  sdfasdfasdfa h3. Actual Results Rebalancing UI still shows that rebalancing finished successfully. !image-2024-09-16-10-56-01-865.png|width=1248,height=159! After refreshing the page only some of the issues being rebalanced. Issues are redistributed between two buckets.  !image-2024-09-16-10-56-59-407.png|width=225,height=119! h3. Workaround After  fix for this bug [JSWSERVER-16057|https://jira.atlassian.com/browse/]  in Jira 10.2 and later rebalancing shouldn't stuck for infinite amount of time and you can try to trigger rebalancing once again.

Stasiu made changes - 16/Sep/2024 9:02 AM

Link

New: This issue is related to JSWSERVER-16057 [ JSWSERVER-16057 ]

Stasiu made changes - 16/Sep/2024 9:00 AM

Link

New: This issue is related to JSWSERVER-26104 [ JSWSERVER-26104 ]

Stasiu created issue - 16/Sep/2024 9:00 AM