[NIFI-1336] PostHTTP does not route to failure in case of Connection failure

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.8.0
• Component/s: Extensions
• Assignee: Andre F de Miranda
• Reporter: Mark Payne
• Created: 29/Dec/15 14:12
• Updated: 25/Mar/21 18:13
• Resolved: 25/Mar/21 18:13

Description

When unable to communicate with a remote NiFi instance, PostHTTP continually rolls back the session (without penalizing) instead of routing to failure. This results in filling the logs with messages like:

2015-12-29 14:09:02,023 WARN [Timer-Driven Process Thread-11] o.a.nifi.processors.standard.PostHTTP PostHTTP[id=015d5ace-3aa3-3e51-8aae-4776d3bd3897] Failed to delete Hold that destination placed on [StandardFlowFileRecord[uuid=220fbcac-d84e-41ed-9cc7-6e558ea207ee,claim=StandardContentClaim [resourceClaim=StandardResourceClaim[id=1451397424256-4, container=pub1, section=4], offset=52418, length=19672005],offset=0,name=GeoLite2-City.mmdb.gz,size=19672005]] due to org.apache.http.conn.HttpHostConnectException: Connect to processing-3:5000 [processing-3/172.172.172.172] failed: Connection refused: org.apache.http.conn.HttpHostConnectException: Connect to processing-3:5000 [processing-3.demo.onyara.com/172.172.172.172] failed: Connection refused

Issue Links

• is fixed by: NIFI-5275 PostHTTP - Hung connections and zero reuse of existing connections
• links to: GitHub Pull Request #1642
• links to: GitHub Pull Request #1642