Member since
04-10-2017
3
Posts
0
Kudos Received
0
Solutions
04-11-2017
08:01 AM
Hi @Wynner , I found something similar to this suggestion yesterday, but thank you. I do have a follow question from an issue I noticed this morning. So I attempted to use a cron schedule to kick off the MonitorActivity which I specified to run 1 minute after the ListDataTables. I thought this was a good way to implement it. Checking the flow this morning, it seems only 50 out of the 800 flowfiles (800 tables from source DB) got through to success while the others just sat in the queue. I guess this must be some limitation on MonitorActivity's part when scheduled through a cron expression. Would the best way to implement this processor be to set the Threshold Duration to 24hrs (from an hour after the flow should have run) as the flow is daily batch?
... View more
04-10-2017
03:59 PM
Hi, We are kicking off a NiFi flow with the ListDatabaseTables processor and we experienced an incident where this processor failed to run. This was due to a network adapter error which seems to have been caused by a restart to NiFi, re-enabling the controller service fixed this issue. However, this is a scheduled job and I would like the flow to be able to respond to an error. The ListDatabaseTables processor will not produce a flowfile when it fails, it has no failure path. Is there a way in which I could add a cron driven processor to send an email if a flowfile doesn't flow through it by a certain time? I can't think of any other solutions that could be possible within NiFi. Any ideas would be appreciated. Thanks, Peter
... View more
Labels:
- Labels:
-
Apache NiFi