[
https://issues.apache.org/jira/browse/NIFI-8321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard resolved NIFI-8321.
----------------------------------
Resolution: Feedback Received
Apache NiFi 1.x is no longer maintained and no new release is planned on the
1.x release line. Marking as resolved as part of a cleanup operation. Please
open a new one with an updated description if this is still relevant for NiFi
2.x.
> Either add an IOException or a NoRouteToHostException on HttpClient
> --------------------------------------------------------------------
>
> Key: NIFI-8321
> URL: https://issues.apache.org/jira/browse/NIFI-8321
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.12.1
> Reporter: RaymondYap
> Priority: Minor
> Original Estimate: 24h
> Time Spent: 0.5h
> Remaining Estimate: 23.5h
>
> * The RemoteProcessGroup will consumer lots of resources if the other side of
> NiFi Cluster disappears (host suddenly shutdown/ instance shutdown
> terminate...).
> * "NoRouteToHostException" => when a host/instance suddenly shutdown or
> remove..., but the RemoteProcessGroup still enable or working.
> * Because of the HttpClient lack of "NoRouteToHostException" exception.
> * Although the HttpClient has thrown an "IOException" and the
> "StandardRemoteGroupPort", has caught the "IOException"
> * but the HttpClient never throw "NoRouteToHostException", therefore,
> "StandardRemoteGroupPort" will never catch the exception and still try to
> create an HTTP connection
> * Therefore, either add an IOException or NoRouteToHostException on HttpClient
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
