Hello,
Instead of implementing another lock within NiFi, I suggest
investigating the reason why the primary node changed.
NiFi uses Zookeeper election to designate a node to be the primary node.
If a primary node's Zookeeper session timed out, Zookeeper elects
another node to take over the primary
I have small cluster with 3 instances of NiFi, and found some problem, as I
think.
Processor QueryDatabaseTable set to work on PrimaryNode only and Concurent
tasks set to 1. Run Schedule set to large value (something like 20
minutes), so I expect only one execution at a time. While query is
execute
