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

RaymondYap updated NIFI-8321:
-----------------------------
    Description: 
* The RemoteProcessGroup will consumer lots of resources if the other side of 
NiFi Cluster disappears (host suddenly shutdown/ instance shutdown 
terminate...).

* 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

  was:
* The RemoteProcessGroup will consumer lots of resources if the other side of 
NiFi Cluster disappears (host suddenly shutdown/ instance shutdown 
terminate...).

* 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 


> 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: 10m
>  Remaining Estimate: 23h 50m
>
> * The RemoteProcessGroup will consumer lots of resources if the other side of 
> NiFi Cluster disappears (host suddenly shutdown/ instance shutdown 
> terminate...).
> * 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.3.4#803005)

Reply via email to