- discuss - lists.mariadb.org

[Maria-discuss] New Question: Does MariaDB Galera Cluster 10.0.21 version support gmcast.segment?
by AskMonty KB 17 Dec '15

17 Dec '15

Hello, A new question has been asked in "MariaDB Galera Cluster" by yu.d.sun_32615. Please answer it at http://mariadb.com/kb/en/does-mariadb-galera-cluster-10021-version-support-… as the person asking the question may not be subscribed to the mailing list. -------------------------------- Hi, Server version: 10.0.21-MariaDB-wsrep-log MariaDB Server, wsrep_25.10.r4144 ip-10-74-2-218$ root@localhost[(none)] MYSQL> set global wsrep_provider_options="gmcast.segment=1"; ERROR 1210 (HY000): Incorrect arguments to SET I also tried to put wsrep_provider_options="gmcast.segment=1" in the my.cnf but cannot start the instance: 151217 7:59:58 [ERROR] WSREP: Unrecognized parameter '"gmcast.segment' 151217 7:59:58 [ERROR] WSREP: wsrep::init() failed: 7, must shutdown 151217 7:59:58 [ERROR] Aborting Denis -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/does-mariadb-galera-cluster-10021-version-support-…

1 0

[Maria-discuss] max key length in import
by Warren H. Prince 17 Dec '15

17 Dec '15

I’m considering moving from MySql to MariaDB so I did a dump today and attempted an import. It failed with the “Specified key was too long; max key length is 767 bytes” error. I dealt with this in MySql and knew to change file format to Barracuda. I zapped the partial import, did a fresh mysql_install_db, restarted the service and tried again to no avail. To confirm my settings immediately after the failure: MariaDB [(none)]> SHOW VARIABLES LIKE 'innodb_file_%'; +--------------------------+-----------+ | Variable_name | Value | +--------------------------+-----------+ | innodb_file_format | Barracuda | | innodb_file_format_check | ON | | innodb_file_format_max | Barracuda | | innodb_file_per_table | ON | +--------------------------+—————+ Does anyone have any suggestions? The dump is 795M compressed so it’s difficult to find the exact place where the problem is (I used zcat for the import). My distribution is: 10.0.22-MariaDB running on Ubuntu 15.04 Thanks in advance.

2 2

[Maria-discuss] New Question: Galera Cluster expire_logs_days
by AskMonty KB 16 Dec '15

16 Dec '15

Hello, A new question has been asked in "MariaDB Galera Cluster" by diego.carrera. Please answer it at http://mariadb.com/kb/en/galera-cluster-expire_logs_days/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- Is it safe to modify the "expire_logs_days" variable while the cluster is running? show variables like 'expire_log_days' is 14, I've not defined this under my.cnf or wsrep.cnf. What would be the proper procedure to reduce or increase binlog expiry? -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/galera-cluster-expire_logs_days/

1 0

[Maria-discuss] Replication variables in my.cnf seem ignored if master connection does not exist
by Игорь Пашев 16 Dec '15

16 Dec '15

MariaDB 10.0.22 I saw weird things a couple of times: I start clean MariaDB with theses options in the configuration file: foo.replicate_wild_do_table = foo_live.% foo.replicate_ignore_table = foo_live.schema_updates Then I execute RESET SLAVE "foo" ALL just to be sure there is no such connection. Then I import the dump of master, and set master options like host, user, password, etc. Then I execute START SLAVE "foo" Then SHOW SLAVE "foo" reveals empty 'Replicate_Wild_Do_Table' and 'Replicate_Ignore_Table'. (And replication shortly breaks, because foo_live.schema_updates wasn't imported). I can fix this by restarting MariaDB. I'd expect the foo.replicate_* options are taking effect anytime. As a work-around I'd set those options dynamically after dump is imported. (I will fill MDEV in case it is confirmed as a bug)

1 1

[Maria-discuss] MariaDB Performance and Diagnostic Tools
by FERRETTI, ANDY 16 Dec '15

16 Dec '15

I'm looking for recommendations on MariaDB Performance Analysis tools. 1. I try MySQL workbench, but much of the capability is disabled. I get an error when I click on the Dashboard "This feature requires MySQL version 5.6.6 or newer". 2. I'm wondering if there are some good scripts to help identify key performance metrics from the performance_schema. I'd like to see a capability similar to an Oracle AWR report. I spent a fair amount of time doing google searches, and found some information on the performance_schema: https://php-built.com/enabling-performance-monitoring-for-mariadb-and-mysql/ , but I really think there should be something better. Thanks, Andy Ferretti Lead Principal-Technical Architect AT&T Technology Development - SD&E Cloud, Platform, Application and Data Layer Support (CPADS) Work: 205 989 0662 Cell: 205 478 9694 e-mail: andy.ferretti(a)att.com<mailto:andy.ferretti@att.com> This e-mail and any files transmitted with it are AT&T property, are confidential, and are intended solely for the use of the individual or entity to whom this emailis addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited.

5 4

[Maria-discuss] Galera Cluster: Cluster Blocked, when one node down?
by Benoit Panizzon 14 Dec '15

14 Dec '15

Hello We use MariaDB Galera Cluster for our email service platform. We decided to use Galera to create a high availability platform. After a year of operation, we start to relaize, that somehow Galera Failures seem to be the most common cause for outages we had in the past. So I wonder if others operating galera clusters also observe this situation: All our services using DB connections use a DNS round-robin name, to connect to one of our three galera instances. While testing this setup, we usualy killed one instance, or disconnected the node from the network to simulate an outage. In this situation, this works as expected. The client connect to the two remaining nodes, no service outage. When the node is re-started it is being re-synced quickly and service with three nodes is restored. Now we experienced a few galera cluster fails, which seem to happen this way: One of the nodes is getting a lot of load. DDOS Attacks, Memory Leaks or similar, which just renders the whole physical machine laggy for a short time. So the affected MariaDB node is being thrown out of the cluster by the two other nodes, probably for not syncing fast enough anymore. But as the node is not 'down' completely, it still accepts connections from the DB clients, but does not reply to them and seems to remain in a 'db locked' situation. Strangely this then also affects the two remaining nodes, who also go into 'locked' mode and do not reply to queries on the time expected by the application anymore. Of course this then causes more DB clients (IMAP, SMTP-Auth, etc) to spawn and to create DB connections worsening the whole situation. The situation seemingly can only be resolved by shuting down the MariaDB node that got thrown out of the cluster. Then the situations normalizes with the two remaining nodes and the third one can be restarted. Is this expected behaviour? Is there a way to tell a MariaDB node that got excluded from the cluster to shut himself down completely so it does NOT accept any more connections from clients, blocking the whole service? Regards -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

3 2

[Maria-discuss] New Question: I want to solve the error C1061 in visual studio.
by AskMonty KB 14 Dec '15

14 Dec '15

Hello, A new question has been asked in "MariaDB Documentation" by goodwill16. Please answer it at http://mariadb.com/kb/en/i-want-to-solve-the-error-c1061-in-visual-studio/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- Hello all, I got error as C1061: compiler limit : blocks nested too deeply i am using below code Try { AAAAAA....... } Catch(Exception^ ex) { if(AAA....); elseif(AAA....); elseif(AAA...); } The problem is catch block has limit to execute if-else statements of 128.but in my program I have 700 if-else statements . so please tell me how to extend the limit of catch block. thankyou, mallika.shaik -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/i-want-to-solve-the-error-c1061-in-visual-studio/

1 0

[Maria-discuss] out of memory linux kill and mysqld_multi
by Roberto Spadim 11 Dec '15

11 Dec '15

Hi guys, could we include a configuration at mysqld_mult and mysqld_safe? at linux killing the mysqld process is a big problem, i prefer leave it as the last process to kill check this post : http://www.oracle.com/technetwork/articles/servers-storage-dev/oom-killer-1… in this case oracle is the last tprocess to kill they use the /proc kernel interface to set the oom_adj i don't read the mysqld_safe and mysqld_multi, but could we include this at my.cnf? my last crash was a big trouble, if kernel killed the others process before mysql maybe the mysqld couldn't be killed thanks guys i will create a MDEV about it -- Roberto Spadim

2 2

[Maria-discuss] Queries Not Completing After Backup
by Brad Jorgensen 11 Dec '15

11 Dec '15

We have a three node (db1, db2, db3) galera cluster with MariaDB 10.0.22 on CentOS 6.7. A couple days ago I upgraded to 10.1.9. Xtrabackup (2.3.2) is run every night on each node at 1am, 2am, and 3am respectively. Before the backup starts, the node is desynced. The first night after upgrading to 10.1.9, the problem began. All connections were going to db1 until the backup started when db1 was removed from the routing pool and new connections began going to db2. At that time there was little traffic aside from the backup; much of it is probably monitoring queries. Our monitoring shows that running threads went from about 2 just before the backup finished around 1:32am to about 150 just after. At the same time, the running threads on db2 went from 1 to 10. After the backup completed, all new connections were going to db1 again. The running threads on db1 continued to slowly grow until the queries that are stuck took up all of the server processes on our application servers and we were alerted around 3:50am. I checked the process list and almost all of the queries were in the "query end" state and I think they were all write queries. I tried to kill most of them but they just stayed in the same state. I restarted db2 to try to kick the cluster without losing data. I had to force the shutdown since three threads never ended after about 10 minutes of waiting. The running threads on db1 returned to normal. db2 had do do a full SST which took until 6:05 to complete. At that time, the running processes on db1 began to increase again. When db2 was back up I downgraded to 10.1.22 and rejoined it to the cluster. I tried to restart db1, but it needed a full SST so I left it down. A bit later I took down db3 to downgrade it, too at that went fine. The cluster was fine through the day during normal business operation. The next night only db2 and db3 were up and were running 10.0.22. What appears to be the same problem started at 3:31am, when xtrabackup paused galera ("Provider paused at 8c53b634-9514-11e4-b8bd-dab05673fb36:875650526") on db3 for the backup. At that time the running threads on db2 shot up and slowly increased until I shut it down at 6:28. I had to kill it again due to three threads on ending. db3 showed nothing unusual in the logs. I got the innodb engine status from db2 three times a few minutes apart before I restarted; they are attached. Additionally, I attached an excerpt from the logs on db2 and db3 during the second incident and the my.cnf from one of the servers, it's basically the same for the others. I'm working on getting a clean set of logs from the first incident, but from what I initially saw, they are basically the same as the second set of logs. I'm ready if the problem arises again and I'll try to get more information including SHOW GLOBAL STATUS. Our environment hasn't changed for at least a month and the issue first appeared after upgrading to 10.1.9, but since it didn't go away after downgrading, I'm not sure where the issue is. I found a few mentions of what might be the same problem: http://marialog.archivist.info/2015-04-03.txt https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1149755

2 1

[Maria-discuss] INNODB not loading
by Roberto Spadim 11 Dec '15

11 Dec '15

hi guys, i was using my database and it crashed, after restart innodb (Xtradb) don't start the log shows this: 151210 21:44:38 [Note] InnoDB: Using mutexes to ref count buffer pool pages 151210 21:44:38 [Note] InnoDB: The InnoDB memory heap is disabled 151210 21:44:38 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 151210 21:44:38 [Note] InnoDB: Memory barrier is not used 151210 21:44:38 [Note] InnoDB: Compressed tables use zlib 1.2.3 151210 21:44:38 [Note] InnoDB: Using CPU crc32 instructions 151210 21:44:38 [Note] InnoDB: Initializing buffer pool, size = 32.0G 151210 21:44:48 [Note] InnoDB: Completed initialization of buffer pool 151210 21:44:54 [Note] InnoDB: Highest supported file format is Barracuda. 151210 21:44:54 [Note] InnoDB: The log sequence numbers 8739254920 and 8739254920 in ibdata files do not match the log sequence number 98318151020 in the ib_logfiles! 151210 21:44:54 [Note] InnoDB: Database was not shutdown normally! 151210 21:44:54 [Note] InnoDB: Starting crash recovery. 151210 21:44:54 [Note] InnoDB: Reading tablespace information from the .ibd files... 151210 21:44:54 [Note] InnoDB: Restoring possible half-written data pages 151210 21:44:54 [Note] InnoDB: from the doublewrite buffer... 151210 21:44:57 [Note] InnoDB: 128 rollback segment(s) are active. 151210 21:44:57 [Note] InnoDB: Waiting for purge to start 151210 21:44:57 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.25-73.1 started; log sequence number 98318151020 151210 21:44:57 [Note] Plugin 'FEEDBACK' is disabled. 151210 21:44:57 [Note] Server socket created on IP: '::'. 151210 21:44:57 [Note] Event Scheduler: Loaded 0 events 2015-12-10 21:44:57 7fbfd435a700 InnoDB: Error: Table "mysql"."innodb_table_stats" not found. 151210 21:44:57 [Note] /opt/mariadb/bin//mysqld: ready for connections. Version: '10.0.21-MariaDB-log' socket: '/tmp/mysql.BH.sock' port: 3307 MariaDB Server any idea what could be done to start recovery from innodb? -- Roberto Spadim

3 4