Hi I am new to NIFI and practice it as my hobby. I would like to know if there is a setting or anything on the anvil , for NIFI to terminate a processor automatically if it encountered run time errors not under the processor’s control , as in memory shortage, errors due to issues in custom code, thread hang-ups or disk space shortages and the like. Most of these result in bulletin messages and result in the flow not progressing beyond this point.
Typically I have tended to clear-up the queues , and stop the processor manually and at worse had to restart NIFI and remove custom processor’s from the flow. In some cases I had to deal with password changes on database connectivity areas , which is trivial , but still had no way of bailing out gracefully. Right now I see success and failure as one of the options which I can connect to on each of the processor’s , but it seems there is no way a hung processor or a processor in distress can give up control to failure after some time. It would be great if there was an signal/event generated with its associated message or stack trace , which could be bound to an exit point for routing it over , seeking attention. I would appreciate any clues on this topic, as I see quite a lot of articles on retrieving bulletin messages and the like, but am yet to come across one which is about this topic. Once again this is not a production issue I am facing , it is just some curiosity on NIFI flows. Regards c.kannan
