mysql-replication | MySQL master-slave replication | Continuous Deployment library

We are using a Galera cluster for MySQL 5.6.
We have been using python mysql replication client (https://github.com/noplay/python-mysql-replication) to keep track of all changes to DB mainly for debugging. This used to work fine. We got data that looked like following:

I am trying to create a read-only slave on an existing database. I managed to export my data, put it into a bucket, remove all the lines with DEFINER clause and successfully create a replica database.

Here is my dump command-

Is there any way to capture 'on delete cascade' events? I have read in the Debezium faq (at the bottom of the page):

== Why don't I see DELETE events in some cases?

This may be caused by the usage of CASCADE DELETE statements. In this case the deletion events generated by the database https://dev.mysql.com/doc/refman/5.7/en/innodb-and-mysql-replication.html [are not part of the binlog] and thus cannot be captured by Debezium.

I appreciate a similar behaviour with 'ON UPDATE CASCADE'

If that events are not part of the binlog I understand that Debezium cannot capture it but, Is there any easy alternative way to do it? In a database this is very important.

I am trying to setup a sync between AWS Aurora and Redshift. What is the best way to achieve this sync?

Possible ways to sync can be: -

1. Query table to find changes in a table(since I am only doing inserts, updates don't matter), export these changes to a flat file in S3 bucket and use Redshift copy command to insert into Redshift.

2. Use python publisher and Boto3 to publish changes into a Kinesis stream and then consume this stream in Firehose from where I can copy directly into Redshift.

3. Use Kinesis Agent to detect changes in binlog (Is it possible to detect changes int binlog using Kinesis Agent) and publish it to Firehose and from there copy into Firehose.

I haven't explored AWS Datapipeline yet.

I am working with a project, i need to watch binlog event, iterator rows, and do something.In my local enviroment ,I tested my codes and everything worked,I can get events and rows in each event.However, after moved to production-enviroment and connected to another database,I can only get bingo event,but there were no rows in any events. I used python-mysql-replication,i dumped all binlog-event i received,each of them in like below:

I have 1 master-slave replication and at the same time the slave is master for a MariaDB cluster which will be replacing the actual two DB servers. everything looks fine but the master position on the slave hasn't updated since the cluster was set up the last month.

Slave is doing ok writing from the Master server but the cluster has not been updated ever since.In fact no errors can be observed but noticed the cluster is just the same it was set up since the beginning.

I know that cluster not wirtting new data ha to do with the mater position on the slave.

So the question would be why the master position on the slave is not updating?

On my MASTER

mysql> show master status\G;

*************************** 1. row ***************************

File: mysql-bin.000775

Position: 6593494

Binlog_Do_DB:

Binlog_Ignore_DB: mysql,performance_schema,phpmyadmin,information_schema

1 row in set (0.00 sec)

On my SLAVE:

MariaDB [(none)]> show slave status\G;

*************************** 1. row ***************************

Slave_IO_State: Waiting for master to send event

Master_Host: master_IP

Master_User: replication

Master_Port: 3306

Connect_Retry: 10

Master_Log_File: mysql-bin.000775

Read_Master_Log_Pos: 4192372

Relay_Log_File: slave-relay-bin.002921

Relay_Log_Pos: 2315832

Relay_Master_Log_File: mysql-bin.000775

Slave_IO_Running: Yes

Slave_SQL_Running: Yes

Also on the SLAVE

MariaDB [(none)]> show master status\G;

*************************** 1. row ***************************

File: mysql-replication.000003

Position: 342

Binlog_Do_DB:

Binlog_Ignore_DB:

1 row in set (0.00 sec)

On the CLUSTER

MariaDB [none]> show slave status\G;

*************************** 1. row ***************************

Slave_IO_State: Waiting for master to send event

Master_Host: slave_IP

Master_User: replica

Master_Port: 3306

Connect_Retry: 10

Master_Log_File: mysql-replication.000003

Read_Master_Log_Pos: 342

Relay_Log_File: cluster-relay-bin.000004

Relay_Log_Pos: 645

Relay_Master_Log_File: mysql-replication.000003

Slave_IO_Running: Yes

Slave_SQL_Running: Yes