Hi Lei,
I don't know any NiFi built-in feature to achieve that.
To distribute CaptureChangeMySQL load among nodes, I'd deploy separate
standalone NiFi (or even MiNiFi Java) in addition to the main NiFi
cluster for the main data flow.
For example, if there are 5 databases and 3 NiFi nodes, deploy
I am using CaptureChangeMySQL to replicate the database.
There are many data sources and so there're many CaptureChangeMySQL processors.
The CaptureChangeMySQL throws same slave id error if scheduled on all nodes.
So it can only be scheduled on primary node. This causes very heavy load on
the
