Actullay the server id is unique and it is scheduled only on primary node By using iftop tool on the nifi side, i see more than one tcp connection between the mysql sever and the nifi server. Even i stop the CaptureChangeMySQL processor, the tcp connection still exists. Looking the nifi-app.log:
2019-09-12 14:45:50,725 INFO [blc-keepalive-192.168.114.118:3306] c.g.shyiko.mysql.binlog.BinaryLogClient Trying to restore lost connection to 192.168.114.118:3306 2019-09-12 14:45:50,904 INFO [blc-192.168.114.118:3306] c.g.shyiko.mysql.binlog.BinaryLogClient Connected to 192.168.114.118:3306 at mysql-bin.000675/707993476 (sid:10091, cid:5560080) I have stopped the processor, why it still retry to connect to mysql server? Thanks, Lei wangl...@geekplus.com.cn From: Williams, Jim Date: 2019-09-11 21:42 To: us...@nifi.apache.org Subject: RE: CaptureChangeMySQL throws communication failure error every 30 seconds Lei, Is this flow being run on a cluster? I’ve not worked with this processor. It seems possible that if the processor is scheduled to run every thirty seconds and is not restricted to run on the primary node of the cluster that this sort of message might occur. Warm regards, Jim Williams | Principal Database Developer O: +1 713.341.7812 | C: +1 919.523.8767 | jwilli...@alertlogic.com | alertlogic.com From: Matt Burgess <mattyb...@apache.org> Sent: Wednesday, September 11, 2019 8:34 AM To: us...@nifi.apache.org Subject: Re: CaptureChangeMySQL throws communication failure error every 30 seconds Lei, This is most likely due to a duplicate Server ID, each instance of the client and server needs a unique ID or you will see errors like this. Set the "Server ID" property in CaptureChangeMySQL to some random integer (like 42 :) and that should remove the errors. Regards, Matt On Mon, Sep 9, 2019 at 11:35 AM wangl...@geekplus.com.cn <wangl...@geekplus.com.cn> wrote: Seems this error accurs every 30 sedonds Any insight on this? Thanks, Lei wangl...@geekplus.com.cn
