nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "" <>
Subject Can CaptureChangeMySQL be scheduled to all nodes instead of primary node?
Date Wed, 09 Oct 2019 05:58:40 GMT
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 primary node.

Is there any method than i can  distribute the CaptureChangeMySQL processors to all nodes
instead of only to primary node?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message