- discuss - lists.mariadb.org

[Maria-discuss] Current Kernel/Distro with best support for performance/stability for VMs (HyperV)
by Alexandre hadjinlian guerra 01 Nov '17

01 Nov '17

Hi I've been looking for improvements in block device handling / XFS filesystem on linux kernel and it looks like that on Kernel 4.11 there is some interesting improvements Im looking to settle on a newer distro/kernel which supports MariaDB 10.2 and ColumnStore and have a long term support. its a new deployment Thanks

1 0

[Maria-discuss] MariaDB 10.2 'show engine innodb status' format change for Pending AIO
by Jonathan Nicol 31 Oct '17

31 Oct '17

Hi, Starting with 10.2, in 'show engine innodb status', the format has changed for pending reads/writes... The old (pre-5.5) format looked like: Pending normal aio reads: 0, aio writes: 0, In 5.5 it switched to: Pending normal aio reads: 0 [0, 0, 0, 0] , aio writes: 0 [0, 0, 0, 0] , (where each value in the brackets corresponds to a read or write thread) Now in 10.2 it looks like: Pending normal aio reads: [0, 0, 0, 0] , aio writes: [0, 0, 0, 0] , I was never clear on what the values outsides the brackets in 5.5-10.1 represented... assumed it was a total of all threads. We were previously monitoring this value, should we move forward monitoring a sum of all threads? It seems a little odd to remove a useful metric from the status output. thanks Jon

1 0

Re: [Maria-discuss] upgrading from 10.1 -> 10.2 with galera cluster
by Jeff Dyke 31 Oct '17

31 Oct '17

Thanks for the tip, that will be helpful for sure. I'm about to set it up on three aws instances and see what happens. Perhaps i can contribute my learnings to the ticket you opened. Best, Jeff On Tue, Oct 31, 2017 at 2:20 PM, Chris Calender <chris.calender(a)mariadb.com> wrote: > Hi Jeff, > > Be sure you have upgraded Xtrabackup to 2.4, or if one of the 10.2 needs > to SST, it will fail with an "No valid checkpoint found" error (as > Xtrabackup 2.3 is not 100% compatible with MariaDB 10.2): > > https://jira.mariadb.org/browse/MDEV-13657 > > Also, I did file a documentation request about this topic last light, if > interested (though you might have this implemented before the page is > added): > > https://jira.mariadb.org/browse/MDEV-14226 > > Hope this helps. > > Best wishes, > Chris > > > > On 10/31/2017 10:09 AM, Jeff Dyke wrote: > >> I have a 10.1 install of galera cluster running in master master mode, i >> would like to upgrade to 10.2.9, and have seen the instructions here[1] >> about "regular" updates, but i'd like to keep the cluster online while i >> upgrade. Is there any difference or things to look out for to keep data >> consistency. can a 10.2 node replicate to a 10.1 node (my guess would be >> no due to the new fields after mysql_upgrade) Downtime offline is a >> possibility, but i'd like to avoid it, as would anyone. >> >> Any hints/links are greatly appreciated. >> Jeff >> >> [1] https://mariadb.com/kb/en/library/upgrading-from-mariadb- >> 101-to-mariadb-102/ >> >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~maria-discuss >> Post to : maria-discuss(a)lists.launchpad.net >> Unsubscribe : https://launchpad.net/~maria-discuss >> More help : https://help.launchpad.net/ListHelp >> >> > > -- > Chris Calender, M.S., Technical Support Manager > MariaDB Corporation >

1 0

[Maria-discuss] upgrading from 10.1 -> 10.2 with galera cluster
by Jeff Dyke 31 Oct '17

31 Oct '17

I have a 10.1 install of galera cluster running in master master mode, i would like to upgrade to 10.2.9, and have seen the instructions here[1] about "regular" updates, but i'd like to keep the cluster online while i upgrade. Is there any difference or things to look out for to keep data consistency. can a 10.2 node replicate to a 10.1 node (my guess would be no due to the new fields after mysql_upgrade) Downtime offline is a possibility, but i'd like to avoid it, as would anyone. Any hints/links are greatly appreciated. Jeff [1] https://mariadb.com/kb/en/library/upgrading-from-mariadb-101-to-mariadb-102/

1 0

[Maria-discuss] Aria_pack error
by Kenneth Penza 27 Oct '17

27 Oct '17

Good afternoon, I am currently working on MariaDB version 10.1.26-MariaDB-1~yakkety running on Ubuntu 16.10 and have encountered an error whilst using aria_pack. The process used to generate the tables is as follows: 1) create table SQL script 2) shutdown MariaDB (systemctl shutdown mariadb.service) 3 )Disable indexes to speedup loading $ aria_chk --keys-used=0 -rq /var/lib/mysql/mygo/term - recovering (with keycache) Aria-table '/var/lib/mysql/mygo/term' Data records: 0 Table: /var/lib/mysql/mygo/term doesn't have an auto increment key State updated 4) startup MariaDB (systemctl start mariadb.service) 5) load data $ mysqlimport -u penzk001 --password=penzk100 -L mygo term.txt mygo.term: Records: 46032 Deleted: 0 Skipped: 0 Warnings: 0 6) shutdown mariadb (systemctl shutdown mariadb.service) 7) Check table $ aria_chk /var/lib/mysql/mygo/term Checking Aria file: /var/lib/mysql/mygo/term Data records: 46032 Deleted blocks: 0 - check file-size - check key delete-chain - check index reference - check record links State update 8) Compress table $ aria_pack /var/lib/mysql/mygo/term Compressing /var/lib/mysql/mygo/term.MAD: (46032 records) - Calculating statistics - Compressing file Segmentation fault (core dumped) When I run steps 1, 5 and 8 I get the following error message: $ aria_pack /var/lib/mysql/mygo/term /var/lib/mysql/mygo/term gave error 132 on open Am I doing something wrong? Any pointers what I can check? Thanks

1 0

[Maria-discuss] Aria_pack error
by Kenneth Penza 27 Oct '17

27 Oct '17

Good afternoon, I am currently working on MariaDB version 10.1.26-MariaDB-1~yakkety running on Ubuntu 16.10 and have encountered an error whilst using aria_pack. The process used to generate the tables is as follows: 1) create table SQL script 2) shutdown MariaDB (systemctl shutdown mariadb.service) 3 )Disable indexes to speedup loading $ aria_chk --keys-used=0 -rq /var/lib/mysql/mygo/term - recovering (with keycache) Aria-table '/var/lib/mysql/mygo/term' Data records: 0 Table: /var/lib/mysql/mygo/term doesn't have an auto increment key State updated 4) startup MariaDB (systemctl start mariadb.service) 5) load data $ mysqlimport -u penzk001 --password=penzk100 -L mygo term.txt mygo.term: Records: 46032 Deleted: 0 Skipped: 0 Warnings: 0 6) shutdown mariadb (systemctl shutdown mariadb.service) 7) Check table $ aria_chk /var/lib/mysql/mygo/term Checking Aria file: /var/lib/mysql/mygo/term Data records: 46032 Deleted blocks: 0 - check file-size - check key delete-chain - check index reference - check record links State update 8) Compress table $ aria_pack /var/lib/mysql/mygo/term Compressing /var/lib/mysql/mygo/term.MAD: (46032 records) - Calculating statistics - Compressing file Segmentation fault (core dumped) When I run steps 1, 5 and 8 I get the following error message: $ aria_pack /var/lib/mysql/mygo/term /var/lib/mysql/mygo/term gave error 132 on open Am I doing something wrong? Any pointers what I can check? Thanks Kenneth

1 0

[Maria-discuss] maria won't start after giving up on mysql 5.7
by Richard Whitney 24 Oct '17

24 Oct '17

Hello, I have been trying for a week to get mysql 5.7 setup on raspbian and have thrown in the towel. I have now installed (tried to install) mariadb 10.1 and it seems to hang on install and then won't start Let me try one more time ....... sudo apt autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: default-mysql-server 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 3 not fully installed or removed. After this operation, 9,216 B disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 126235 files and directories currently installed.) Removing default-mysql-server (1.0.2) ... Setting up mariadb-server-10.1 (10.1.23-9+deb9u1) ... Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details. invoke-rc.d: initscript mysql, action "start" failed. ● mariadb.service - MariaDB database server Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2017-10-24 13:25:21 MST; 60ms ago Process: 5576 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE) Process: 5487 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS) Process: 5482 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS) Process: 5479 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS) Main PID: 5576 (code=exited, status=1/FAILURE) Status: "MariaDB server is down" Oct 24 13:25:16 qa.com systemd[1]: Starting MariaDB database server... Oct 24 13:25:18 qa.com mysqld[5576]: 2017-10-24 13:25:18 1996230656 [Note] /usr/sbin/mysqld (mysqld 10.1.…576 ... Oct 24 13:25:21 qa.com systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE Oct 24 13:25:21 qa.com systemd[1]: Failed to start MariaDB database server. Oct 24 13:25:21 qa.com systemd[1]: mariadb.service: Unit entered failed state. Oct 24 13:25:21 qa.com systemd[1]: mariadb.service: Failed with result 'exit-code'. Hint: Some lines were ellipsized, use -l to show in full. dpkg: error processing package mariadb-server-10.1 (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of mariadb-server: mariadb-server depends on mariadb-server-10.1 (>= 10.1.23-9+deb9u1); however: Package mariadb-server-10.1 is not configured yet. dpkg: error processing package mariadb-server (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: mariadb-server-10.1 mariadb-server E: Sub-process /usr/bin/dpkg returned an error code (1) any ideas? Thank you! -- Richard Whitney phpMyDEV, LLC phpmydev.com 602-334-7771 May there always be tread and air in your tires and oatmeal and butter in your bowl - Author Unknown

1 0

[Maria-discuss] MaxScale behaviour differs for TLs and non-TLS clients
by Pak Chan 16 Oct '17

16 Oct '17

Hi, I'm (still) testing MaxScale, set up to connect only to the master node, on Ubuntu 16.04 fronting a Galera cluster. The cluster comprises of 2 MariaDB 10.1 instances on different servers, with a Galera Arbitrator instance running on the MaxScale server. I'm testing this using the MariaDB client (mysql) from a fourth machine. My test scenario is to see what the client experiences if I stop and restart a MariaDB node part-way through a transaction. I start with the "slave" node, to give me a baseline for comparison, before doing it with the master node. However, the baseline case gives me different results, depending on whether the MySQL client is connecting via TLS or not. If I connect to MaxScale via TLS, the connection disappears when the "slave" node comes back (but not when it goes down). Watching it via a network packet trace, I can see that, just after the slave comes back up, MaxScale sends the client an encrypted packet to the mysql client, then sends a MySQL Quit command to the master node before disconnecting. The syslog contains the line "[galeramon] There are no cluster members". If I connect to MaxScale without TLS, the connection remains stable regardless of the number of times the slave node goes down and up, and the "galeramon" line doesn't appear in the syslog. (I discovered this when I disabled the TLS in order to see what the encrypted packet being sent to the client was...I still don't know what it is!) Has anyone else come across this behaviour? MaxScale is configured as follows (the commented-out configuration is uncommented when connecting via TLS): [dbnode1] type=server address=172.16.1.22 port=3306 protocol=MySQLBackend priority=1 [dbnode2] type=server address=172.16.1.23 port=3306 protocol=MySQLBackend priority=2 [Galera Monitor] type=monitor module=galeramon servers=dbnode1,dbnode2 user=galeramon passwd=galeramon monitor_interval=1000 available_when_donor=true use_priority=true [Galera Service] type=service router=readrouteconn router_options=master servers=dbnode1,dbnode2 user=galeramon passwd=galeramon [MaxAdmin Service] type=service router=cli [Galera Listener] type=listener service=Galera Service protocol=MySQLClient port=3306 #ssl=required #ssl_version=TLSv12 #ssl_cert=/etc/mysql/ssl/server-cert.pem #ssl_key=/etc/mysql/ssl/server-key.pem #ssl_ca_cert=/etc/mysql/ssl/ca-cert.pem #ssl_cert_verify_depth=1 [MaxAdmin Listener] type=listener service=MaxAdmin Service protocol=maxscaled socket=default PC

2 3

[Maria-discuss] GitHub morgo/mysql-compatibility-config - add MariaDB
by Lukas Lehner 15 Oct '17

15 Oct '17

Hey I really like https://github.com/morgo/mysql-compatibility-config is there something similar for MariaDB? Since the repo is owned by some Oracle guy, I guess he won't add MariaDB. Lukas

1 0

[Maria-discuss] MaxScale (lack of) resilience to Galera cluster changes
by Pak Chan 06 Oct '17

06 Oct '17

Hi, Following on from my other thread, I'm testing MaxScale fronting a 2-node Galera cluster (with a Galera Arbitrator acting as the third node). My current test outline is as follows: 1. Identify the Write Master server in MaxScale 2. Connect two mysql clients to MaxScale, and put them both into "READ COMMITTED" isolation level ("set global transaction isolation level read committed") 3. Begin a transaction in each client session 4. Take down the non-Write master node in the Galera cluster ("systemctl stop mysql" on that server) 5. Commit the transaction in client 1 6. Confirm that the clients can see the committed change 7. Start up the stopped node in the Galera cluster ("systemctl start mysql" on that server) 8. Commit the transaction in client 2 9. Confirm that the clients can see the committed change 10. ... What happens is that everything appear to work up until step 8, when client 2 loses its connection to the database when trying to commit, reconnects and loses its uncommitted transaction as a result. At step 9, client 1 announces that it has lost the connection and reconnects. Is this meant to happen? If I run the same test, bypassing MaxScale and connecting both clients directly to the same Galera node, I don't get the connection loss. I understand that MaxScale will route writes to one node and reads to another, but surely the loss of connection to a read node should not result in the loss of connection to the write node? Am I doing something wrong? Yours very puzzled. PC

1 1