You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2024/08/27 17:40:00 UTC
[jira] [Commented] (NIFI-13684) Set Runtime Cluster Status Response Code based on Connection
[ https://issues.apache.org/jira/browse/NIFI-13684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17877117#comment-17877117 ]
ASF subversion and git services commented on NIFI-13684:
--------------------------------------------------------
Commit e9f84083ebdeceee17c40f143c2ced4bd5395896 in nifi's branch refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=e9f84083eb ]
NIFI-13684 Set Cluster Status HTTP Code based on Connection (#9202)
> 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
> 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)