Github user ijokarumawak commented on the issue:
https://github.com/apache/nifi/pull/575
@JPercivall Thanks for reviewing this.
For the 1st comment:
I didn't notice that it's failing Travis test... I'll check what caused the
error. Thanks for pointing that.
For the 2nd and last comment:
> When running clustered and monitoring on the cluster, it needs to take
into account generating the inactive flowfiles in a cluster friendly way as
well. Currently each Node will generate a flowfile when the inactivity time
hits. Probably need to track in clustered state whether or not a marker has
been sent.
I wrote onTrigger like that intentionally, because I thought there're
use-cases in which user would like to do something on each node when NiFi went
inactive or recovered activity. If one would like to get notification flow-file
only on a single node in the cluster, then they can use `On primary node`
scheduling strategy. Excuse me if I misunderstood your comments, but does this
address your concern?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---