Details
-
Sub-task
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
None
-
None
Description
Turns out the cause is somewhat related to keep alive in that we can't always expect NiFi to close the connection within a reasonable amount of time. It could be upwards of 5-10 seconds before the HTTP connection is severed. This may be a function of my overloaded test environment, but since this is a problem that impacts large files, we should account for it and wait until the connection is severed.