How to turn on GTID on MariaDB if already using binary/position replication?

MariaDB 10.3

current master config

[mysqld]
log-bin
server_id=1
binlog-format=mixed
expire_logs_days=10

current slave config

[mysqld]
log-bin
server_id=2
binlog-format=mixed
expire_logs_days=10

I can stop both master and slave if needed for changing replication method.

So questions are:

  1. Do I need to stop replication and application and then execute “CHANGE MASTER TO MASTER_USE_GTID = slave_pos” Is it enough? Should I purge bin logs?
  2. If so how do slave knows about where master server is?
  3. Should I changed binlog-format to “row”?

Go to Source
Author: GarfieldCat

Can InnoDB data at rest encryption be overriden

I am exploring options for distributing a MySQL/MariaDB database with my app. I want to ensure users (even the root user) cannot view or manipulate data in my database/tables. Recent releases of MySQL and MariaDB have data-at-rest capabilities:

MariaDB
https://mariadb.com/kb/en/mariadb/why-encrypt-mariadb-data/

MySQL 5.7.11 comes with InnoDB tablespace encryption
https://dev.mysql.com/doc/refman/5.7/en/innodb-tablespace-encryption.html

But what is not clear to me is: Can the MySQL root user reset the encryption password on my database/tables to view or manipulate the contents?

Go to Source
Author: TSG