[NIFI-6317] HandleHttpRequest timeout handling issues

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.10.0
• Component/s: Extensions
• Assignee: Peter Turcsanyi
• Reporter: Peter Turcsanyi
• Created: 24/May/19 08:26
• Updated: 17/Nov/21 14:22
• Resolved: 24/May/19 18:45

Description

The request timeout can be configured on StandardHttpContextMap and expired requests are handled by a cleanup thread periodically.
The scheduling of this thread calculated as 'request timeout / 2' which is quite infrequent if the user configures a higher timeout value (and even with the default 1 min too). The expired requests stay in the cache more time than necessary and new requests can be rejected because the cache is full.
A shorter period should be used for the thread scheduling.

The same timeout is used in HandleHttpRequest currently. Originally it was Long.MAX_VALUE, but it caused memory leak that has been fixed in NIFI-4858.
On the other hand, the current timeout setting fires the request again when timeout expires (and before the cleanup thread could remove the request) and a new FF gets generated (which makes the situation even worse in a busy flow where timeouts occur).
The timeout should be set to 0 which disables the timeout handling at all in HandleHttpRequest (no scheduler tasks will be generated).

Issue Links

• fixes: NIFI-6697 HandleHttpRequest - 500, stopping does not works
• relates to: NIFI-4858 HandleHttpRequest has a memory leak
• links to: GitHub Pull Request #3490