Hi again, Sorry this appears to be my fault - I didn't realise that ExecuteStreamCommand penalises failed flowfiles, adjusting the penalty time in the processor has fixed the problem.
Thanks, Mandeep On Wed, 5 Dec 2018 at 11:39, Mandeep Gill <[email protected]> wrote: > Hi there, > > I'm having an issue when routing a flowfile from ExecuteStreamCommand > using the non-zero relationship. On a running a successful command, the > flowfile on the output stream passes on and there is no issue. However, on > a non-zero exit, the flowfile gets stuck when entering the next processor > and takes around 1.5M task slices before it's sent through. > > I've attached a screenshot demonstrating a sample flow and the > corresponding template, this when using NiFi 1.8.0 on Linux & OpenJDK > 1.8.0_191-b12. > > Any help / pointers would be appreciated - cheers! > Mandeep >
