-
Bug
-
Resolution: Fixed
-
Low
-
4.20.0
-
None
-
1
-
Severity 3 - Minor
-
Issue Summary
User faces 503 error while performing full re-indexing. This error doesn't have any impact on the full reindexing process. But an inconvenience to the customer.
This is reproducible on the customer's end. But not on our end.
Steps to Reproduce
The issue is reproducible at the customer's end. But not reproducible at our end.
- Set up a single-node DC instance.
- Run a clean reindex process.
Expected Results
No errors are thrown on the screen while reindex is going on.
Actual Results
The user faces 503 error on the screen, while the call is being made to
https://<base_url>rest/insight/1.0/global/config?_=33333333333333
Workaround
Currently, there is no workaround for this.
- mentioned in
-
Page Failed to load
Form Name |
---|
[JSDSERVER-15162] Jira clean reindex process on single node DC throws 503
Remote Link | New: This issue links to "Page (Confluence)" [ 939669 ] |
Assignee | New: Benjamin Suess [ c8bcca445054 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Needs Triage [ 10030 ] | New: Closed [ 6 ] |
Fix Version/s | New: 5.12.0 [ 105722 ] |
Support reference count | New: 1 |
Description |
Original:
h3. Issue Summary
User faces 503 error while performing full re-indexing. This error don't have any impact on the full reindexing process. But an inconvenience to the customer. This is reproducible on Data Center: yes h3. Steps to Reproduce The issue is reproducible at customer's end. But not reproducible at our end. # Set up a single-node DC instance. # Run a clean reindex process. h3. Expected Results No errors are thrown on the screen while reindex is going on. h3. Actual Results The user faces 503 error on the screen, while the call is being made to {code:java} https://<base_url>rest/insight/1.0/global/config?_=33333333333333{code} !Screenshot 2024-03-05 at 1.28.06 PM.png|thumbnail! h3. Workaround Currently, there is no workaround for this. |
New:
h3. Issue Summary
User faces 503 error while performing full re-indexing. This error doesn't have any impact on the full reindexing process. But an inconvenience to the customer. This is reproducible on the customer's end. But not on our end. h3. Steps to Reproduce The issue is reproducible at the customer's end. But not reproducible at our end. # Set up a single-node DC instance. # Run a clean reindex process. h3. Expected Results No errors are thrown on the screen while reindex is going on. h3. Actual Results The user faces 503 error on the screen, while the call is being made to {code:java} https://<base_url>rest/insight/1.0/global/config?_=33333333333333{code} !Screenshot 2024-03-05 at 1.28.06 PM.png|thumbnail! h3. Workaround Currently, there is no workaround for this. |