[ 
https://issues.apache.org/jira/browse/NIFI-13684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bryan Bende updated NIFI-13684:
-------------------------------
    Fix Version/s: 2.0.0-M5
       Resolution: Fixed
           Status: Resolved  (was: Patch Available)

> Set Runtime Cluster Status Response Code based on Connection
> ------------------------------------------------------------
>
>                 Key: NIFI-13684
>                 URL: https://issues.apache.org/jira/browse/NIFI-13684
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>            Reporter: David Handermann
>            Assignee: David Handermann
>            Priority: Major
>             Fix For: 2.0.0-M5
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Recent improvements to the bootstrap and runtime process handling including 
> the introduction of an HTTP management server to return application health 
> and status.
> The {{/health/cluster}} path returns different status values based on cluster 
> connection status, but the initial implementation returns HTTP 200 regardless 
> of the connection status. This behavior should be changed to return more 
> specific HTTP response codes for unhealthy connection states, such that 
> connected and connecting status continue to return HTTP 200, but other states 
> return an error code of HTTP 503.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to