December 2017 - discuss - lists.mariadb.org

[Maria-discuss] why stdout? -> [Note] /usr/libexec/mysqld (mysqld 10.0.20-MariaDB) starting as process 115096
by Reindl Harald 05 Jul '20

05 Jul '20

Aug 6 12:24:24 testserver mysqld: 150806 12:24:24 [Note] /usr/libexec/mysqld (mysqld 10.0.20-MariaDB) starting as process 115096 ... why is this now stdout instead mysql logs? on systemd based distributions that spits now to the global syslog and finally on machines restarting 2 instances every hour for backup reasons it annoys until 10.0.19 or 10.0.20 that was not this way

5 13

[Maria-discuss] Charsets and collations
by Peter Laursen 20 Apr '18

20 Apr '18

Does anybody know if there are any plans to bring collations added in MySQL 8 - refer http://mysqlserverteam.com/new-collations-in-mysql-8-0-0/ - to MariaDB and are there any plans to change the default charset to a unicode-based one? -- Peter -- Webyog

2 2

[Maria-discuss] Replication Upgrade Strategy MySQL 5.6 to MariaDB 10.2
by Michael Caplan 29 Dec '17

29 Dec '17

Hello, Am hoping to get some feedback on an upgrade strategy to go from MySQL 5.6 (two separate servers, one replication slave) to MariaDB 10.2 (installed on new servers). I'm looking at an rsync process to seed the two new instances on MariaDB, and am unsure if this is sound (https://www.stephenrlang.com/2016/08/setting-up-mysql-master-slave-replicat…). Roughly, the process would look like this: - rsync data from MySQL 5.6 Master to MariaDB 10.2 Slave - Lock master - Get master status - Refresh rsync - Remove lock - Run upgrade process on MariaDB 10.2 Slave. - Change MASTER.... on MariaDB 10.2 Slave - Create second MariaDB 10.2 Slave from first MariaDB 10.2 Slave - Promote MariaDB 10.2 Slave to Master (redirect all DB traffic at this point) - Redirect other MariaDB 10.2 Slave to new Master - Shutdown MySQL 5.6 servers. What I'm most concerned about is the viability of rsync as a method to seed the new MariaDB server from MySQL 5.6. I've come across some chatter that there are risks using rsync instead of a proper dump and restore. Can anyone comment on this? Thanks, Mike

2 3

[Maria-discuss] WSREP: BF lock wait long
by Jesus 22 Dec '17

22 Dec '17

Hi I'm getting this message almost daily or even more and I must restart the server that generates it: WSREP: BF lock wait long How can I solve this? Thanks for your help

2 3

Re: [Maria-discuss] About data encryption
by Sergei Golubchik 15 Dec '17

15 Dec '17

Hi, Cesar! On Dec 15, Cesar Hernandez wrote: > > Thanks Sergei! > > So the database is encrypted by using AES-128-CBC or AES-128-CRT, right? > Can I use AES-256-CBC? No. Each tablespace is encrypted with a different per-tablespace key. This key is 128 bit. It's generated by encrypting a random 128-bit nonce with the user-specified key. So, if you specify a 256-bit key in the file_key_manager plugin, this 256-bit key will be used to generate the 128-bit tablespace key. The tablespace itself will be encrypted using the 128-bit key. Regards, Sergei Chief Architect MariaDB and security(a)mariadb.org

1 0

[Maria-discuss] About data encryption
by Cesar Hernandez 14 Dec '17

14 Dec '17

Hi Can someone tell me which algorithm uses MariaDB when using table encryption? Looking at https://mariadb.com/kb/en/library/data-at-rest-encryption/ <https://mariadb.com/kb/en/library/data-at-rest-encryption/> Seems to talk only about encryption of the key file, but not on the database data. I've been looking for a while and haven't found complete documentation about it. I've even taken a look at the MariaDB source code, in the file /storage/innobase/fil/fil0crypt.cc <http://fil0crypt.cc/> Seems the encryption is done by AES algorithm, but I'm not sure, and I don't know the key size neither the mode of operation. Thanks Cesar

2 1