-
Suggestion
-
Resolution: Fixed
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Problem Definition
The URL that is suggested for use in JIRA Data Center behind a load balancer, as mentioned in https://confluence.atlassian.com/display/ENTERPRISE/JIRA+Data+Center+Load+Balancer+examples states to use /status and it will return "state":"RUNNING" for a healthy node that should be in the LB pool. In my testing, I found that when a node is performing a foreground re-index that locks JIRA, it is actually unavailable for processing user requests. Accessing a node that is performing a locking re-index redirects to an error page and gives an HTTP 503. When that is occurring, I would not want that node to have user requests routed to it.
Suggested Solution
Having multiple nodes for JIRA Data Center, we like foreground re-indexing as it is much faster with the amount of data we have. So when a node is locked for re-indexing we'd like it to take itself out of the pool. This issue is to suggest either:
- the /status page be updated to provide a different status during indexing, possibly "state":"INDEXING". This would allow a LB health check to take the node out of the pool during indexing
- update the Data Center LB documentation (above) to instruct users to use /secure/errors.jsp as the health check URL as it more accurately conveys whether a node is capable of servicing requests
- is related to
-
- Closed
-
- Gathering Interest
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRACLOUD-46458] JIRA Data Center health check status URL doesn't accommodate for foreground indexing
| Workflow | Original: JAC Suggestion Workflow [ 3154181 ] | New: JAC Suggestion Workflow 3 [ 3655895 ] |
| Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2330112 ] | New: JAC Suggestion Workflow [ 3154181 ] |
| Component/s | New: System Administration [ 46544 ] | |
| Component/s | Original: System Administration - Support Tools [ 46610 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 2100993 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2330112 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2072851 ] | New: JIRA Bug Workflow w Kanban v6 [ 2100993 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 1867447 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2072851 ] |
| Description |
Original:
h3. Problem Definition The URL that is suggested for use in JIRA Data Center behind a load balancer, as mentioned in https://confluence.atlassian.com/display/ENTERPRISE/JIRA+Data+Center+Load+Balancer+examples states to use {{/status}} and it will return {{"state":"RUNNING"}} for a healthy node that should be in the LB pool. In my testing, I found that when a node is performing a *foreground re-index* that locks JIRA, it is actually unavailable for processing user requests. Accessing a node that is performing a locking re-index redirects to an error page and gives an HTTP 503. When that is occurring, I would not want that node to have user requests routed to it. h3. Suggested Solution Having multiple nodes for JIRA Data Center, we like foreground re-indexing as it is much faster with the amount of data we have. So when a node is locked for re-indexing we'd like it to take itself out of the pool. This issue is to suggest either: * the /status page be updated to provide a different status during indexing, possibly {{"state":"INDEXING"}}. This would allow a LB health check to take the node out of the pool during indexing * update the Data Center LB documentation (above) to instruct users to use {{/secure/errors.jsp}} as the health check URL as it more accurately conveys whether a node is capable of servicing requests |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Cloud*. Using *JIRA Server*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRASERVER-46458]. {panel} h3. Problem Definition The URL that is suggested for use in JIRA Data Center behind a load balancer, as mentioned in https://confluence.atlassian.com/display/ENTERPRISE/JIRA+Data+Center+Load+Balancer+examples states to use {{/status}} and it will return {{"state":"RUNNING"}} for a healthy node that should be in the LB pool. In my testing, I found that when a node is performing a *foreground re-index* that locks JIRA, it is actually unavailable for processing user requests. Accessing a node that is performing a locking re-index redirects to an error page and gives an HTTP 503. When that is occurring, I would not want that node to have user requests routed to it. h3. Suggested Solution Having multiple nodes for JIRA Data Center, we like foreground re-indexing as it is much faster with the amount of data we have. So when a node is locked for re-indexing we'd like it to take itself out of the pool. This issue is to suggest either: * the /status page be updated to provide a different status during indexing, possibly {{"state":"INDEXING"}}. This would allow a LB health check to take the node out of the pool during indexing * update the Data Center LB documentation (above) to instruct users to use {{/secure/errors.jsp}} as the health check URL as it more accurately conveys whether a node is capable of servicing requests |
| Link |
New:
This issue is related to |
| Project Import | New: Sat Apr 01 19:36:47 UTC 2017 [ 1491075407146 ] |