- discuss - lists.mariadb.org

[Maria-discuss] start mariadb randomly fails or answers with wrong response to systemd
by Reindl Harald 20 Jan '14

20 Jan '14

i have for at least 5 years a backup server with two mysql-instances * one replication instance listening on port 3307 * one "live" service * a script once a hour stop both instances and rsync replication->live * after that start both intances again * looking at the mysqld logs i am pretty sure there is nothing wrong and only the non.zero response causes systemd to restart the daemon one time well, with MariaDB on Fedora 19 systemd cries about failing service at the same time there is nothing in the mysql-errorlog (both instances using the same) the systemd-units are configured to restart the daemon again if it fails what replaces the mysqld_safe scripts and is done this way unchanged since summer 2011 with MySQL 5.5.x has anybody an idea what causes the "mysqld.service" instance to respond with status 1 instead 0 causing systemd to consider the service as failed while there is nothing uncommon in the mysqld-logs? the "Error reading relay log event: slave SQL thread was killed" as well as "Error reading packet from server" are not relevant in that context because they are from the not failing "replication.service" and normal due shutdown the slave (well, i dislike "error" in that context, but that's OT) interesting is that i have 3 machine-pairs with the 100% identical logic two of them are failing this way nearly every hour (backup schedule 60 minutes) while the one with 5000 tables is running perfect all the time any information i could provide additional to the logs and configs below? ___________________________________________________________________________ Jan 7 20:21:04 localhost backups: stop replication service Jan 7 20:21:04 localhost systemd[1]: Stopping MySQL Replication... Jan 7 20:21:04 localhost systemd[1]: Stopped MySQL Replication. Jan 7 20:21:04 localhost backups: stop live database Jan 7 20:21:04 localhost systemd[1]: Stopping MariaDB Database... Jan 7 20:21:04 localhost systemd[1]: Stopped MariaDB Database. Jan 7 20:21:04 localhost backups: backup replication data to '/data/mysql_data/' Jan 7 20:21:04 localhost backups: backup replication data finished Jan 7 20:21:04 localhost backups: start MySQL-Replication-Service Jan 7 20:21:04 localhost systemd[1]: Starting MySQL Replication... Jan 7 20:21:04 localhost systemd[1]: Started MySQL Replication. Jan 7 20:21:04 localhost backups: start MySQL-Live-Service Jan 7 20:21:04 localhost systemd[1]: Starting MariaDB Database... Jan 7 20:21:04 localhost systemd[1]: mysqld.service: control process exited, code=exited status=1 Jan 7 20:21:04 localhost systemd[1]: Failed to start MariaDB Database. Jan 7 20:21:04 localhost systemd[1]: Unit mysqld.service entered failed state. Jan 7 20:21:04 localhost backups: database backup finished Jan 7 20:21:05 localhost systemd[1]: mysqld.service holdoff time over, scheduling restart. Jan 7 20:21:05 localhost systemd[1]: Stopping MariaDB Database... Jan 7 20:21:05 localhost systemd[1]: Starting MariaDB Database... Jan 7 20:21:06 localhost systemd[1]: Started MariaDB Database. ___________________________________________________________________________ 140107 20:21:04 [Note] /usr/libexec/mysqld: Normal shutdown 140107 20:21:04 [Note] Event Scheduler: Purging the queue. 0 events 140107 20:21:04 [Note] Error reading relay log event: slave SQL thread was killed 140107 20:21:04 [ERROR] Error reading packet from server: Lost connection to MySQL server during query ( server_errno=2013) 140107 20:21:04 [Note] Slave I/O thread killed while reading event 140107 20:21:04 [Note] Slave I/O thread exiting, read up to log 'bin.000002', position 245 140107 20:21:04 [Note] /usr/libexec/mysqld: Shutdown complete 140107 20:21:04 [Note] /usr/libexec/mysqld: Normal shutdown 140107 20:21:04 [Note] Event Scheduler: Purging the queue. 0 events 140107 20:21:04 [Note] /usr/libexec/mysqld: Shutdown complete 140107 20:21:04 [Note] Plugin 'InnoDB' is disabled. 140107 20:21:04 [Note] Plugin 'FEDERATED' is disabled. 140107 20:21:04 [Note] Plugin 'FEEDBACK' is disabled. 140107 20:21:04 [Note] Plugin 'InnoDB' is disabled. 140107 20:21:04 [Note] Plugin 'FEDERATED' is disabled. 140107 20:21:04 [Note] Plugin 'FEEDBACK' is disabled. 140107 20:21:04 [Note] Event Scheduler: Loaded 0 events 140107 20:21:04 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.5.34-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 0 thelounge 140107 20:21:04 [Note] Event Scheduler: Loaded 0 events 140107 20:21:04 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.5.34-MariaDB' socket: '/var/lib/mysql/mysql_replication.sock' port: 0 thelounge 140107 20:21:04 [Note] Slave SQL thread initialized, starting replication in log 'bin.000002' at position 245, relay log './mysql-relay-bin.000016' position: 523 140107 20:21:04 [Note] /usr/libexec/mysqld: Normal shutdown 140107 20:21:04 [Note] Event Scheduler: Purging the queue. 0 events 140107 20:21:04 [Note] /usr/libexec/mysqld: Shutdown complete 140107 20:21:04 [Note] Slave I/O thread: connected to master 'replication@masterserver:3306',replication started in log 'bin.000002' at position 245 140107 20:21:05 [Note] Plugin 'InnoDB' is disabled. 140107 20:21:05 [Note] Plugin 'FEDERATED' is disabled. 140107 20:21:05 [Note] Plugin 'FEEDBACK' is disabled. 140107 20:21:05 [Note] Event Scheduler: Loaded 0 events 140107 20:21:05 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.5.34-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 0 thelounge ___________________________________________________________________________ /usr/lib/systemd/system/mysqld.service [Unit] Description=MariaDB Database Before=postfix.service dovecot.service dbmail-imapd.service dbmail-lmtpd.service dbmail-pop3d.service dbmail-postfix-policyd.service [Service] Type=simple PIDFile=/var/run/mysqld/mysqld.pid ExecStart=/usr/libexec/mysqld --defaults-file=/etc/my.cnf --pid-file=/var/run/mysqld/mysqld.pid --socket=/var/lib/mysql/mysql.sock --open-files-limit=750000 --basedir=/usr --user=mysql ExecStartPost=/usr/libexec/mysqld-wait-ready $MAINPID Restart=always RestartSec=1 TimeoutSec=300 LimitNOFILE=infinity LimitMEMLOCK=infinity OOMScoreAdjust=-1000 SysVStartPriority=64 PrivateTmp=true CapabilityBoundingSet=~CAP_SYS_PTRACE ReadOnlyDirectories=/etc ReadOnlyDirectories=/usr InaccessibleDirectories=/boot InaccessibleDirectories=/home InaccessibleDirectories=/root Restart=always InaccessibleDirectories=/usr/local/scripts InaccessibleDirectories=/var/lib/rpm InaccessibleDirectories=/var/lib/yum InaccessibleDirectories=/var/spool [Install] WantedBy=multi-user.target ___________________________________________________________________________ /usr/lib/systemd/system/replication.service [Unit] Description=MySQL Replication [Service] Type=simple PIDFile=/var/run/mysqld/mysqld_replication.pid ExecStart=/usr/libexec/mysqld --defaults-file=/etc/my-replication.cnf --pid-file=/var/run/mysqld/mysqld_replication.pid --socket=/var/lib/mysql/mysql_replication.sock --open-files-limit=30000 --basedir=/usr --user=mysql Restart=always RestartSec=1 TimeoutSec=300 LimitNOFILE=infinity LimitMEMLOCK=infinity OOMScoreAdjust=-1000 SysVStartPriority=64 PrivateTmp=true CapabilityBoundingSet=~CAP_SYS_PTRACE ReadOnlyDirectories=/etc ReadOnlyDirectories=/usr InaccessibleDirectories=/boot InaccessibleDirectories=/home InaccessibleDirectories=/root InaccessibleDirectories=/usr/local/scripts InaccessibleDirectories=/var/lib/rpm InaccessibleDirectories=/var/lib/yum InaccessibleDirectories=/var/spool [Install] WantedBy=multi-user.target

2 5

[Maria-discuss] Top voted features for MariaDB 10.1
by Rasmus Johansson 19 Jan '14

19 Jan '14

Hi, Yesterday Daniel Bartholomew published a blog post about voting for features in MariaDB 10.1, https://blog.mariadb.org/what-do-you-want-to-see-in-mariadb-10-1/ . To make it easier to follow which the most wanted (most votes) features are I pulled together a list in JIRA for anyone interested. It can be found here https://mariadb.atlassian.net/secure/Dashboard.jspa?selectPageId=11500 . The page doesn't require login, but if you want to vote you need to log in. BR, Rasmus -- Rasmus Johansson, VP Engineering MariaDB | t: +358 50 499 9589 | Skype: ratzpo

2 1

[Maria-discuss] mydumper halting replication by creating innodb table in mysql db
by Daniel Black 18 Jan '14

18 Jan '14

1 1

[Maria-discuss] Galera on Fedora
by David Timothy Strauss 15 Jan '14

15 Jan '14

The documentation currently warns against using Galera with Fedora [1]. Is that advice still true with Fedora 19+, which defaults to MariaDB? I can see some activity in the bug tracker [2], but nothing the last few months. In a related topic, when are RPMs for Fedora 20 [3] planned? Is there any way I can sponsor work to improve the situation? [1] https://mariadb.com/kb/en/installing-mariadb-with-yum/#installing-mariadb-g… [2] https://mariadb.atlassian.net/browse/MDEV-4141 [3] http://yum.mariadb.org/5.5-galera/

2 1

[Maria-discuss] trademarks
by Federico Razzoli 08 Jan '14

08 Jan '14

I found contradictory information about whom the MariaDB trademark belongs to: "The MariaDB Foundation also holds the trademark of the MariaDB server and owns mariadb.org. This ensures that the official MariaDB development tree will always be open for the MariaDB developer community." https://mariadb.com/kb/en/mariadb-foundation/ "SkySQL and MariaDB are trademarks or registered trademarks of SkySQL Corporation Ab in the European Union and United States of America and/or other countries." http://www.skysql.com/about/legal/trademarks If the last statement is true, I have several questions about the other statement I quoted and some other statements in the Foundation's site. If the last statement is false, I suggest it is fixed, because it is confusing. Regards, Federico

3 2

[Maria-discuss] MariaDB Developer meetings still public?
by Jeremy Cole 07 Jan '14

07 Jan '14

In the past, MariaDB Developer meetings have been open invitation and pre-announced, e.g.: - https://mariadb.org/en/developer-meetings/ - http://planet.mysql.com/entry/?id=30418 - http://monty-says.blogspot.com/2011/02/come-to-lisbon-and-meet-mariadb.html - http://monty-says.blogspot.com/2011/11/mariadb-developer-meeting-in-athens.… And this was even included in Monty's presentation as recently as a couple weeks ago: http://www.slideshare.net/skysql/mariadb-100-skysql-paris-meetup-171220113 >From Slide 47: "Open source development: Anyone can be part of the development at all stages. Developer meetings are public!" Yet, I've heard from a casual mention on IRC that there is such a meeting next week in Barcelona, and I haven't seen any mention of it on this list or elsewhere: <montywi> prohaska7: we will have a mariadb developers meeting in Barcelona next week Are the meetings still public/open? If so, what happened here? Is this a policy change? (I've also seen no private invitation, in case that were in question.) Regards, Jeremy

2 1

[Maria-discuss] failing test: rpl.rpl_stm_sql_mode
by Reindl Harald 07 Jan '14

07 Jan '14

i see the error below over many months, AFAIK also with mySQL "This operation cannot be performed with a running slave; run STOP SLAVE first" is nice but out of scope due running the auto-tests /usr/bin/su -c 'cd /usr/share/mysql-test; ./mysql-test-run.pl --default-myisam --parallel=1 --max-test-fail=0 --mysqld=--binlog-format=mixed --skip-ndb --force' mysql __________________________________________________ rpl.rpl_stm_sql_mode 'stmt' [ fail ] Test ended at 2014-01-07 20:27:05 CURRENT_TEST: rpl.rpl_stm_sql_mode mysqltest: In included file "./include/rpl_init.inc": included from ./include/master-slave.inc at line 38: included from /usr/share/mysql-test/suite/rpl/t/rpl_stm_sql_mode.test at line 2: At line 179: query 'RESET SLAVE' failed: 1198: This operation cannot be performed with a running slave; run STOP SLAVE first The result from queries just before the failure was: include/master-slave.inc - saving '/usr/share/mysql-test/var/log/rpl.rpl_stm_sql_mode-stmt/' to '/usr/share/mysql-test/var/log/rpl.rpl_stm_sql_mode-stmt/' rpl.rpl_stm_user_variables 'stmt' [ skipped ] Not STATEMENT format

1 0

[Maria-discuss] New Question: MariaDB Galera Cluster Questions
by AskMonty KB 04 Jan '14

04 Jan '14

Hello, A new question has been asked in "MariaDB FAQ" by pranava: -------------------------------- I have some questions on Maria DB Galera Cluster. Q1) If I partition a table in a schema which is part of MariaDB Galera Cluster, can i configure partitions in such a way that a one partition resides in one Node, another partition resides in second Node and so on? I'm trying to shard the data and use Galera cluster nodes to accommodate parts of that shard. Q2) Scenario - During replication of MariaDB Galera Cluster, the Master node gets a request, it processes it and then sends to other nodes for approval, followed by a commit at every node. What if commit happens on majority of nodes except one or two? What happens to that transaction and how about Data consistency among all nodes? Q3) Which protocol is used for communicating between nodes during data replication in MariaDB Galera Cluster? Is it TCP or a Broadcast to all other nodes or Some customized protocol between nodes that enables replication in the cluster. Thanks a lot in advance. Thanks Pranav. -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/mariadb-galera-cluster-questions/

3 2

[Maria-discuss] question about mariadb threadpools and file descriptors
by Rohan M C 31 Dec '13

31 Dec '13

Hi All, We're considering a switch to mariadb (5.5.33a) from mysql (5.5.31) for our production servers. First, some background info about our system 1) ~2000 tables. 3/4th of them are innodb, the rest are myisam 2) All tables are partitioned with ~100 partitions each 3) our largest tables are partitioned (~200 partitions each) and they're all myisam due to space constraints (and other reasons) 4) all our instances are on amazon ec2 on ephemeral store Some of our config parameters open-files-limit 131072 innodb-open-files 16384 table-open-cache 4096 innodb-buffer-pool-size 256M One of the problems we're facing with mysql, and we're hoping to solve with mariadb, is the blowup of the number of open file descriptors when some of our long-running/heavier scripts run. So far we've been able to keep it in control by having our scripts flush at intervals, as well as making individual threads hit different read slaves so as to not open up mulitple copies of myisam fds on a single machine. I do know that the above parameters could be tweaked to set a cap on the number of file descriptors (innodb seems to be a hard limit, so thats under control), but we've set table-open-cache at a high number for performance reasons. Our ideal solution would be to keep the above parameters and not run into a situation where the number of file descriptors grow uncontrollably beyond 70k-80k. It would be preferable to have mariadb close file descriptors once queries are done. We were interested in the mariadb threadpool option as it launches threads dynamically when needed and closes them once it's done. I'm currently testing on a mariadb instance with the default parameters. One of my assumptions with threadpools was that when additional threads were closed, the file descriptors opened for them would also be closed, but upon testing I've seen that this is not the case, and that mariadb behavior as far as threadpools are concerned is exactly the same as mysql. For example, with thread_pool_size=1 and max_threads at 500, if I run 10 identical concurrent queries from different connections on mariadb on a myisam table, it opens up 10 sets of 200 file descriptors. Threadpool_threads spikes up to 10 and drops back down after some time, but all the file descriptors initially opened are still in the open state (2200 fds ). Is this intended behavior for threadpools? I would also be grateful for any tips, reading material or knowledge regarding how mariadb handles file descriptors and if there are any additional parameters that can be tuned to keep the number of file descriptors under control, while not impacting performance too much Thanks in advance. Rohan

1 0

[Maria-discuss] MariaDB 10.0.7 Now Available
by Daniel Bartholomew 27 Dec '13

27 Dec '13

The MariaDB project is pleased to announce the immediate availability of MariaDB 10.0.7. This is a Beta release. See the Release Notes and Changelog for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB 10.0.7 - Release Notes: https://mariadb.com/kb/en/mariadb-1007-release-notes - Changelog: https://mariadb.com/kb/en/mariadb-1007-changelog - Downloads: https://downloads.mariadb.org/mariadb/10.0.7 About MariaDB 10.0: - https://mariadb.com/kb/en/what-is-mariadb-100/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ - - MariaDB Webinars - - - - - - - - - - - - - - - - - - - - - - - - - SkySQL has had several MariaDB focused Webinars recently which are available on an on-demand basis at: - http://www.skysql.com/why-skysql/webinars/ They are also planning several more MariaDB-focused webinars that will be held over the comming months. Details available at the above link. - - New MariaDB Book - - - - - - - - - - - - - - - - - - - - - - - - - A new MariaDB book has been released! Getting Started with MariaDB is a how-to guide for beginners to help them get up to speed quickly with MariaDB, no previous MariaDB or MySQL experience required. It's available from several booksellers in both paperback and DRM-free epub, mobi and pdf formats. See the PacktPub website for details: - http://www.packtpub.com/getting-started-with-mariadb/book - - User Feedback plugin - - - - - - - - - - - - - - - - - - - - - - - MariaDB includes a User Feedback plugin. This plugin is disabled by default. If enabled, it submits basic, completely anonymous MariaDB usage information. This information is used by the developers to track trends in MariaDB usage to better guide development efforts. If you would like to help make MariaDB better, please add "feedback=ON" to your my.cnf or my.ini file! See http://mariadb.com/kb/en/user-feedback-plugin for more information. - - Quality - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The project always strives for quality, but in reality, nothing is perfect. Please take time to report any issues you encounter at: - http://mariadb.org/jira - - Support MariaDB - - - - - - - - - - - - - - - - - - - - - - - - - - If you would like to contribute to the MariaDB Foundation, please see the "contributing" and "donations" pages. We also have merchandise available in a cafepress store. All proceeds go to support the MariaDB Foundation. - https://mariadb.com/kb/en/contributing - https://mariadb.org/en/donate/ - http://www.cafepress.com/mariadb We hope you enjoy MariaDB! -- MariaDB: An Enhanced Drop-in Replacement for MySQL Website - http://mariadb.org Twitter - http://twitter.com/mariadb Google+ - http://google.com/+mariadb Facebook - http://fb.com/MariaDB.dbms Knowledge Base - http://mariadb.com/kb

1 0