Juan, How full is your disk that holds your content repository? The issue that Joe mentioned, I don’t think, will cause what you’re seeing. But I am guessing that your content repository is exerting back pressure.
Can you check your logs for the message "Unable to write to container"? I am guessing that you will see a message along the lines of: 2021-03-18 10:26:20,988 INFO [Timer-Driven Process Thread-10] o.a.n.c.repository.FileSystemRepository Unable to write to container default due to archive file size constraints; waiting for archive cleanup This would indicate that your content repository is filling up and is exerting backpressure on the Input Port, which prevents it from writing the data out. This can potentially result in the transfer timing out. By default, the content repository exerts backpressure if the disk is 50% full. This can be configured in nifi.properties: nifi.content.repository.archive.max.usage.percentage=50% Thanks -Mark On Mar 17, 2021, at 11:58 PM, Joe Witt <[email protected]<mailto:[email protected]>> wrote: Thanks Juan - that would be very valuable actually. I'll send you a link to a build here in an hour or so. If you can test that and let us know that will help us with the release candidate voting process quite a bit. Thanks On Wed, Mar 17, 2021 at 8:49 PM Juan Pablo Gardella <[email protected]<mailto:[email protected]>> wrote: Wow that is fast! You are awesome, thanks Joe. I will test it. Juan On Thu, 18 Mar 2021 at 00:47, Joe Witt <[email protected]<mailto:[email protected]>> wrote: Juan We found a bug in 1.13.1 today as reported here https://issues.apache.org/jira/browse/NIFI-8337 and https://issues.apache.org/jira/browse/NIFI-8334. We will have a 1.13.2 out asap to fix this and the regression now has tests to prevent it in the future. Thanks Joe On Wed, Mar 17, 2021 at 8:44 PM Juan Pablo Gardella <[email protected]<mailto:[email protected]>> wrote: Hi all, I am using latest nifi version and SplitRecord works only once and then hangs: <image.png> I cannot stop it also. Juan
