The RocketMQ-MySQL is a data replicator between MySQL and other systems. The replicator simulates a MySQL slave instance, parses the binlog event and sends it to RocketMQ in json format. Besides MySQL, other systems can also consume data from RocketMQ. With the RocketMQ-MySQL Replicator, more systems can easily process data from MySQL binlog at a very low cost.
key | nullable | default | description |
---|---|---|---|
mysqlAddr | false | MySQL address | |
mysqlPort | false | MySQL port | |
mysqlUsername | false | username of MySQL account | |
mysqlPassword | false | password of MySQL account | |
mqNamesrvAddr | false | RocketMQ name server address (e.g.,127.0.0.1:9876) | |
mqTopic | false | RocketMQ topic name | |
startType | true | DEFAULT | The way that the replicator starts processing data,there are four options available: - DEFAULT: try to start processing data in the “LAST_PROCESSED” way,if failed, then in the “NEW_EVENT” way - LAST_PROCESSED: starts processing data from the last processed event - NEW_EVENT: starts processing data from the tail of binlog - SPECIFIED: starts processing data from the position that user specified,if you choose this option,the binlogFilename and nextPosition must not be null |
binlogFilename | true | If “startType” is “SPECIFIED”,the replicator will begin to replicate from this binlog file | |
nextPosition | true | If “startType” is “SPECIFIED”,the replicator will begin to replicate from this position | |
maxTransactionRows | true | 100 | max rows of the transaction pushed to RocketMQ |