- discuss - lists.mariadb.org

Re: [Maria-discuss] MySQL Workbench Fork?
by Federico Razzoli 27 Apr '17

27 Apr '17

I've just seen this Quora answer, which lists some good reasons to avoid GUIs. There are others. Again: my point is not "GUI's shouldn't exist", it's just "please don't call them an enterprise software, because they are not". https://www.quora.com/Do-database-administrators-actually-think-that-GUIs-a… Cheers, Federico

2 1

[Maria-discuss] userstats Denied_connections
by Rhys.Campbell＠swisscom.com 27 Apr '17

27 Apr '17

Hello All, I've been using the userstats plugin do debug an application issue and I think there's a bug in the collection of statistics, or at least a case of bad wording... https://mariadb.com/kb/en/mariadb/user-statistics/ DENIED_CONNECTIONS - The number of connections denied to this user. ACCESS_DENIED - The number of times this user's connections issued commands that were denied. A application user was displaying very high "DENIED_CONNECTION" values. This sent us in the direction a bad password was being supplied. Long story short it actually turns out that a series of ALTER TABLE statements were failing, because the application does not have permission to do so. During one our tests DENIED_CONNECTION was 5397 and ACCESS_DENIED was 0. We can see the ALTER TABLE statement failing and DENIED_CONNECTION being incremented quickly. According to the documentation shouldn't this ACCESS_DENIED (which I think might be better named COMMAND_DENIED?). Cheers, Rhys

2 1

[Maria-discuss] Inconsistent Query Results from Dependent Subquery
by Sam Vaughan 27 Apr '17

27 Apr '17

I'm seeing some odd behaviour on MariaDB 10.1.22 that's got me scratching my head. My production servers (a master and two slaves) are returning incorrect query results, but when I run the same query on the same data elsewhere I always get the correct results, even on a VM with matching OS, H/W arch and MariaDB version. The problem is triggered by using "ORDER BY x DESC LIMIT 1" in a dependent subquery on a single table. The query is being run on a small InnoDB table that very rarely changes. Each row contains a date, an integer identifier, a sequence number and a handful of applicable settings that are all integers. Unfortunately I can't create a simplified reproducible test case, but the following example shows the sort of query I'm working with. Imagine a table that looks like this: CREATE TABLE `settings` ( `date` date NOT NULL, `id` int(11) NOT NULL, `seq` int(11) NOT NULL, `value` int(11) NOT NULL, UNIQUE KEY `date_id_seq` (`date`,`id`,`seq`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1; The table is designed to store a sequence of values belonging to something identified by the ID. Each sequence of values has a date stamp, and can be replaced at a later date by a new sequence of values: +------------+----+-----+-------+ | date | id | seq | value | +------------+----+-----+-------+ | 2011-11-01 | 1 | 0 | 6 | | 2011-11-01 | 1 | 1 | 3 | | 2011-11-01 | 1 | 2 | 9 | | 2011-11-01 | 2 | 0 | 6 | | 2011-11-01 | 2 | 1 | 1 | | 2011-11-01 | 3 | 0 | 6 | | 2011-11-01 | 3 | 1 | 8 | | 2012-04-01 | 1 | 0 | 4 | | 2012-04-01 | 1 | 1 | 3 | | 2013-06-01 | 3 | 0 | 5 | +------------+----+-----+-------+ The query is asking for all the IDs that had a particular first value set as of a particular date, in this case a first value of 6 as of '2012-07-01': SELECT s1.id FROM settings s1 WHERE s1.seq = 0 and s1.value = 6 and s1.date = ( SELECT s2.date FROM settings s2 WHERE s2.id = s1.id and s2.date <= '2012-07-01' ORDER BY s2.date DESC LIMIT 1 ); This query correctly returns IDs 2 and 3, and not ID 1 since the data for '2012-04-01' overrides the data for '2011-11-01'. In my equivalent situation, my production servers are returning 1, 2 and 3. Everywhere else I try to run it I get just 2 and 3 as expected. The table in question changes rarely, so it's trivial to show that the test system I've set up is working on the same data as the production systems. I've selected the entire table to out-files and diffed them, I've restored the test system from a mysqldump backup of production, and I've even run XtraBackup and prepared it with --export, then followed the instructions to import the table files into my test system just in case there's something weird in the production table's .ibd file. No matter what I do, I can't reproduce the problem anywhere but on my production systems. Testing has shown that minor changes to the query will fix the result set. Changing it to use "max()" instead of "order/limit" fixes it. Removing the date test from the where clause also fixes it. I don't want to just change all my queries like this to use MAX() and be done with it, because this weirdness will always be in the back of my mind. Is my query insufficiently specific? Have my queries of this type only ever returned the right results by accident until I moved to MariaDB recently? I haven't tried adding an index to the date column yet, because it too might make the problem vanish and I'll be none the wiser. I'd rather work out how to make the problem reproducible then dig in further to expose the cause. I thought that my InnoDB file could have been corrupt, but preparing the XtraBackup didn't detect it. Perhaps I've triggered a bug in MariaDB that needs very special conditions to appear? That seems unlikely but I'm at a bit of a loss now. Any suggestions anyone might have would be very gratefully received! Kind regards, Sam

1 0

[Maria-discuss] MariaDB Server maintenance policy for 10.0
by Colin Charles 26 Apr '17

26 Apr '17

Hi! I just read: https://mariadb.org/about/maintenance-policy/ It says the 5 year boundary date for support ending for 10.0 is 31 Mar 2019, and later goes on to specify why 5.5 has a later EOL, "The MariaDB Foundation may decide to maintain selected releases beyond the normal 5 years if they are in exceptionally widespread use. As MariaDB 5.5 is included in multiple prominent Linux distributions with a lifespan beyond 2017, the Foundation is committed in maintaining it until 2020." Is SUSE Enterprise Linux Server 12, with MariaDB Server 10.0, not considered a “prominent Linux distribution”? SLES12 released in 2014, comes with MariaDB Server 10.0, and requires at least 10 years of support (https://www.suse.com/releasenotes/x86_64/SUSE-SLES/12/) Just checking to see if the maintenance policy above is in error Thanks -- Colin Charles, http://bytebot.net/blog/ twitter: @bytebot | skype: colincharles "First they ignore you, then they laugh at you, then they fight you, then you win." -- Mohandas Gandhi

3 4

Re: [Maria-discuss] Are some MyISAM settings used for Aria
by Federico Razzoli 24 Apr '17

24 Apr '17

Hi Jocelyn, The article you linked is quite old, so I wanted to check the source code to find if something changed. I didn't investigate much but I searched in MariaDB's master branch via GitHub. The search strings were 'read_rnd_buffer_size' and 'read-rnd-buffer-size'. I found nothing except for some test files and the variable initialization at server startup. I repeated the same searches in MySQL master branch, and again, I found only tests and initialization. Can you explain this? The variable is unused now? Federico -------------------------------------------- Lun 24/4/17, jocelyn fournier <jocelyn.fournier(a)gmail.com> ha scritto: Oggetto: Re: [Maria-discuss] Are some MyISAM settings used for Aria A: "Sales" <info(a)smallbusinessconsultingexperts.com> Cc: "Maria Discuss" <maria-discuss(a)lists.launchpad.net> Data: Lunedì 24 Aprile 2017, 09:16 Hi Steve, Le 24 avr. 2017 3:28 AM, "Sales" <info(a)smallbusinessconsultingexperts.com> a écrit : On Apr 23, 2017, at 4:12 PM, jocelyn fournier <jocelyn.fournier(a)gmail.com> wrote: Hi Steve, Le 23/04/2017 à 19:32, Sales a écrit : On our system, Mariadb 10.1.22, with aria_used_for_temp_tables = ON, we have a set of MyISAM settings carried over from an earlier setup. Those settings are: key_buffer_size=256M myisam_sort_buffer_size = 64M join_buffer_size=512K bulk_insert_buffer_size=512M read_rnd_buffer_size = 1M read_rnd_buffer_size and join_buffer_size are not MyISAM specific settings, did you try to modify/not modify only those ones ? HTH, Jocelyn Really? So, the doc is wrong? https://mariadb.com/kb/en/ mariadb/server-system- variables/#read_rnd_buffer_ size Says, MyISAM. So, are you saying that is mistaken? If so, that would make sense At least according to https://www.percona.com/blog/2007/07/24/what-exactly-is-read_rnd_buffer_siz… it's not. BTW it has been updated in the mysql manual to mention it optimizes mrr for any engine :https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_read_rnd_buffer_size MariaDB KB would need an update as well. Jocelyn _______________________________________________ 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

3 4

[Maria-discuss] Are some MyISAM settings used for Aria
by Sales 24 Apr '17

24 Apr '17

On our system, Mariadb 10.1.22, with aria_used_for_temp_tables = ON, we have a set of MyISAM settings carried over from an earlier setup. Those settings are: key_buffer_size=256M myisam_sort_buffer_size = 64M join_buffer_size=512K bulk_insert_buffer_size=512M read_rnd_buffer_size = 1M Looking in the information_schema, we have one entire schema of tables still using MyISAM (third party system), and, this schema is not used in any daily processing. The only other MyISAM tables are in the mysql schema. So, nothing else, not one table. The way I understand aria, it should be used instead of MyISAM even for tmp tables given our settings. We have a long running set of programs that do things over night to manage products, many millions of them, ends up processing at least 50 million rows of various tables, thousands of mysql statements. This process has no MyISAM as noted. When I disable the settings above for MyISAM, a significant runtime increase is noted, I’ve repeated this 5 times now over a few week period. The increase is 20%, pretty significant, and that 20% never occurs when not changing settings. So, it would seem unlikely that I am just that unlucky. I am curious as to why those settings for MyISAM would have an impact? There are certainly tmp tables in the process (or internally created tmp tables) and the rest is innodb. Any good potential reason I am missing? I have not really looked into aria much before, read most of the mariadb doc. Maybe I missed something key, it appears likely I did! We have the following somewhat corresponding aria settings: aria_pagecache_buffer_size = 256M aria_sort_buffer_size = 256M Steve

2 3

[Maria-discuss] R: Are some MyISAM settings used for Aria
by Federico Razzoli 24 Apr '17

24 Apr '17

Steve, aria_used_for_temp_tables only affects internally created temporary tables, not the temp tables created explicitly by applications. So I suggest: * check if your applications create MyISAM (temporary) tables * use the slow log (long_query_time=0, min_examine_rows=0) and pt-query-digest to check which queries are slower when you comment those settings Federico -------------------------------------------- Dom 23/4/17, Sales <info(a)smallbusinessconsultingexperts.com> ha scritto: Oggetto: [Maria-discuss] Are some MyISAM settings used for Aria A: maria-discuss(a)lists.launchpad.net Data: Domenica 23 Aprile 2017, 19:32 On our system, Mariadb 10.1.22, with aria_used_for_temp_tables = ON, we have a set of MyISAM settings carried over from an earlier setup. Those settings are: key_buffer_size=256M myisam_sort_buffer_size = 64M join_buffer_size=512K bulk_insert_buffer_size=512M read_rnd_buffer_size = 1M Looking in the information_schema, we have one entire schema of tables still using MyISAM (third party system), and, this schema is not used in any daily processing. The only other MyISAM tables are in the mysql schema. So, nothing else, not one table. The way I understand aria, it should be used instead of MyISAM even for tmp tables given our settings. We have a long running set of programs that do things over night to manage products, many millions of them, ends up processing at least 50 million rows of various tables, thousands of mysql statements. This process has no MyISAM as noted. When I disable the settings above for MyISAM, a significant runtime increase is noted, I’ve repeated this 5 times now over a few week period. The increase is 20%, pretty significant, and that 20% never occurs when not changing settings. So, it would seem unlikely that I am just that unlucky. I am curious as to why those settings for MyISAM would have an impact? There are certainly tmp tables in the process (or internally created tmp tables) and the rest is innodb. Any good potential reason I am missing? I have not really looked into aria much before, read most of the mariadb doc. Maybe I missed something key, it appears likely I did! We have the following somewhat corresponding aria settings: aria_pagecache_buffer_size = 256M aria_sort_buffer_size = 256M Steve _______________________________________________ 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

3 3

Re: [Maria-discuss] Are some MyISAM settings used for Aria
by Federico Razzoli 23 Apr '17

23 Apr '17

Once you see which queries are slower, you can find which changes affected the query. Execution plans are not expected to change when you resize a buffer, but you can measure the effect of resizing the buffers. SHOW GLOBAL STATUS LIKE 'Handler%' can also help you to measure WHICH PART of a query becomes slower/fast after changing a variable. Usually those buffers should be left on their default values. If you really need to change them for some queries (which is not common) the application should do it at session level to avoid impacting the whole workload. Federico -------------------------------------------- Dom 23/4/17, Sales <info(a)smallbusinessconsultingexperts.com> ha scritto: Oggetto: Re: [Maria-discuss] Are some MyISAM settings used for Aria A: "Federico Razzoli" <federico_raz(a)yahoo.it> Cc: maria-discuss(a)lists.launchpad.net Data: Domenica 23 Aprile 2017, 22:59 > On Apr 23, 2017, at 3:00 PM, Federico Razzoli <federico_raz(a)yahoo.it> wrote: > > Steve, > > aria_used_for_temp_tables only affects internally created temporary tables, not the temp tables created explicitly by applications. > So I suggest: > * check if your applications create MyISAM (temporary) tables > * use the slow log (long_query_time=0, min_examine_rows=0) and pt-query-digest to check which queries are slower when you comment those settings > > Federico > Yes, the default engine for tables is innodb as evidenced by default_storage_engine, so, those are not using MyISAM. The default_tmp_storage_engine defaults to nothing, so, according to the doc, this means it uses default_storage_engine, which means innodb again. I was merely pointing out that all temp tables are not using MyISAM, or at least should not be. Have used the slow query log and Percona toolkit with various length settings and did not give much benefit sadly. It showed some queries running longer, but, that did not help too much as far as why since the queries were using optimal query paths. We have many long running queries and that’s fine as these are calculations and mass imports from suppliers, pricing, etc. We’ve just been unable to make sense of the why of it. A second potential hint is mariadb 10.1 has performed slower than mariadb 5.5 on the same machine, and thus far, we’ve been unable to isolate why. It’s not slower by a lot, maybe 5%. The word MyISAM does not exist anywhere in our code. Simple grep -ri shows this. It’s puzzling to me. Kind of makes me want to explicitly set default_tmp_storage_engine just to see if any effect. I am just checking if anything might still use MyISAM despite these settings. It’s not a big deal as the settings don’t use a tremendous amount of memory by any means, but, was hoping to just size MyISAM all the way down. And then became curious as to why this might be. Thanks!

1 0

[Maria-discuss] MariaDB Galera Cluster 5.5.55 and Connector/J 2.0.0 now available
by Daniel Bartholomew 22 Apr '17

22 Apr '17

The MariaDB project is pleased to announce the immediate availability of MariaDB Galera Cluster 5.5.55 Stable (GA) and MariaDB Connector/J 2.0.0 Release Candidate (RC). See the Release Notes and Changelogs for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB Galera Cluster 5.5.55 - Release Notes: https://mariadb.com/kb/en/mgc-5555-rn/ - Changelog: https://mariadb.com/kb/en/mgc-5555-cl/ - Downloads: https://downloads.mariadb.org/mariadb-galera/5.5.55 About MariaDB Galera Cluster: - https://mariadb.com/kb/en/what-is-mariadb-galera-cluster/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ MariaDB Connector/J 2.0.0 - Release Notes: https://mariadb.com/kb/en/mcj-200-rn/ - Changelog: https://mariadb.com/kb/en/mcj-200-cl/ - Downloads: https://downloads.mariadb.org/connector-java/2.0.0/ About MariaDB Connector/J: - https://mariadb.com/kb/en/about-mariadb-connector-j/ - - MariaDB Webinars - - - - - - - - - - - - - - - - - - - - - - - - - There are several upcoming MariaDB-focused webinars and many previously held ones available to watch on an on-demand basis at: - https://mariadb.com/news-events/webinars - - MariaDB Books - - - - - - - - - - - - - - - - - - - - - - - - - - There is an ever-growing library of MariaDB books available to help you get the most out of MariaDB. See the MariaDB Books page for details and links: - https://mariadb.com/kb/en/mariadb/books/ - - 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/donate/ We hope you enjoy MariaDB! -- MariaDB Website - http://mariadb.org Twitter - http://twitter.com/mariadbfdn - http://twitter.com/mariadb Google+ - http://google.com/+mariadb Facebook - http://fb.com/MariaDB.dbms Knowledge Base - http://mariadb.com/kb

1 0

Re: [Maria-discuss] MySQL Workbench Fork?
by Federico Razzoli 20 Apr '17

20 Apr '17

Looks like a lot of people want to use GUIs. Which is absolutely legit, but frankly, I don't agree that any database GUI should be considered enterprise software. Selecting checkboxes and selecting from drop-down menus is much slower, and much more error-prone, than writing SQL queries. I recognize that they allow you to avoid learning ALTER TABLE syntax, which potentially turns a person with no specific skill into a database architect. Is this an enterprise feature? Also, you never really know what you are doing. Some examples? * You read the database size. Where did the GUI read this value? I want to see system tables and file sizes, not values with vague names. * Ok, you just issued an SQL statement. But first, the GUI transparently ran tons of SET statements. What you did is what you wanted to do, or is it the random result of GUI's authors overactive creativity? :) Please, don't misunderstand me. I'm not saying that GUIs are useless or badly designed. But I wouldn't call them enterprise software, and I would not suggest them in a professional environment. Cheers, Federico -------------------------------------------- Gio 20/4/17, <info(a)smallbusinessconsultingexperts.com> ha scritto: Oggetto: Re: [Maria-discuss] MySQL Workbench Fork? A: maria-discuss(a)lists.launchpad.net, "Zach Lym" <zachlym(a)indolering.com> Data: Giovedì 20 Aprile 2017, 21:51 Totally agree. It's an necessary part for us. So many features missing. Tired of their warning too about mariadb. Steve Fatula On Apr 20, 2017, 2:13 PM -0500, Zach Lym <zachlym(a)indolering.com>, wrote: I convinced my boss to use MariaDB for a new project but it appears that the workbench is incompatible with new features of MariaDB. I've looked at the alternatives listed on the website, but they are all either proprietary or Windows only. I just can't sell my boss on switching to MariaDB without workbench. Free software isn't free, but I think Workbench is a big driver of commercial and enterprise use. It's easy to kvetch from the outside, but I feel as though MariaDB has just lost some ground. Has management considered forking Workbench? Thank you, -Zach Lym _______________________________________________ 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 _______________________________________________ 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

1 0

[Maria-discuss] innodb table single column index max length
by butler 18 Apr '17

18 Apr '17

we know the mysql have a limit that the max index length on a single column is 767.I want know how the 767 come from ? why not 799 or 800 etc.

2 2

[Maria-discuss] MariaDB 10.3.0 Alpha and 5.5.55 Stable now available
by Daniel Bartholomew 18 Apr '17

18 Apr '17

The MariaDB project is pleased to announce the immediate availability of MariaDB 10.3.0 Alpha and MariaDB 5.5.55 Stable (GA). See the Release Notes and Changelog for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB 10.3.0 - Release Notes: https://mariadb.com/kb/en/mdb-1030-rn/ - Changelog: https://mariadb.com/kb/en/mdb-1030-cl/ - Downloads: https://downloads.mariadb.org/mariadb/10.3.0 About MariaDB 10.3: - https://mariadb.com/kb/en/what-is-mariadb-103/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ MariaDB 5.5.55 - Release Notes: https://mariadb.com/kb/en/mdb-5555-rn/ - Changelog: https://mariadb.com/kb/en/mdb-5555-cl/ - Downloads: https://downloads.mariadb.org/mariadb/5.5.55 About MariaDB 5.5: - https://mariadb.com/kb/en/what-is-mariadb-55/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ - - MariaDB Webinars - - - - - - - - - - - - - - - - - - - - - - - - - There are several upcoming MariaDB-focused webinars and many previously held ones available to watch on an on-demand basis at: - https://mariadb.com/news-events/webinars - - MariaDB Books - - - - - - - - - - - - - - - - - - - - - - - - - - There is an ever-growing library of MariaDB books available to help you get the most out of MariaDB. See the MariaDB Books page for details and links: - https://mariadb.com/kb/en/mariadb/books/ - - 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/donate/ We hope you enjoy MariaDB! -- MariaDB Website - http://mariadb.org Twitter - http://twitter.com/mariadbfdn - http://twitter.com/mariadb Google+ - http://google.com/+mariadb Facebook - http://fb.com/MariaDB.dbms Knowledge Base - http://mariadb.com/kb

1 0

[Maria-discuss] logrotate
by Daniel Black 17 Apr '17

17 Apr '17

Quick proof of concept logrotate that hasn't really been changed in a while. The aim is to get this closer to a state for distro maintainers to use directly. By using a dedicated SQL user this shouldn't conflict with an existing user root user (which users always use despite the ability create other users with SUPER privs). As users will occasional change the password on the root without taking into account that logrotate typically uses the same user. Relying on users to update /root/.my.cnf is unreliable. Giving selinux permissions to allow logrotate read files under /root is also a little excessive. Using a dedicated mysqladmin.logrotate this won't conflict with existing mysqladmin group. Adds slow query log and general log to the logrotate script. Binary logs are deliberately omitted (MDEV-11610). https://mariadb.com/kb/en/mariadb/sql_error_log-plugin/ seems to have its own rotation) Proposed changes: https://github.com/MariaDB/server/compare/10.2...grooverdan:10.2-logrotate?… mysqladmin --local uses SET SESSION SQL_LOG_BIN=0 so I'll change its implementation to use FLUSH LOCAL ... which would preserve the need to use RELOAD only privs for logrotate. Thoughts? Difficulties? Suggestions? ref: https://jira.mariadb.org/browse/MDEV-11610 https://jira.mariadb.org/browse/MDEV-5662

3 4

[Maria-discuss] Help explain what a SQL line was INTENDING to do?
by David Karr 17 Apr '17

17 Apr '17

I've used Mariadb for a couple of small projects. I prefer to automate as much of the initial creation and config as possible, using SQL scripts executed from JDBC. I can at least do this for the table creation and population. I'm taking over an existing small project that is organized somewhat funky. There are some scripts that are apparently intended to initialize the database, but I'm seeing one line in one of those scripts that I don't understand, and I don't think is valid. I would appreciate some help explaining what you think this line MIGHT be intending to do: ----------------- ALTER TABLE `project` add column (proj_typ_id TINYINT(2) NOT NULL DEFAULT 1, parent_proj_id int(11, has_children BOOLEAN); ----------------- The first problem is that first paren. There's no matching right paren, so I can't imagine this can succeed. Second, I don't understand much past that first comma. Is this intending to add TWO columns, the second being "parent_proj_id"? Assuming that's the case, what exactly does "int(11, has_children BOOLEAN)" mean? I can see that it's declaring an 11-digit int, but I don't understand the "has_children" part.

2 2

Re: [Maria-discuss] "Error: MySQL server has gone away" issue while running mariadb database
by Daniel Black 12 Apr '17

12 Apr '17

On 11/04/17 15:15, Geunsik Lim wrote: > For reference, We are running web-based front service > with nodejs package + pm2 (http://pm2.keymetrics.io/) on Ubuntu 16.04.1 > server. > > It seems that this issue results from the too big packet size and too > long waiting time > between mariadb server and our nodejs-based web-service. its probably one or the other but not both.. MySQL document is still applicable https://dev.mysql.com/doc/refman/5.7/en/gone-away.html

2 4

[Maria-discuss] "Error: MySQL server has gone away" issue while running mariadb database
by Geunsik Lim 11 Apr '17

11 Apr '17

Recently, I have often been getting the "Error:MySQL server has gone away" message after I enabled the multiple-user access in front web service. Here is logs. . . . Upper Omission . . . 2017-04-10 21:15:22.881 [INFO][socketio.js] socket disconnect 2017-04-10 21:15:23.858 [INFO][socketio.js] socket connection 2017-04-10 21:36:07.635 [INFO][socketio.js] socket disconnect 2017-04-10 21:36:16.635 [INFO][socketio.js] socket disconnect 2017-04-10 21:46:12.254 [INFO][socketio.js] socket disconnect 2017-04-10 21:46:12.255 [INFO][socketio.js] socket disconnect events.js:160 throw er; // Unhandled 'error' event ^ Error: MySQL server has gone away at Error (native) At this time, I have checked the status of mariadb server. Please, see a time stampe information from the below mariadb's status. As we can see, the mariadb server was not stopped or not restarted. root@mytizen:~# systemctl status mysql * mysql.service - LSB: Start and stop the mysql database server daemon Loaded: loaded (/etc/init.d/mysql; bad; vendor preset: enabled) Active: active (running) since 2017-04-10 15:35:34 KST; 15h ago Docs: man:systemd-sysv-generator(8) Process: 1982 ExecStart=/etc/init.d/mysql start (code=exited, status=0/SUCCESS) Tasks: 28 Memory: 131.6M CPU: 29.563s CGroup: /system.slice/mysql.service ├─2544 /bin/bash /usr/bin/mysqld_safe ├─2691 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib/mysql/plugin --user=my └─2692 logger -t mysqld -p daemon error 4월 10 15:35:31 mytizen mysqld[2692]: 170410 15:35:31 [Note] InnoDB: 128 rollback segment(s) are active. 4월 10 15:35:31 mytizen mysqld[2692]: 170410 15:35:31 [Note] InnoDB: Waiting for purge to start 4월 10 15:35:31 mytizen mysqld[2692]: 170410 15:35:31 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.34-79 4월 10 15:35:31 mytizen mysqld[2692]: 170410 15:35:31 [Note] Plugin 'FEEDBACK' is disabled. 4월 10 15:35:31 mytizen mysqld[2692]: 170410 15:35:31 [Note] Server socket created on IP: '127.0.0.1'. 4월 10 15:35:33 mytizen mysqld[2692]: 170410 15:35:33 [Note] /usr/sbin/mysqld: ready for connections. 4월 10 15:35:33 mytizen mysqld[2692]: Version: '10.0.29-MariaDB-0ubuntu0.16.04.1' socket: '/var/run/mysqld/mysqld.sock 4월 10 15:35:34 mytizen mysql[1982]: ...done. 4월 10 15:35:34 mytizen systemd[1]: Started LSB: Start and stop the mysql database server daemon. 4월 10 15:35:34 mytizen mysql[1982]: ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO) root@mytizen:~# root@mytizen:~# ------------------- root@mytizen:~# ls -al /var/run/mysqld/mysqld.sock srwxrwxrwx 1 mysql mysql 0 4 10 15:35 /var/run/mysqld/mysqld.sock After digging the operation functions from the mariadb source ( https://github.com/MariaDB/server) I could get some hints where the issue was generated. For example, a) storage/spider/spd_trx.cc (!conn->disable_reconnect) https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar… b) storage/cassandra/ha_cassandra.cc Anyone who experience a similar issue such as "Error: MySQL server has gone away" message? -- http://leemgs.fedorapeople.org Don't try to avoid pain if you fail. If you decided to face the challenges in life, you can gain a lot by giving your best. Cheolsang Jeong's Book & life --

1 1

[Maria-discuss] Page Compression in production and backup strategies
by Tim Kersten 10 Apr '17

10 Apr '17

Hi folks, Does anyone here use page compression ( https://mariadb.com/kb/en/mariadb/compression/ ) in production? (Or know folks who do?) What prompted my question was seeing that XtraBackup is not supported when using page compression. Given the popularity of the XtraBackup, I'm left wondering if there's some other backup strategy people use (especially since it's also used to sync and provision slaves), or if page compression is simply not used by folks who have master/slave setups, or perhaps don't require backups? Searching has not been helpful in my finding the answer, other than a pull request ( https://github.com/percona/percona-xtrabackup/pull/200 ) by Jan Lindstrom from last year. Hoping you can help, best regards, Tim

3 2

[Maria-discuss] Maraidb 10.1, Dependent Subqueries, much slower than 5.5
by Sales 07 Apr '17

07 Apr '17

We are noticing many dependent subqueries not working as well as they did on Mariadb 5.5, we’re having to add a force index. Relatively simple example: explain update Product_Master pm set Total_Inventory = (select sum(ifnull(pi.Quantity_On_Hand, pi.Other_Quantity)) from Product_Inventory_Summed pi where pi.Product_ID = pm.Product_ID group by pi.Product_ID); +------+--------------------+-------+-------+---------------+---------+---------+------+---------+-------------+ | id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra | +------+--------------------+-------+-------+---------------+---------+---------+------+---------+-------------+ | 1 | PRIMARY | pm | index | NULL | PRIMARY | 22 | NULL | 5001829 | | | 2 | DEPENDENT SUBQUERY | pi | ALL | PRIMARY | NULL | NULL | NULL | 1 | Using where | +------+--------------------+-------+-------+---------------+---------+---------+------+---------+——————+ This query runs in a couple of minutes on 5.5, runs for many many hours on 10.1 By adding the force index, it is back to “normal”. explain update Product_Master pm set Total_Inventory = (select sum(ifnull(pi.Quantity_On_Hand, pi.Other_Quantity)) from Product_Inventory_Summed pi force index (PRIMARY) where pi.Product_ID = pm.Product_ID group by pi.Product_ID); +------+--------------------+-------+-------+---------------+---------+---------+---------------------+---------+-------+ | id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra | +------+--------------------+-------+-------+---------------+---------+---------+---------------------+---------+-------+ | 1 | PRIMARY | pm | index | NULL | PRIMARY | 22 | NULL | 5001829 | | | 2 | DEPENDENT SUBQUERY | pi | ref | PRIMARY | PRIMARY | 22 | feeds.pm.Product_ID | 1 | | +------+--------------------+-------+-------+---------------+---------+---------+---------------------+---------+———+ We are using persistent statistics on both tables, so, it knows there are a lot of rows in each. I don’t see any optimizer switches that are turned off. Any hints as to why or is this a current limitation of 10.1? Steve

2 3

Re: [Maria-discuss] mysqladmin - flush failed: Unknown error
by Daniel Black 06 Apr '17

06 Apr '17

On 30/03/17 20:46, Matthew Pash wrote: > Morning Daniel, > > Thanks for your reply, I've been doing some more testing. The logrotate > script (below) currently runs fine when executed manually (sudo > logrotate -v -f /etc/logrotate.d/mysql) but fails when run overnight by > cron. > > /var/log/mysqld.log { > compress > daily > missingok > notifempty > rotate 3 > postrotate > if test -x /usr/bin/mysqladmin && /usr/bin/mysqladmin ping &>/dev/null > then > /usr/bin/mysqladmin flush-logs > fi > endscript > } > > I tweaked it last night to capture the output of the mysqladmin command > and it did this: > > /usr/bin/mysqladmin: connect to server at 'localhost' failed > error: 'Access denied for user 'root'@'localhost' (using password: NO)' > > Which makes me think the problem is more about cron than MariaDB. No, MariaDB doesn't have a passwordless root user that mysqladmin needs to issue the flush-logs command. I suspect that there was originally a root user with socket authentication this system. Even after fixing this the mysqld may not be able to create new logs in /var/log/. I'd normally expect /var/log/mysql to be owned by the mysql user and its configuration to log the error to a file in this directory. > I've > added some extra information gathering, so we'll see how it runs tonight. > > > On 27 March 2017 at 22:34, Daniel Black <daniel.black(a)au1.ibm.com > <mailto:daniel.black@au1.ibm.com>> wrote: > > I think you'll find that the mysql user don't have permissions to create > a new file in /var/log/. As such logrotate renames the file which is > still open by mysqld. As such it is now writing to mysqld.log.1. > > On 28/03/17 00:13, Matthew Pash wrote: > > Hi, > > > > We've got some database servers running MariaDB 10.1.22, and are having > > issues with logrotate. Specifically, after it runs, it leaves a 0 byte > > file and continues writing log data to mysqld.log.1 > > > > Manually running logrotate in verbose mode shows this error from > > mysqladmin when it tries to run -flush_logs: > > > > /usr/bin/mysqladmin: flush failed; error: 'Unknown error' > > error: error running non-shared postrotate script for > > /var/log/mysqld.log of '/var/log/mysqld.log ' > > set default create context > > What does the logrotate script look like? It really should be a "shared" > (in a logrotate way) script. > > > > > Has anyone seen this before? It doesn't look like a permissions error - > > the logs are created fine if you run systemctl restart mariadb. > > Is the log actually writing to /var/log/mysqld.log using systemd? It > normally writes to the journal because with systemd redirects stderr > there > > > From lsof, it looks like /var/log/mysqld.log is being written to by the > mysql process itself: > $ sudo lsof | grep mysqld.log > mysqld 38803 mysql 1w REG 8,3 > 31781 537216904 /var/log/mysqld.log.1 > mysqld 38803 mysql 2w REG 8,3 > 31781 537216904 /var/log/mysqld.log.1 > ... > > > > > > Thanks, > > ~Matt > > > > -- > > *Matthew* > > Senior Systems Administrator, IT Services > > University of Bristol > > > > > > _______________________________________________ > > Mailing list: https://launchpad.net/~maria-discuss > <https://launchpad.net/%7Emaria-discuss> > > Post to : maria-discuss(a)lists.launchpad.net > <mailto:maria-discuss@lists.launchpad.net> > > Unsubscribe : https://launchpad.net/~maria-discuss > <https://launchpad.net/%7Emaria-discuss> > > More help : https://help.launchpad.net/ListHelp > <https://help.launchpad.net/ListHelp> > > > > > > > -- > *Matthew Pash* > Senior Systems Administrator, IT Services > University of Bristol

2 1

[Maria-discuss] MariaDB 10.2.5 RC now available
by Daniel Bartholomew 05 Apr '17

05 Apr '17

The MariaDB project is pleased to announce the immediate availability of MariaDB 10.2.5 Release Candidate (RC). See the Release Notes and Changelog for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB 10.2.5 - Release Notes: https://mariadb.com/kb/en/mdb-1025-rn/ - Changelog: https://mariadb.com/kb/en/mdb-1025-cl/ - Downloads: https://downloads.mariadb.org/mariadb/10.2.5 About MariaDB 10.2: - https://mariadb.com/kb/en/what-is-mariadb-102/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ - - MariaDB Webinars - - - - - - - - - - - - - - - - - - - - - - - - - There are several upcoming MariaDB-focused webinars and many previously held ones available to watch on an on-demand basis at: - https://mariadb.com/news-events/webinars - - MariaDB Books - - - - - - - - - - - - - - - - - - - - - - - - - - There is an ever-growing library of MariaDB books available to help you get the most out of MariaDB. See the MariaDB Books page for details and links: - https://mariadb.com/kb/en/mariadb/books/ - - 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/donate/ We hope you enjoy MariaDB! -- MariaDB Website - http://mariadb.org Twitter - http://twitter.com/mariadbfdn - http://twitter.com/mariadb Google+ - http://google.com/+mariadb Facebook - http://fb.com/MariaDB.dbms Knowledge Base - http://mariadb.com/kb

1 0

[Maria-discuss] NOT AGAIN PLEASE
by Federico Razzoli 05 Apr '17

05 Apr '17

Periodically this list becomes an early 90's fashion BBS. For days. It is very interesting to discuss how every single human being except one is an idiot who don't reply messages correctly to emails but 1- After some years, if you didn't convince anyone, maybe you are not totally right. 2- It is a bit off topic here. Maybe setup a list like use-reply-correctly-or-die(a)lists.launchpad.net and use this list to talk about MariaDB? 3- Yes, I wrote the subject in uppercase and killing me is still illegal. What a nasty world. Thanks. Federico -------------------------------------------- Mer 5/4/17, Reindl Harald <h.reindl(a)thelounge.net> ha scritto: Oggetto: Re: [Maria-discuss] searching for etc/my.cnf and CMAKE_INSTALL_PREFIX A: "Maria Discuss" <maria-discuss(a)lists.launchpad.net> Data: Mercoledì 5 Aprile 2017, 19:23 Am 05.04.2017 um 19:14 schrieb MARK CALLAGHAN: > Why do you need to shout about this? why don't you bring ANY specific reasoining for your sloppy "Maybe someone should edit the too strong claims" - anyways - if someone is too dumb to respond just to the list instead reply-all and convert plaintext mails in the quote to HTML all is said.... > On Wed, Apr 5, 2017 at 10:04 AM, Reindl Harald <h.reindl(a)thelounge.net > <mailto:h.reindl@thelounge.net>> wrote: > > > > Am 05.04.2017 um 18:57 schrieb MARK CALLAGHAN: > > It is different from upstream MySQL in many ways as that page > explains. > > > bla - if it woul dbe just a recompile from the mysql sources it > would not be a fork - in 99.9% of all cases IT IS a > drop-in-replacement - if you have REAL issues name them - period > > On Wed, Apr 5, 2017 at 8:03 AM, Reindl Harald > <h.reindl(a)thelounge.net <mailto:h.reindl@thelounge.net> > <mailto:h.reindl@thelounge.net <mailto:h.reindl@thelounge.net>>> > wrote: > > and why? > > it is and where it isn't unintentional report it and help to > get it > fixed, that said from a admin which dozens of MariaDB > servers where > the datadir was originally created on Windows under MySQL > 3.x, got > moved in prduction for some years to MacOS, later to Linux > and now > is running MariaDB 10.1 just fine with the same datadirs and the > help of "mysql_upgrade" over the years > > > Am 05.04.2017 um 16:50 schrieb MARK CALLAGHAN: > > Maybe someone should edit the too strong claims > on > https://mariadb.com/kb/en/mariadb/mariadb-vs-mysql-compatibility/ > <https://mariadb.com/kb/en/mariadb/mariadb-vs-mysql-compatibility/> > > <https://mariadb.com/kb/en/mariadb/mariadb-vs-mysql-compatibility/ > <https://mariadb.com/kb/en/mariadb/mariadb-vs-mysql-compatibility/>> > > In bold at the top of the page... > > > MariaDB is a binary drop in replacement for MySQL > > > On Tue, Apr 4, 2017 at 9:58 PM, Sergei Golubchik > <serg(a)mariadb.org <mailto:serg@mariadb.org> > <mailto:serg@mariadb.org <mailto:serg@mariadb.org>>> wrote: > > Hi, Mark! > > On Apr 04, Mark Callaghan wrote: > > With upstream (5.6 and 5.7) MySQL when I use cmake > > -DCMAKE_INSTALL_PREFIX=$X, then after I install > the build, > mysqld searches > > in $X/etc for my.cnf. That is not true for MariaDB > Server > 10.2. Why can't > > this match upstream? > > > It certainly can. It just doesn't. Because we merge > from 5.6 into > MariaDB feature by feature, and nobody has requested > this > particular > feature so far. At least I couldn't find it in Jira. > > Regards, > Sergei > Chief Architect MariaDB > and security(a)mariadb.org > <mailto:security@mariadb.org> <mailto:security@mariadb.org > <mailto:security@mariadb.org>> _______________________________________________ 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

2 1

[Maria-discuss] restore db from dump?
by l vic 05 Apr '17

05 Apr '17

Hello, I have "mydump.sql" with dump of all databases in cluster. I am trying to selectively restore one database only from the scenario below: Have created 2 databases: test1 and test2 with table "person": +-------+--------------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +-------+--------------+------+-----+---------+-------+ | name | varchar(255) | YES | | NULL | | +-------+--------------+------+-----+---------+-------+ Insert name "one" into table "person" for both databases: insert into person values ('name'); Backup all data into "mysqldump.sql": mysqldump -P3306 -uroot -pdbpass --all-databases >mysqldump.sql drop database test2 (my mistake); and insert additional data into "test1": insert into person values ('name1'); insert into person values ('name2'); Now, i'd like to restore database test2 only: mysql -uroot -pdbpass -e "create database if not exists test2;" mysql -uroot -pdbpass test2 < mysqldump.sql Success !! test2 is restored with all the data, but when I'checked "test1" i only see one record "name" - two records that I've added after backup are lost It looks as mysql just restore all data in dump file, regardless of specifying the "target" database. Is that expected, or do i have some error in my backup/restore procedure? If this is expected, is there some comprehensive method to restore one database selectively? Thanks, vl

3 3

[Maria-discuss] searching for etc/my.cnf and CMAKE_INSTALL_PREFIX
by MARK CALLAGHAN 05 Apr '17

05 Apr '17

With upstream (5.6 and 5.7) MySQL when I use cmake -DCMAKE_INSTALL_PREFIX=$X, then after I install the build, mysqld searches in $X/etc for my.cnf. That is not true for MariaDB Server 10.2. Why can't this match upstream? -- Mark Callaghan mdcallag(a)gmail.com

3 8

Re: [Maria-discuss] searching for etc/my.cnf and CMAKE_INSTALL_PREFIX
by Federico Razzoli 05 Apr '17

05 Apr '17

Or maybe people can file bugs/feature requests when they think they have a "practical purpose". If those bugs are ignored, then yes, the page should be edited :) Federico -------------------------------------------- Mer 5/4/17, MARK CALLAGHAN <mdcallag(a)gmail.com> ha scritto: Oggetto: Re: [Maria-discuss] searching for etc/my.cnf and CMAKE_INSTALL_PREFIX A: "Sergei Golubchik" <serg(a)mariadb.org> Cc: "Maria Discuss" <maria-discuss(a)lists.launchpad.net> Data: Mercoledì 5 Aprile 2017, 16:50 Maybe someone should edit the too strong claims on https://mariadb.com/kb/en/mariadb/mariadb-vs-mysql-compatibility/ In bold at the top of the page... MariaDB is a binary drop in replacement for MySQL On Tue, Apr 4, 2017 at 9:58 PM, Sergei Golubchik <serg(a)mariadb.org> wrote: Hi, Mark! On Apr 04, Mark Callaghan wrote: > With upstream (5.6 and 5.7) MySQL when I use cmake > -DCMAKE_INSTALL_PREFIX=$X, then after I install the build, mysqld searches > in $X/etc for my.cnf. That is not true for MariaDB Server 10.2. Why can't > this match upstream? It certainly can. It just doesn't. Because we merge from 5.6 into MariaDB feature by feature, and nobody has requested this particular feature so far. At least I couldn't find it in Jira. Regards, Sergei Chief Architect MariaDB and security(a)mariadb.org -- Mark Callaghan mdcallag(a)gmail.com _______________________________________________ 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

1 0

[Maria-discuss] thanks for ROW
by Federico Razzoli 03 Apr '17

03 Apr '17

Dear MariaDB team, I have just read carefully this KB page: https://mariadb.com/kb/en/mariadb/row/ Thank you for implementing the ROW type in procedures. We talked about procedures limitations several times in this list, and this is clearly a step in increasing usability and power. Cheers, Federico

1 0

Re: [Maria-discuss] Cross compile error
by Daniel Black 01 Apr '17

01 Apr '17

On this error I'm not sure. Looks to be some sort of inheritance hierarchy that is different in musl from glibc et al. I'd chase them up to see who is violating the C++ spec. Have you tried using buildroot? It has a stable 10.1 version that is kept up to date and it has the one outstanding uclibc patch (that is waiting in jira https://jira.mariadb.org/browse/MDEV-10841) On 26/03/17 02:52, Lucian Cristian wrote: > Hi > > I'm trying to cross compile (any 10.* versions) using musl and uClibc++ > for a LEDE/Openwrt system and I have problems with these errors: > > > staging_dir/target-x86_64_musl/usr/include/uClibc++/associative_base:444:8: > error: 'void std::__base_associative<Key, ValueType, Compare, > Allocator>::swap(std::__base_associative<Key, ValueType, Compare, > Allocator>&) [with Key = dict_foreign_t*; ValueType = dict_foreign_t*; > Compare = dict_foreign_compare; Allocator = > ut_allocator<dict_foreign_t*>]' is protected > void __base_associative<Key, ValueType, Compare, > Allocator>::swap(__base_associative<Key, ValueType, Compare, Allocator>& m) > ^ > build_dir/target-x86_64_musl/mariadb-10.2.4/storage/innobase/dict/dict0dict.cc:1996:32: > error: within this context > table->foreign_set.swap(fk_set); > ^ > storage/innobase/CMakeFiles/innobase.dir/build.make:542: recipe for > target 'storage/innobase/CMakeFiles/innobase.dir/dict/dict0dict.cc.o' > failed > > > > staging_dir/target-x86_64_musl/usr/include/uClibc++/map: In > instantiation of 'std::map<Key, T, Compare, Allocator>::reference > std::map<Key, T, Compare, Allocator>::operator[](const key_type&) [with > Key = const char*; T = dict_index_t*; Compare = ut_strcmp_functor; > Allocator = ut_allocator<std::pair<const char*, dict_index_t*> >; > std::map<Key, T, Compare, Allocator>::reference = std::pair<const char*, > dict_index_t*>&; std::map<Key, T, Compare, Allocator>::key_type = const > char*]': > build_dir/target-x86_64_musl/mariadb-10.2.4/storage/innobase/dict/dict0stats.cc:2518:22: > required from here > staging_dir/target-x86_64_musl/usr/include/uClibc++/map:143:13: error: > invalid initialization of reference of type 'std::map<const char*, > dict_index_t*, ut_strcmp_functor, ut_allocator<std::pair<const char*, > dict_index_t*> > >::reference {aka std::pair<const char*, > dict_index_t*>&}' from expression of type 'dict_index_t*' > return i->second; > ^ > storage/innobase/CMakeFiles/innobase.dir/build.make:614: recipe for > target 'storage/innobase/CMakeFiles/innobase.dir/dict/dict0stats.cc.o' > failed > > > > build_dir/target-x86_64_musl/mariadb-10.2.4/plugin/handler_socket/handlersocket/hstcpsvr.cpp: > In constructor 'dena::hstcpsvr::hstcpsvr(const dena::config&)': > build_dir/target-x86_64_musl/mariadb-10.2.4/plugin/handler_socket/handlersocket/hstcpsvr.cpp:92:37: > error: invalid initialization of non-const reference of type > 'std::auto_ptr<volatile dena::database_i>&' from an rvalue of type > 'dena::database_ptr {aka std::auto_ptr<volatile dena::database_i>}' > cshared.dbptr = database_i::create(c); > ^ > In file included from > staging_dir/target-x86_64_musl/usr/include/uClibc++/vector:22:0, > from > build_dir/target-x86_64_musl/mariadb-10.2.4/plugin/handler_socket/handlersocket/hstcpsvr.cpp:12: > > staging_dir/target-x86_64_musl/usr/include/uClibc++/memory:137:12: > note: initializing argument 1 of 'std::auto_ptr<T>& > std::auto_ptr<T>::operator=(std::auto_ptr<T>&) [with T = volatile > dena::database_i]' > auto_ptr& operator=(auto_ptr& p) throw(){ > ^ > plugin/handler_socket/CMakeFiles/handlersocket.dir/build.make:134: > recipe for target > 'plugin/handler_socket/CMakeFiles/handlersocket.dir/handlersocket/hstcpsvr.cpp.o' > failed > make[5]: *** > [plugin/handler_socket/CMakeFiles/handlersocket.dir/handlersocket/hstcpsvr.cpp.o] > Error 1 > > > this is the command line > > (cd /build_dir/target-x86_64_musl/mariadb-10.2.4; CFLAGS="-Os -pipe > -fno-caller-saves -fno-plt -fhonour-copts > -Wno-error=unused-but-set-variable -Wno-error=unused-result > -iremap/build_dir/target-x86_64_musl/mariadb-10.2.4:mariadb-10.2.4 > -Wformat -Werror=format-security -fstack-protector -D_FORTIFY_SOURCE=1 > -Wl,-z,now -Wl,-z,relro -fpic " CXXFLAGS="-Os -pipe -fno-caller-saves > -fno-plt -fhonour-copts -Wno-error=unused-but-set-variable > -Wno-error=unused-result > -iremap/build_dir/target-x86_64_musl/mariadb-10.2.4:mariadb-10.2.4 > -Wformat -Werror=format-security -fstack-protector -D_FORTIFY_SOURCE=1 > -Wl,-z,now -Wl,-z,relro -fpic " > LDFLAGS="-L/staging_dir/target-x86_64_musl/usr/lib > -L/staging_dir/target-x86_64_musl/lib > -L/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/usr/lib > -L/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/lib -znow -zrelro " cmake > -DCMAKE_SYSTEM_NAME=Linux -DCMAKE_SYSTEM_VERSION=1 > -DCMAKE_SYSTEM_PROCESSOR=x86_64 -DCMAKE_BUILD_TYPE=Release > -DCMAKE_C_FLAGS_RELEASE="-DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-DNDEBUG" > -DCMAKE_C_COMPILER="/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/bin/x86_64-openwrt-linux-musl-gcc" > -DCMAKE_C_COMPILER_ARG1="" > -DCMAKE_CXX_COMPILER="/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/bin/g++-uc" > -DCMAKE_CXX_COMPILER_ARG1="" > -DCMAKE_ASM_COMPILER="/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/bin/x86_64-openwrt-linux-musl-gcc" > -DCMAKE_ASM_COMPILER_ARG1="" > -DCMAKE_EXE_LINKER_FLAGS:STRING="-L/staging_dir/target-x86_64_musl/usr/lib > -L/staging_dir/target-x86_64_musl/lib > -L/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/usr/lib > -L/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/lib -znow -zrelro" > -DCMAKE_MODULE_LINKER_FLAGS:STRING="-L/staging_dir/target-x86_64_musl/usr/lib > -L/staging_dir/target-x86_64_musl/lib > -L/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/usr/lib > -L/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/lib -znow -zrelro > -Wl,-Bsymbolic-functions" > -DCMAKE_SHARED_LINKER_FLAGS:STRING="-L/staging_dir/target-x86_64_musl/usr/lib > -L/staging_dir/target-x86_64_musl/lib > -L/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/usr/lib > -L/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/lib -znow -zrelro > -Wl,-Bsymbolic-functions" > -DCMAKE_AR="/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/bin/x86_64-openwrt-linux-musl-gcc-ar" > -DCMAKE_NM="/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/bin/x86_64-openwrt-linux-musl-gcc-nm" > -DCMAKE_RANLIB="/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/bin/x86_64-openwrt-linux-musl-gcc-ranlib" > -DCMAKE_FIND_ROOT_PATH="/staging_dir/target-x86_64_musl/usr;/staging_dir/toolchain-x86_64_gcc-5.4.0_musl" > -DCMAKE_FIND_ROOT_PATH_MODE_PROGRAM=BOTH > -DCMAKE_FIND_ROOT_PATH_MODE_LIBRARY=ONLY > -DCMAKE_FIND_ROOT_PATH_MODE_INCLUDE=ONLY -DCMAKE_STRIP=: > -DCMAKE_INSTALL_PREFIX=/usr -DDL_LIBRARY=/staging_dir/target-x86_64_musl > -DCMAKE_PREFIX_PATH=/staging_dir/target-x86_64_musl > -DCMAKE_SKIP_RPATH=TRUE -DCMAKE_SYSTEM_NAME=Linux -DSTACK_DIRECTION=-1 > -DWITH_WSREP=ON -DWITH_INNODB_DISALLOW_WRITES=1 -DCONNECT_WITH_JDBC=OFF > -DWITHOUT_TOKUDB=1 > -DIMPORT_EXECUTABLES=/build_dir/hostpkg/mariadb-10.2.4/host/import_executables.cmake > /build_dir/target-x86_64_musl/mariadb-10.2.4 ) > > > can someone give me an advice ? > > Regards > > > _______________________________________________ > 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 >

2 1

[Maria-discuss] MariaDB memory usage
by Selvam 31 Mar '17

31 Mar '17

Hi, Hi, I have MariaDB 10.1.19 with 1 GB of RAM on (AWS RDS) and another one with 4 GB of RAM (production instance). Memory usage keeps on increasing on both. Free memory goes below 50MB. InnoDB status shows "History list length 2671". My total table count is 225 and shows around 10 GB of data for them. I am giving the InnoDB engine status for your reference below, I would be happy to get any pointers on this issue. ===================================== 2017-03-31 10:53:08 2b25f6ec2700 INNODB MONITOR OUTPUT ===================================== Per second averages calculated from the last 41 seconds ----------------- BACKGROUND THREAD ----------------- srv_master_thread loops: 6695 srv_active, 0 srv_shutdown, 187084 srv_idle srv_master_thread log flush and writes: 193768 ---------- SEMAPHORES ---------- OS WAIT ARRAY INFO: reservation count 77210 OS WAIT ARRAY INFO: signal count 212544 Mutex spin waits 201779, rounds 289254, OS waits 5769 RW-shared spins 71644, rounds 1292843, OS waits 28918 RW-excl spins 27933, rounds 1582253, OS waits 41414 Spin rounds per wait: 1.43 mutex, 18.05 RW-shared, 56.64 RW-excl ------------ TRANSACTIONS ------------ Trx id counter 106794202 Purge done for trx's n:o < 106794191 undo n:o < 0 state: running but idle History list length 3618 LIST OF TRANSACTIONS FOR EACH SESSION: ---TRANSACTION 106794062, not started MySQL thread id 110715, OS thread handle 0x2b25f6ec2700, query id 5020955 182.71.229.138 ebuser init SHOW ENGINE INNODB STATUS ---TRANSACTION 106794201, not started MySQL thread id 8, OS thread handle 0x2b25a2703700, query id 5020954 localhost 127.0.0.1 rdsadmin cleaning up ---TRANSACTION 106028547, not started MySQL thread id 1, OS thread handle 0x2b25a2681700, query id 0 Waiting for background binlog tasks -------- FILE I/O -------- I/O thread 0 state: waiting for completed aio requests (insert buffer thread) I/O thread 1 state: waiting for completed aio requests (log thread) I/O thread 2 state: waiting for completed aio requests (read thread) I/O thread 3 state: waiting for completed aio requests (read thread) I/O thread 4 state: waiting for completed aio requests (read thread) I/O thread 5 state: waiting for completed aio requests (read thread) I/O thread 6 state: waiting for completed aio requests (write thread) I/O thread 7 state: waiting for completed aio requests (write thread) I/O thread 8 state: waiting for completed aio requests (write thread) I/O thread 9 state: waiting for completed aio requests (write thread) Pending normal aio reads: 0 [0, 0, 0, 0] , aio writes: 0 [0, 0, 0, 0] , ibuf aio reads: 0, log i/o's: 0, sync i/o's: 0 Pending flushes (fsync) log: 0; buffer pool: 0 748253 OS file reads, 1159722 OS file writes, 187669 OS fsyncs 0.00 reads/s, 0 avg bytes/read, 0.00 writes/s, 0.00 fsyncs/s ------------------------------------- INSERT BUFFER AND ADAPTIVE HASH INDEX ------------------------------------- Ibuf: size 1, free list len 101, seg size 103, 63021 merges merged operations: insert 49746, delete mark 141267, delete 44296 discarded operations: insert 0, delete mark 0, delete 0 29.05 hash searches/s, 1.85 non-hash searches/s --- LOG --- Log sequence number 150636062402 Log flushed up to 150636062402 Pages flushed up to 150636062402 Last checkpoint at 150636062402 Max checkpoint age 216721613 Checkpoint age target 209949063 Modified age 0 Checkpoint age 0 0 pending log writes, 0 pending chkp writes 138085 log i/o's done, 0.00 log i/o's/second ---------------------- BUFFER POOL AND MEMORY ---------------------- Total memory allocated 3021996032; in additional pool allocated 0 Total memory allocated by read views 416 Internal hash tables (constant factor + variable factor) Adaptive hash index 262562512 (46748264 + 215814248) Page hash 366056 (buffer pool 0 only) Dictionary cache 13611078 (11688592 + 1922486) File system 960472 (812272 + 148200) Lock system 7306496 (7305416 + 1080) Recovery system 0 (0 + 0) Dictionary memory allocated 1922486 Buffer pool size 180216 Buffer pool size, bytes 2952658944 Free buffers 8193 Database pages 158851 Old database pages 58475 Modified db pages 0 Percent of dirty pages(LRU & free pages): 0.000 Max dirty pages percent: 75.000 Pending reads 0 Pending writes: LRU 0, flush list 0, single page 0 Pages made young 1247738, not young 25033050 0.00 youngs/s, 0.00 non-youngs/s Pages read 748000, created 43142, written 994180 0.00 reads/s, 0.00 creates/s, 0.00 writes/s Buffer pool hit rate 1000 / 1000, young-making rate 0 / 1000 not 0 / 1000 Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s LRU len: 158851, unzip_LRU len: 0 I/O sum[0]:cur[0], unzip sum[0]:cur[0] ---------------------- INDIVIDUAL BUFFER POOL INFO ---------------------- ---BUFFER POOL 0 Buffer pool size 22527 Buffer pool size, bytes 369082368 Free buffers 1025 Database pages 19861 Old database pages 7311 Modified db pages 0 Percent of dirty pages(LRU & free pages): 0.000 Max dirty pages percent: 75.000 Pending reads 0 Pending writes: LRU 0, flush list 0, single page 0 Pages made young 98238, not young 2723636 0.00 youngs/s, 0.00 non-youngs/s Pages read 92864, created 5425, written 135077 0.00 reads/s, 0.00 creates/s, 0.00 writes/s Buffer pool hit rate 1000 / 1000, young-making rate 0 / 1000 not 0 / 1000 Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s LRU len: 19861, unzip_LRU len: 0 I/O sum[0]:cur[0], unzip sum[0]:cur[0] ---BUFFER POOL 1 Buffer pool size 22527 Buffer pool size, bytes 369082368 Free buffers 1024 Database pages 19853 Old database pages 7308 Modified db pages 0 Percent of dirty pages(LRU & free pages): 0.000 Max dirty pages percent: 75.000 Pending reads 0 Pending writes: LRU 0, flush list 0, single page 0 Pages made young 95625, not young 3098260 0.00 youngs/s, 0.00 non-youngs/s Pages read 89244, created 5544, written 116844 0.00 reads/s, 0.00 creates/s, 0.00 writes/s Buffer pool hit rate 1000 / 1000, young-making rate 0 / 1000 not 0 / 1000 Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s LRU len: 19853, unzip_LRU len: 0 I/O sum[0]:cur[0], unzip sum[0]:cur[0] ---BUFFER POOL 2 Buffer pool size 22527 Buffer pool size, bytes 369082368 Free buffers 1024 Database pages 19851 Old database pages 7307 Modified db pages 0 Percent of dirty pages(LRU & free pages): 0.000 Max dirty pages percent: 75.000 Pending reads 0 Pending writes: LRU 0, flush list 0, single page 0 Pages made young 128795, not young 3109159 0.00 youngs/s, 0.00 non-youngs/s Pages read 96654, created 5166, written 121945 0.00 reads/s, 0.00 creates/s, 0.00 writes/s Buffer pool hit rate 1000 / 1000, young-making rate 0 / 1000 not 0 / 1000 Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s LRU len: 19851, unzip_LRU len: 0 I/O sum[0]:cur[0], unzip sum[0]:cur[0] ---BUFFER POOL 3 Buffer pool size 22527 Buffer pool size, bytes 369082368 Free buffers 1024 Database pages 19847 Old database pages 7306 Modified db pages 0 Percent of dirty pages(LRU & free pages): 0.000 Max dirty pages percent: 75.000 Pending reads 0 Pending writes: LRU 0, flush list 0, single page 0 Pages made young 305308, not young 4040408 0.00 youngs/s, 0.00 non-youngs/s Pages read 96897, created 5125, written 135851 0.00 reads/s, 0.00 creates/s, 0.00 writes/s Buffer pool hit rate 1000 / 1000, young-making rate 0 / 1000 not 0 / 1000 Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s LRU len: 19847, unzip_LRU len: 0 I/O sum[0]:cur[0], unzip sum[0]:cur[0] ---BUFFER POOL 4 Buffer pool size 22527 Buffer pool size, bytes 369082368 Free buffers 1024 Database pages 19852 Old database pages 7308 Modified db pages 0 Percent of dirty pages(LRU & free pages): 0.000 Max dirty pages percent: 75.000 Pending reads 0 Pending writes: LRU 0, flush list 0, single page 0 Pages made young 128721, not young 3047134 0.00 youngs/s, 0.00 non-youngs/s Pages read 94024, created 5765, written 126032 0.00 reads/s, 0.00 creates/s, 0.00 writes/s Buffer pool hit rate 1000 / 1000, young-making rate 0 / 1000 not 0 / 1000 Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s LRU len: 19852, unzip_LRU len: 0 I/O sum[0]:cur[0], unzip sum[0]:cur[0] ---BUFFER POOL 5 Buffer pool size 22527 Buffer pool size, bytes 369082368 Free buffers 1024 Database pages 19860 Old database pages 7311 Modified db pages 0 Percent of dirty pages(LRU & free pages): 0.000 Max dirty pages percent: 75.000 Pending reads 0 Pending writes: LRU 0, flush list 0, single page 0 Pages made young 146912, not young 2641167 0.00 youngs/s, 0.00 non-youngs/s Pages read 94359, created 5540, written 120390 0.00 reads/s, 0.00 creates/s, 0.00 writes/s Buffer pool hit rate 1000 / 1000, young-making rate 0 / 1000 not 0 / 1000 Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s LRU len: 19860, unzip_LRU len: 0 I/O sum[0]:cur[0], unzip sum[0]:cur[0] ---BUFFER POOL 6 Buffer pool size 22527 Buffer pool size, bytes 369082368 Free buffers 1024 Database pages 19872 Old database pages 7315 Modified db pages 0 Percent of dirty pages(LRU & free pages): 0.000 Max dirty pages percent: 75.000 Pending reads 0 Pending writes: LRU 0, flush list 0, single page 0 Pages made young 96242, not young 3087412 0.00 youngs/s, 0.00 non-youngs/s Pages read 88868, created 4950, written 119917 0.00 reads/s, 0.00 creates/s, 0.00 writes/s Buffer pool hit rate 1000 / 1000, young-making rate 0 / 1000 not 0 / 1000 Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s LRU len: 19872, unzip_LRU len: 0 I/O sum[0]:cur[0], unzip sum[0]:cur[0] ---BUFFER POOL 7 Buffer pool size 22527 Buffer pool size, bytes 369082368 Free buffers 1024 Database pages 19855 Old database pages 7309 Modified db pages 0 Percent of dirty pages(LRU & free pages): 0.000 Max dirty pages percent: 75.000 Pending reads 0 Pending writes: LRU 0, flush list 0, single page 0 Pages made young 247897, not young 3285874 0.00 youngs/s, 0.00 non-youngs/s Pages read 95090, created 5627, written 118124 0.00 reads/s, 0.00 creates/s, 0.00 writes/s Buffer pool hit rate 1000 / 1000, young-making rate 0 / 1000 not 0 / 1000 Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s LRU len: 19855, unzip_LRU len: 0 I/O sum[0]:cur[0], unzip sum[0]:cur[0] -------------- ROW OPERATIONS -------------- 0 queries inside InnoDB, 0 queries in queue 0 read views open inside InnoDB 0 RW transactions active inside InnoDB 0 RO transactions active inside InnoDB 0 out of 1000 descriptors used Main thread process no. 9357, id 47444582741760, state: sleeping Number of rows inserted 1455191, updated 16167028, deleted 1399680, read 1844055639 0.00 inserts/s, 0.00 updates/s, 0.00 deletes/s, 30.83 reads/s Number of system rows inserted 3, updated 641, deleted 3, read 20758 0.00 inserts/s, 0.00 updates/s, 0.00 deletes/s, 0.12 reads/s ---------------------------- END OF INNODB MONITOR OUTPUT ============================ -- Regards, Selvam KnackForge <http://knackforge.com>

1 0

[Maria-discuss] semi-sync replication rpl_semi_sync_master_clients question ?
by Ljr Yang 29 Mar '17

29 Mar '17

HI, we have many groups master slave , used semi-sync are normal. but there a group master and slave , semi-sync status show have a little question. master: 10.1.0.61 (MariaDB 10.1.22) slave1 : 10.1.0.62 (MariaDB 10.1.22) slave2: 10.1.0.63 (MariaDB 10.1.22) three machine's semi-sync parameter: rpl_semi_sync_master_enabled ON rpl_semi_sync_master_timeout 10000 rpl_semi_sync_master_wait_point AFTER_COMMIT rpl_semi_sync_slave_enabled ON on master: SHOW GLOBAL STATUS LIKE '%semi%' ; *Rpl_semi_sync_master_clients 1 # should show : 2 * ...... on slave1: stop slave io_thread; then on master: SHOW GLOBAL STATUS LIKE '%semi%' ; *Rpl_semi_sync_master_clients ０* on slave1: start slave io_thread; on master: SHOW GLOBAL STATUS LIKE '%semi%' ; *Rpl_semi_sync_master_clients 1* on slave2: stop slave io_thread; then on master: SHOW GLOBAL STATUS LIKE '%semi%' ; *Rpl_semi_sync_master_clients ０* on slave2: start slave io_thread; on master: SHOW GLOBAL STATUS LIKE '%semi%' ; *Rpl_semi_sync_master_clients 1* *on slave1 and slave2 , I had uninstall and reinstall semi-sync plugin, * *still show **Rpl_semi_sync_master_clients is 1* I don't know where config have question? please you help, thanks

2 4

[Maria-discuss] mysqladmin - flush failed: Unknown error
by Matthew Pash 27 Mar '17

27 Mar '17

Hi, We've got some database servers running MariaDB 10.1.22, and are having issues with logrotate. Specifically, after it runs, it leaves a 0 byte file and continues writing log data to mysqld.log.1 Manually running logrotate in verbose mode shows this error from mysqladmin when it tries to run -flush_logs: /usr/bin/mysqladmin: flush failed; error: 'Unknown error' error: error running non-shared postrotate script for /var/log/mysqld.log of '/var/log/mysqld.log ' set default create context Has anyone seen this before? It doesn't look like a permissions error - the logs are created fine if you run systemctl restart mariadb. Thanks, ~Matt -- *Matthew* Senior Systems Administrator, IT Services University of Bristol

2 1

[Maria-discuss] MariaDB Galera Cluster 10.0.30 and Connector/J 1.5.9 now available
by Daniel Bartholomew 22 Mar '17

22 Mar '17

The MariaDB project is pleased to announce the immediate availability of MariaDB Galera Cluster 10.0.30 and MariaDB Connector/J 1.5.9. These are both stable (GA) releases. See the Release Notes and Changelogs for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB Galera Cluster 10.0.30 - Release Notes: https://mariadb.com/kb/en/mgc-10030-rn/ - Changelog: https://mariadb.com/kb/en/mgc-10030-cl/ - Downloads: https://downloads.mariadb.org/mariadb-galera/10.0.30 About MariaDB Galera Cluster: - https://mariadb.com/kb/en/what-is-mariadb-galera-cluster/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ MariaDB Connector/J 1.5.9 - Release Notes: https://mariadb.com/kb/en/mcj-159-rn/ - Changelog: https://mariadb.com/kb/en/mcj-159-cl/ - Downloads: https://downloads.mariadb.org/connector-java/1.5.9/ About MariaDB Connector/J: - https://mariadb.com/kb/en/about-mariadb-connector-j/ - - Developers Meetup and M|17 User Conference in April - - - - - - - The MariaDB Foundation is hosting a MariaDB Developers Meetup from 9-10 April in New York City. This event is being held in conjunction with the MariaDB Corporation sponsored M|17 MariaDB User Conference being held from 11-12 April, also in NYC. Details on both events can be found at: - https://mariadb.org/2017-developers-meetup-new-york/ - https://m17.mariadb.com/ - - MariaDB Webinars - - - - - - - - - - - - - - - - - - - - - - - - - There are several upcoming MariaDB-focused webinars and many previously held ones available to watch on an on-demand basis at: - https://mariadb.com/news-events/webinars - - MariaDB Books - - - - - - - - - - - - - - - - - - - - - - - - - - There is an ever-growing library of MariaDB books available to help you get the most out of MariaDB. See the MariaDB Books page for details and links: - https://mariadb.com/kb/en/mariadb/books/ - - 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/donate/ We hope you enjoy MariaDB! -- MariaDB Website - http://mariadb.org Twitter - http://twitter.com/mariadbfdn - http://twitter.com/mariadb Google+ - http://google.com/+mariadb Facebook - http://fb.com/MariaDB.dbms Knowledge Base - http://mariadb.com/kb

1 0

[Maria-discuss] Can not build MariaDB 10.0.30 and 10.1.22 with Visual Studio 2013
by Ayano Kosaka 22 Mar '17

22 Mar '17

Hi, I can not build MariaDB 10.0.30 and 10.1.22 with Visual Studio 2013 on Windows 7 Pro 64 bit. `identifier "int64_t" is undefined` occurs at `storage/xtradb/btr/btr0cur.cc`. It is probably caused by the following merge commit: [Merge branch 'merge-xtradb-5.6' into 10.0] https://github.com/MariaDB/server/commit/83da1a1e572d67588b66724b34fdb7f079… Before this commit, `ib_int64_t` (the typedef, which wraps compiler differences, in `../include/univ.i`) is used instead of `int64_t`. This error does not occur on VS2015, because it has `int64_t`. But VS2013 does not have `int64_t`. Were the supported compilers changed? Or, a bug or my environmental problem? Regards, Ayano Kosaka

3 2

[Maria-discuss] Problem Upgrade MariaDb 5.5.52 MariaDb 10.1.22
by Wilmer Arambula 21 Mar '17

21 Mar '17

Hi, i have a system running perfectly on mariadb 5.5.52, i will change everything to a new server with mariadb 10.1.22, but running the installation script gives me problems, this is the error, is there any way to configure mariadb 10.1.22 To omit this error, since mariadb 10.1.22 works with strict-trans-table, there is some old_mode feature that allows this. QUERY: CREATE TABLE `media_gallery_music` ( `gallery_id` INT(11) UNSIGNED NOT NULL AUTO_INCREMENT, `value_id` INT(11) UNSIGNED NOT NULL, `artwork_url` VARCHAR(255) COLLATE utf8_unicode_ci NOT NULL, `name` VARCHAR(255) COLLATE utf8_unicode_ci NOT NULL, `position` INT(11) NOT NULL, PRIMARY KEY (`gallery_id`) ) ENGINE=INNODB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; CREATE TABLE `media_gallery_music_album` ( `album_id` INT(11) UNSIGNED NOT NULL AUTO_INCREMENT, `gallery_id` INT(11) UNSIGNED NOT NULL, `name` VARCHAR(255) COLLATE utf8_unicode_ci NOT NULL, `artwork_url` VARCHAR(255) COLLATE utf8_unicode_ci DEFAULT NULL, `podcast_url` VARCHAR(255) COLLATE utf8_unicode_ci DEFAULT NULL, `artist_name` VARCHAR(255) COLLATE utf8_unicode_ci DEFAULT NULL, `type` VARCHAR(255) COLLATE utf8_unicode_ci DEFAULT NULL, PRIMARY KEY (`album_id`), KEY `KEY_GALLERY_ID` (`gallery_id`) ) ENGINE=INNODB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; CREATE TABLE `media_gallery_music_elements` ( `position_id` INT(11) UNSIGNED NOT NULL AUTO_INCREMENT, `gallery_id` INT(11) UNSIGNED DEFAULT NULL, `album_id` INT(11) UNSIGNED DEFAULT NULL, `track_id` INT(11) UNSIGNED DEFAULT NULL, `position` INT(11) NOT NULL, PRIMARY KEY (`position_id`), KEY `KEY_GALLERY_ID` (`gallery_id`), KEY `KEY_ALBUM_ID` (`album_id`), KEY `KEY_TRACK_ID` (`track_id`) ) ENGINE=INNODB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; CREATE TABLE `media_gallery_music_track` ( `track_id` INT(11) UNSIGNED NOT NULL AUTO_INCREMENT, `album_id` INT(11) UNSIGNED DEFAULT NULL, `gallery_id` INT(11) UNSIGNED DEFAULT NULL, `name` VARCHAR(255) COLLATE utf8_unicode_ci NOT NULL, `duration` VARCHAR(255) COLLATE utf8_unicode_ci DEFAULT NULL, `artwork_url` VARCHAR(255) COLLATE utf8_unicode_ci DEFAULT NULL, `artist_name` VARCHAR(255) COLLATE utf8_unicode_ci DEFAULT NULL, `album_name` VARCHAR(255) COLLATE utf8_unicode_ci DEFAULT NULL, `price` VARCHAR(255) COLLATE utf8_unicode_ci DEFAULT NULL, `currency` VARCHAR(255) COLLATE utf8_unicode_ci DEFAULT NULL, `purchase_url` VARCHAR(255) COLLATE utf8_unicode_ci DEFAULT NULL, `stream_url` VARCHAR(255) COLLATE utf8_unicode_ci NOT NULL, `type` VARCHAR(255) COLLATE utf8_unicode_ci DEFAULT NULL, `position` INT(11) NOT NULL, PRIMARY KEY (`track_id`), KEY `KEY_ALBUM_ID` (`album_id`), KEY `KEY_GALLERY_ID` (`gallery_id`) ) ENGINE=INNODB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; ALTER TABLE `media_gallery_music_album` ADD FOREIGN KEY `FK_GALLERY_ID`(`gallery_id`) REFERENCES `media_gallery_music` (`gallery_id`) ON DELETE CASCADE ON UPDATE CASCADE; ALTER TABLE `media_gallery_music_elements` ADD FOREIGN KEY `FK_GALLERY_ID` (`gallery_id`) REFERENCES `media_gallery_music` (`gallery_id`) ON DELETE CASCADE ON UPDATE CASCADE, ADD FOREIGN KEY `FK_ALBUM_ID` (`album_id`) REFERENCES `media_gallery_music_album` (`album_id`) ON DELETE CASCADE ON UPDATE CASCADE, ADD FOREIGN KEY `FK_TRACK_ID` (`track_id`) REFERENCES `media_gallery_music_track` (`track_id`) ON DELETE CASCADE ON UPDATE CASCADE; ALTER TABLE `media_gallery_music_track` ADD FOREIGN KEY `FK_ALBUM_ID` (`album_id`) REFERENCES `media_gallery_music_album` (`album_id`) ON DELETE CASCADE ON UPDATE CASCADE, ADD FOREIGN KEY `FK_GALLERY_ID` (`gallery_id`) REFERENCES `media_gallery_music` (`gallery_id`) ON DELETE CASCADE ON UPDATE CASCADE; Work perfect MariaDb 5.5.52. Error MariaDb 10.1.22: Query : ALTER TABLE `media_gallery_music_elements` ADD FOREIGN KEY `FK_GALLERY_ID` (`gallery_id`) REFERENCES `media_gallery_musi... Error Code : 1005 Can't create table `test`.`#sql-c82_1086` (errno: 121 "Duplicate key on write or update") Execution Time : 00:00:00:000 Transfer Time : 00:00:00:000 Total Time : 00:00:00:000 I can manually modify and fix the error, but it is a system with many scripts and updates, is there any way to omit this error in Mariadb 10.1.22. Thks, -- *Wilmer.*

3 2

[Maria-discuss] sst failure?
by l vic 21 Mar '17

21 Mar '17

What can case the following problem? [Warning] WSREP: Failed to prepare for incremental state transfer: Local state UUID (00000000-0000-0000-0000-000000000000) does not match group state UUID (2cd97600-0e4e-11e7-997a-0a414b1bb17e): 1 (Operation not permitted) at galera/src/replicator_str.cpp:prepare_for_IST():482. IST will be unavailable. [Note] WSREP: Member 1.0 () requested state transfer from '*any*'.

1 0

Re: [Maria-discuss] Problem Upgrade MariaDb 5.5.52 MariaDb 10.1.22
by Wilmer Arambula 21 Mar '17

21 Mar '17

Thanks for your answer, I understand perfectly, but this is an old system, I understand the procedure of the update, but I thought there was some old_mode configuration only to run that database with the options of mariadb 5.5.52 in mariadb 10.1.22. Thks, Wilmer. 2017-03-21 16:19 GMT-04:00 Reindl Harald <h.reindl(a)thelounge.net>: > >> >> >> Am 21.03.2017 um 21:08 schrieb Wilmer Arambula: >> >>> Hi, ihave a system running perfectly on mariadb 5.5.52, i will change >>> everything to a new server with mariadb 10.1.22, but running the >>> installation script gives me problems, this is the error, is there any >>> way to configure mariadb 10.1.22 To omit this error, since mariadb >>> 10.1.22 works with strict-trans-table, there is some old_mode feature >>> that allows this. >>> >>> Query : ALTER TABLE `media_gallery_music_elements` ADD FOREIGN >>> KEY `FK_GALLERY_ID` (`gallery_id`) REFERENCES `media_gallery_musi... >>> >>> Error Code : 1005 >>> Can't create table `test`.`#sql-c82_1086` (errno: 121 "Duplicate key on >>> write or update") >>> >>> Execution Time : 00:00:00:000 >>> Transfer Time : 00:00:00:000 >>> Total Time : 00:00:00:000 >>> >>> I can manually modify and fix the error, but it is a system with many >>> scripts and updates, is there any way to omit this error in Mariadb >>> 10.1.22 >>> >> >> either you have unique keys or not >> >> however why not first upgrade to 10.0.x and why working with dumps >> instead just as others do for many many years an dbrought their server from >> mysql3 to mariadb 10.1 - this is not postgresql >> >> * upgrade 10.x >> * mysql_upgrade -u root -p >> * upgrade 10.1.x >> * mysql_upgrade -u root -p >> >> no, not on the live-server, on a virtual machine where you first rsync >> your datadir, play the upgrades and finally when you have a working plan >> after the last retry rsync the datadir to the new liveserver >> >> >> _______________________________________________ >> 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 >> > > >

1 0

[Maria-discuss] Missing MariaDB Seal logos?
by Colin Charles 20 Mar '17

20 Mar '17

Hi! Visiting: https://mariadb.com/kb/en/mariadb/branding-guidelines/ You’ll note that the Powered by MariaDB badges still exist (https://mariadb.org/about/logos/) — they should really say Powered by MariaDB Server But what is missing are all the seal logos? Currently beyond the archives at Wikimedia Commons (https://commons.wikimedia.org/wiki/File:Mariadb-seal-browntext.svg) they seem to have disappeared Is this just an oversight and something that needs fixing? Thanks -- Colin Charles, http://bytebot.net/blog/ twitter: @bytebot | skype: colincharles "First they ignore you, then they laugh at you, then they fight you, then you win." -- Mohandas Gandhi

2 1

[Maria-discuss] Questions to temporary myisam table files
by Hempel, Sebastian 20 Mar '17

20 Mar '17

Hallo, there is a known issue with the repair table function (MDEV-5871, MDEV-8475), which was fixed in MariaDB 10. Which is fine, but we have still MariaDB 5.5 server running. So we created our own repairtable function to work around this problem. For that function I like to know all possible file extensions for temporary myisam table files. For me temporary myisam table files are these files which are generated when calling "check table", "repair table" or other database functions. Thanks Sebastian

2 3

[Maria-discuss] Exclusive lock not working
by Jesse Schalken 20 Mar '17

20 Mar '17

I have a transaction that checks if a row exists with a particular value and if not, generates the data for that row and inserts it: -- schema CREATE TABLE test ( col INT, data TEXT, KEY (col) ); -- transaction START TRANSACTION; SELECT * FROM test WHERE col = 4 FOR UPDATE; -- If no results, generate data and insert INSERT INTO test SET col = 4, data = 'generated data goes here'; COMMIT; The problem I have is that if two copies of this transaction run concurrently (with the queries interleaved), they both pass the SELECT and deadlock on the INSERT. I would expect that the SELECT would acquire an exclusive lock on "col = 4" so only one transaction will proceed to insert, but the "FOR UPDATE" seems to behave as a shared lock instead. What is the correct way to write this transaction so only one copy proceeds to generate the "data" string and insert the row? (I originally posted this on Stack Overflow here <https://stackoverflow.com/questions/42547629/insert-row-if-not-exists-witho…> .) Thanks

2 2

[Maria-discuss] MariaDB 10.1.22 now available
by Daniel Bartholomew 19 Mar '17

19 Mar '17

The MariaDB project is pleased to announce the immediate availability of MariaDB 10.1.22. This is a stable (GA) release. See the Release Notes and Changelogs for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB 10.1.22 - Release Notes: https://mariadb.com/kb/en/mdb-10122-rn/ - Changelog: https://mariadb.com/kb/en/mdb-10122-cl/ - Downloads: https://downloads.mariadb.org/mariadb/10.1.22 About MariaDB 10.1: - https://mariadb.com/kb/en/what-is-mariadb-101/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ - - MariaDB Webinars - - - - - - - - - - - - - - - - - - - - - - - - - There are several upcoming MariaDB-focused webinars and many previously held ones available to watch on an on-demand basis at: - https://mariadb.com/news-events/webinars - - MariaDB Books - - - - - - - - - - - - - - - - - - - - - - - - - - There is an ever-growing library of MariaDB books available to help you get the most out of MariaDB. See the MariaDB Books page for details and links: - https://mariadb.com/kb/en/mariadb/books/ - - 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/donate/ We hope you enjoy MariaDB! -- MariaDB Website - http://mariadb.org Twitter - http://twitter.com/mariadbfdn - http://twitter.com/mariadb Google+ - http://google.com/+mariadb Facebook - http://fb.com/MariaDB.dbms Knowledge Base - http://mariadb.com/kb

3 11

[Maria-discuss] Fix different gtid-positions on domain 0 in multi-master
by Reinder Cuperus 17 Mar '17

17 Mar '17

Hello, After moving half of the databases on our primary master-master-cluster to a different cluster, we have a problem on our backup-server which is now a slave of both servers. Topology before: master1 <-> master2 -> backup-slave Topology during migrations: master1 <-> master2 -> backup-slave <-> master3 <-> master4 Final topology: master1 <-> master2 -> backup-slave <- master3 <-> master master4 The gtid_domain_ids before/during the migration were: master1/master2 : 0 master3/master4 : 20 Replication-settings: master2 -> backup: Replicate_Do_Domain_Ids: 0 master3 -> backup: Replicate_Do_Domain_Ids: 20 backup->master3: Replicate_Do_DB: DbToMigrate1,DbToMigrate2,etc Server version: 10.1.9 So after the migration, a typical gtid_position would be on: master1/2: 0-1-12345 master3/4: 0-1-12345,20-21-5678 As long as I keep the connection backup->master running (safe, because no new transactions on the migrated databases are occurring anymore on master1/2), the position on domain 0 gets recorded on master3. The problem is, as soon as I stop that connection, that master2 and master3 have different gtid-positions for domain0, and stop/start on replication master3->backup results in the error: "Got fatal error 1236 from master when reading data from binary log: 'Error: connecting slave requested to start from GTID 0-1-3898746614, which is not in the master's binlog' I have tried moving master1/2 to domain_id:1, and removing the domain_id:0 from the gtid_slave_pos on backup, but starting the replication master2->backup results in the error: Got fatal error 1236 from master when reading data from binary log: 'Could not find GTID state requested by slave in any binlog files. Probably the slave state is too old and required binlog files have been purged.' I have tried to find a way to insert an empty transaction, with the last gtid on domain_id:0 on the master3, to bring master2/master3 in sync again on that domain, but I could not find a way to do that on MariaDB. I tried finding a way to purge domain:0 from master3/master4, but the only way sofar I have found is doing a "RESET MASTER" on master3, which would break replication between master3 and master4. Are there other ways to fix this issue, so I can have reliable replication master3->backup without having to keep the dummy replication backup->master3 indefinitely? Regards, Reinder Cuperus

2 2

[Maria-discuss] Partition a Huge table
by Suresh Rajagopal 14 Mar '17

14 Mar '17

Hi, What is the fastest approach to partition a huge table with 2 additional columns? How safe its to alter table on slave and promote slave as master? It takes 25 hours to alter the table for now on slave. MariaDB Version : 10.1.18OS : Centos 6 ThanksSuresh

4 6

[Maria-discuss] [Warning] WSREP: Send action {(nil), 785, TORDERED} returned -103 (Software caused connection abort)
by Robbi Nespu 10 Mar '17

10 Mar '17

Hi there, I need to ask a guide from here. I have 5 galera cluster using mariadb 10.1 on centos 7 hosted on VPS for a few month. It running well until a weeks ago, during my leave, our VPS hosting rebooted our server. I create a backups and reboot the clusters1 till cluster2 (I don't enable auto start services on my box). Then on galera cluster 1, I ran command "galera_new_cluster" and start services on others clusters. cluster 2 - cluster 5 are working great. But it seems, cluster1 has problem. I checked services status and I got lot of this message : Mar 10 15:04:05 galera1 mysqld[6628]: 2017-03-10 15:04:05 139929087744768 [Warning] WSREP: Send action {(nil), 520, TORDERED} returned -103 (Software caused connection abort) Mar 10 15:04:05 galera1 mysqld[6628]: 2017-03-10 15:04:05 139929087744768 [Warning] WSREP: Send action {(nil), 520, TORDERED} returned -103 (Software caused connection abort) I tried to connect mariadb galera on cluster 1, seem the data are not synced unlike the others 4 cluster. Anyone face the same problem? Any guideline for me to troubleshoot this problem is most appreciated.

1 0

[Maria-discuss] Multiple Mariadb 10.1 instances on Centos 7
by Sales 09 Mar '17

09 Mar '17

I don’t see a mariadb@.service file on centos 7. I need to install multiple instances of mariadb 10.1 though and have them run from systemd (on the same server). The doc page https://mariadb.com/kb/en/mariadb/systemd/ <https://mariadb.com/kb/en/mariadb/systemd/> says that it’s installed on “some” systems. Apparently, some does not include Centos 7. So, is there a way to obtain a copy of the relevant file(s) needed to run multiple instances? Perhaps from another distribution? Seems like it’s a much better starting point than trying to create all that myself. Or, will it simply not work? What is the best way then to run multiple instances on Centos 7? Steve

2 3

[Maria-discuss] Maria db read/write configuration issues
by Chaitanya Cheekate 09 Mar '17

09 Mar '17

Hi We have configured maxscale in our environment using the links http://karlssonondatabases.blogspot.in/2014/02/maxscale-for-rest-of-us-part…, 2, 3 . We have two slaves and one master and the replication between them is working well. But after configuring read/write split the select queries are being executed in master itself, not routing to the slaves. Please find the attached documents of maxscale configuration, maxscale commands maxscale log and. Please help with maxscale read/write split. Attached documentsdetails 1. maxsconf.txt from the location /etc/maxscale.cnf 2. maxscale-commands.txt, coomands like maxadmin -pmariadb list servers, maxadmin -pmariadb list services, maxadmin -pmariadb show service "Splitter Service", 3. maxscale-log.txt from /var/log/maxscale Thanks Chaitu -- Thanks.

4 4

[Maria-discuss] slave_compressed_protocol = 1 has no effect
by Phil Sweeney 09 Mar '17

09 Mar '17

Hi there, I've been trying to make use of the compressed replication protocol between two existing MariaDB 10.1.21 boxes. Replication itself has been working fine for a while. I do: SET GLOBAL slave_compressed_protocol = 1; On both master and slave. Then stop/start slave. However, when I monitor the network usage, I see no reduction in network traffic. However, I tried compression via an ssh tunnel and saw a big reduction (ssh doing the compression, not MariaDB). So the traffic is definitely compressible. I tried setting the param via my.cnf and also restarting both master and slave to see if that would make a difference - no luck. Have confirmed the global variable shows 'ON' after the change, and was 'OFF' before. Is there potentially an issue with this working with the MariaDB supplied binary tarball (e.g. some compression lib dependency?) I see nothing in error.log to show an issue. Any other useful ways to debug this? Thanks! Phil

2 1

[Maria-discuss] MariaDB 10.0.30 now available
by Daniel Bartholomew 08 Mar '17

08 Mar '17

The MariaDB project is pleased to announce the immediate availability of MariaDB 10.0.30. This is a stable (GA) release. See the Release Notes and Changelog for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB 10.0.30 - Release Notes: https://mariadb.com/kb/en/mdb-10030-rn/ - Changelog: https://mariadb.com/kb/en/mdb-10030-cl/ - Downloads: https://downloads.mariadb.org/mariadb/10.0.30 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 - - - - - - - - - - - - - - - - - - - - - - - - - There are several upcoming MariaDB-focused webinars and many previously held ones available to watch on an on-demand basis at: - https://mariadb.com/news-events/webinars - - MariaDB Books - - - - - - - - - - - - - - - - - - - - - - - - - - There is an ever-growing library of MariaDB books available to help you get the most out of MariaDB. See the MariaDB Books page for details and links: - https://mariadb.com/kb/en/mariadb/books/ - - 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/donate/ We hope you enjoy MariaDB! -- MariaDB Website - http://mariadb.org Twitter - http://twitter.com/mariadbfdn - http://twitter.com/mariadb Google+ - http://google.com/+mariadb Facebook - http://fb.com/MariaDB.dbms Knowledge Base - http://mariadb.com/kb

4 5

[Maria-discuss] Change to innodb_large_prefix with respect to creating long indexes
by Marco Nicosia 07 Mar '17

07 Mar '17

Hi there, We noticed a change between MariaDB 10.1.18 and 10.1.20, but I haven't been able to find anything in the changelogs or JIRA that would help me understand what changed, and why. On 10.1.18, if I set `innodb_large_prefix=OFF` I can create indexes with lengths greater than 767 bytes and MariaDB only issues a warning. If I configure `innodb_large_prefix=ON` I get an error and the index fails to create. This seems like a bug? On 10.1.20, mysql fails to create the index regardless of how innodb_large_prefix is configured. We think that the result is that in 10.1.20, tables must be created or altered to use `ROW_FORMAT DYNAMIC` or `ROW_FORMAT COMPRESSED` if they are to contain an index with greater than 767 bytes in it. Is this the desired behavior? Was there a bug in 10.1.18 (and maybe previous)? I'm trying to understand the context better so that when devs ask us why index creation is failing, we give them the correct answer for why it used to work, and what they should be doing differently now that we're on 10.1.20. Thanks! -- Marco Nicosia Pivotal Software, Inc.

4 3

[Maria-discuss] Replication-manager + Maxscale
by Karthick Subramanian 02 Mar '17

02 Mar '17

Hi Experts, I have a 2 db server with one as master and another one as slave. Maxscale implemented with below monitor config: *[MySQL Monitor]* *type=monitor* *module=mysqlmon* *servers=master1,slave1* *monitor_interval=500* *script=/usr/bin/replication-manager --user root:password --rpluser replusr:password * *--hosts $INITIATOR,$NODELIST --failover=force --interactive=false* *events=master_down* When I shutdown master, failover is not automated. MRM (Replication Manager) is not promoting the slave to master automatically. In maxscale log, I noticed below: *2017-03-02 03:33:36 notice : Executed monitor script '/usr/bin/replication-manager --user root:password --rpluser replusr:password --hosts $INITIATOR,$NODELIST --failover=force --interactive=false' on event 'master_down'.* *2017-03-02 03:33:36 error : No Master can be determined.* Is this because I didn't have the quorum (no slave) since its one master and one slave set-up. Is there any workaround. Regards, Kart

3 4

[Maria-discuss] latin1 to utf8 conversion
by Suresh Rajagopal 25 Feb '17

25 Feb '17

Hi, I have a database(MariaDB 10.1.18) with latin1 characterset and a table with utf8 characterset.I can query the data only if i set names to latin1. How to convert the data to utf8 ? I have tried export/import,iconv. But still data doesn't show up. show create database test;+----------+----------------------------------------------------------------+| Database | Create Database |+----------+----------------------------------------------------------------+| test | CREATE DATABASE `test` /*!40100 DEFAULT CHARACTER SET latin1 */ |+----------+----------------------------------------------------------------+1 row in set (0.00 sec) CREATE TABLE `Test` ( `id` int(11) NOT NULL AUTO_INCREMENT, `name` varchar(255) COLLATE utf8_unicode_ci NOT NULL) ENGINE=InnoDB AUTO_INCREMENT=4312 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci | set names utf8;Query OK, 0 rows affected (0.00 sec) SELECT * FROM Test WHERE name = '2%Ss 60°C';Empty set (0.00 sec) set names latin1;Query OK, 0 rows affected (0.00 sec) SELECT name FROM Test WHERE name = '2%Ss 60°C';+------------+| name |+------------+| 2%Ss 60°C|| 2%Ss 60°C|+------------+2 rows in set (0.01 sec) ThanksSuresh

1 0

[Maria-discuss] Upgrading From MySQL 5.6 to MariaDB 10.1
by Michael Caplan 23 Feb '17

23 Feb '17

Hi there, I'm not seeing any concise information in the MariaDB docs about the recommended upgrade plan from MySQL 5.6 to MariaDB 10.1. Should I install MariaDB 10.0 and then 10.1? Or can I run right to 10.1? I'm running an older version of Ubuntu (12.04 Precise). Looking at the repo, it looks like I can stick with Precise, and hand that upgrade later. Or are there recommended min version of Ubuntu I should hit first? Thanks! Mike

5 9

[Maria-discuss] timestamp with time zone support mariaDB 10.1.14
by Karthick Subramanian 23 Feb '17

23 Feb '17

Hi Experts, I got this error, not sure whether maria db supports time zone: MariaDB [devdb]> create table ts (dt datetime, tz timestamp with time zone); ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'time zone)' at line 1 My application team is looking for time zone support. Any thought please. reference: https://mariadb.com/kb/en/sql-99/temporal-data-types/#time-with-time-zone

3 3

[Maria-discuss] MariaDB 10.2.4 RC now available
by Daniel Bartholomew 17 Feb '17

17 Feb '17

The MariaDB project is pleased to announce the immediate availability of MariaDB 10.2.4 Release Candidate (RC). See the Release Notes and Changelog for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB 10.2.4 - Release Notes: https://mariadb.com/kb/en/mdb-1024-rn/ - Changelog: https://mariadb.com/kb/en/mdb-1024-cl/ - Downloads: https://downloads.mariadb.org/mariadb/10.2.4 About MariaDB 10.2: - https://mariadb.com/kb/en/what-is-mariadb-102/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ - - MariaDB Webinars - - - - - - - - - - - - - - - - - - - - - - - - - There are several upcoming MariaDB-focused webinars and many previously held ones available to watch on an on-demand basis at: - https://mariadb.com/news-events/webinars - - MariaDB Books - - - - - - - - - - - - - - - - - - - - - - - - - - There is an ever-growing library of MariaDB books available to help you get the most out of MariaDB. See the MariaDB Books page for details and links: - https://mariadb.com/kb/en/mariadb/books/ - - 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/donate/ We hope you enjoy MariaDB! -- MariaDB Website - http://mariadb.org Twitter - http://twitter.com/mariadbfdn - http://twitter.com/mariadb Google+ - http://google.com/+mariadb Facebook - http://fb.com/MariaDB.dbms Knowledge Base - http://mariadb.com/kb

1 0

Re: [Maria-discuss] 10.1.x: Got packet bigger than 'max_allowed_packet' bytes
by Reindl Harald 17 Feb '17

17 Feb '17

Am 17.02.2017 um 18:26 schrieb Chris Calender: > Hello, > > On 2/17/2017 9:51 AM, Reindl Harald wrote: >> Am 16.02.2017 um 10:04 schrieb Peter Laursen: >>> The particular error message "Got packet bigger than >>> 'max_allowed_packet' bytes" is returned from the client and not the >>> server. >>> >>> Both the server and the client has a "max_allowed_packet" setting. The >>> client-one is listed >>> here https://dev.mysql.com/doc/refman/5.7/en/mysql-command-options.html >> >> well, tell that "mysql_upgrade" (part of mariadb) and "myqltuner" >> (mysqtuner pretends "[!!] Attempted to use login credentials, but they >> were invalid" when this is ste in the [client] section >> >> mysql_upgrade >> /usr/bin/mysql_upgrade: unknown variable 'max_allowed_packet=200M' > > I'm sure you're already aware of this, but for anyone else out there > following along that does not know, cases like this are exactly what the > --loose- prefix is for. That way one should be able to prefix such > variables with --loose-, under say the [client] section, and then client > programs that understand the variable should work, and those that do not > *should* not fail (though I cannot comment specifically on mysqltuner, > as I've not used it before). But that is the general premise of the > --loose-* prefix. no, i am not aware of this and to be honest have zero understanding when client software from the same build don't understand and or at least just ignores options it don't understand we can dicsuss about server better safe than sorry, but frankly i am not a big fan of things not doing anything because they don't understand a future or removed config param > For instance, if you set: > > [client] > loose-max_allowed_packet=200M > > Then mysql_upgrade will only throw a warning and continue on: > > shell> mysql_upgrade -uroot -ppass -P3366 > Warning: mysql_upgrade: unknown variable 'loose-max_allowed_packet=200M' > Phase 1/6: Checking and upgrading mysql database > Processing databases > ... > >> so currently "mysql" is the only client which a) understands it and b) >> proceeeds it correctly - what a mess > > Also, mysqldump does read and process max_allowed_packet correctly. So > for anyone out there reading this strictly in regards to > max_allowed_packet, don't forget mysqldump needs it too (which it would > read it from [client], [mysqldump], or the command line invocation itself)

1 0

[Maria-discuss] 10.1.x: Got packet bigger than 'max_allowed_packet' bytes
by Reindl Harald 17 Feb '17

17 Feb '17

/etc/my.cnf (for many years now) max_allowed_packet = 200M how can it be that when the whole table file is 54MB large with a setting of 200MB that something is larger then 200MB while obviously it was not too large at insert time at 2016-10-06 but with MariaDB 10.0.x instead 10.1.x? PHP says mysqli_fetch_assoc() [<a href='http://at.php.net/manual/de/function.mysqli-fetch-assoc.php'>function.mysqli-fetch-assoc.php</a>]: Malformed server packet. Field length pointing 22 bytes after end of packet MariaDB [afi]> select * from cms1_docmgmt_entrys where doc_id=19; ERROR 2020 (HY000): Got packet bigger than 'max_allowed_packet' bytes MariaDB [afi]> show variables like 'max_allowed_packet'; +--------------------+-----------+ | Variable_name | Value | +--------------------+-----------+ | max_allowed_packet | 209715200 | +--------------------+-----------+ 1 row in set (0,00 sec) MariaDB [afi]> select doc_file_download_size from cms1_docmgmt_entrys where doc_id=19; +------------------------+ | doc_file_download_size | +------------------------+ | 15838399 | +------------------------+ 1 row in set (0,00 sec) -rw-rw---- 1 mysql mysql 9,3K 2017-02-04 15:39 cms1_docmgmt_entrys.frm -rw-rw---- 1 mysql mysql 54M 2017-02-10 04:05 cms1_docmgmt_entrys.MYD -rw-rw---- 1 mysql mysql 234K 2017-02-10 04:05 cms1_docmgmt_entrys.MYI

3 5

[Maria-discuss] mysqldump 10.1.16
by Karthick Subramanian 16 Feb '17

16 Feb '17

All, I got a replciation problem and planned to take master server dump using below command and tried to restore in slave server: mysqldump --skip-lock-tables --single-transaction --flush-logs --hex-blob --master-data=1 -A --routines > ~/dump.sql I got into this error: https://jira.mariadb.org/browse/MDEV-10119 Then I tried this method: http://lists.askmonty.org/pipermail/commits/2016-June/009504.html My question: Is it ok if the GIS procedure currently with definer as definer=`root@localhost` instead of blank as definer=`` for the following two procs in mysql: Slave_MariaDB [(none)]> select db, name, definer from mysql.proc; +---------+------------------------+-----------------+ | db | name | definer | +---------+------------------------+-----------------+ | mysql | AddGeometryColumn | root@localhost | | mysql | DropGeometryColumn | root@localhost | Master_MariaDB [(none)]> select db, name, definer from mysql.proc; +---------+------------------------+-----------------+ | db | name | definer | +---------+------------------------+-----------------+ | mysql | AddGeometryColumn | @ | | mysql | DropGeometryColumn | @ |

2 2

[Maria-discuss] LOAD DATA LOCAL INFILE
by Karthick Subramanian 15 Feb '17

15 Feb '17

HI All, Even after enabling --local-infile=1 at mysql user login, I couldn't load the file locally. mysql -u root --local-infile=1 LOAD DATA LOCAL INFILE ERROR 1148 (42000): The used command is not allowed with this MariaDB version show variables like '%local%'; +---------------+-------+ | Variable_name | Value | +---------------+-------+ | local_infile | OFF | +---------------+-------+ Even though i enable --local-infile=1, the local-infile still shows OFF. Pleaselet know how can I fix this.

3 4

[Maria-discuss] ROLE and DEFAULT DATABASE
by Karthick Subramanian 09 Feb '17

09 Feb '17

Hi, Can anyone assist me on this below: I have a database called appdb. I need to grant access to this db to different users say: api_user, app_user, portal_user. So I created a ROLE as APP_ROLE and GRANT as below: GRANT SELECT, INSERT, UPDATE, DELETE ON APPDB.* TO APP_ROLE; Later I assign the Role to user: GRANT APP_ROLE TO API_USER@'%' IDENTIFIED BY 'YOU'; SET DEFAULT ROLE APP_ROLE TO API_USER@'%'; But the problem now is: Application team want to choose the database when they establish connection. But they couldn't use APPDB. So they couldn't see any db objects listed in APPDB. Is there a way we can assign a default database also for user.

3 2

[Maria-discuss] default_tmp_storage_engine=NULL
by Ian Gilfillan 09 Feb '17

09 Feb '17

What is the purpose/effect of having MariaDB's default_tmp_storage_engine setting default to NULL instead of the default used in MySQL, Innodb? I can't see any obvious differences in behaviour.

3 3

Re: [Maria-discuss] R: default_tmp_storage_engine=NULL
by Federico Razzoli 09 Feb '17

09 Feb '17

Well, I can't think many cases where InnoDB is not the default engine. But, if it is not, why should you use it for temporary tables? If you mainly use TokuDB, maybe don't want to mix the engines. If you use MyISAM, maybe you don't want transactional temporary tables. I still think that MEMORY makes sense in all cases :) Federico -------------------------------------------- Gio 9/2/17, Ian Gilfillan <ian(a)mariadb.org> ha scritto: Oggetto: Re: [Maria-discuss] R: default_tmp_storage_engine=NULL A: "Maria Discuss" <maria-discuss(a)lists.launchpad.net> Data: Giovedì 9 febbraio 2017, 10:32 > I beleive that there is a difference if default_storage_engine != innodb, because in that case, default_tmp_storage_engine will not be InnoDB. Yes, that's the case. So why is this desirable in MariaDB as opposed to MySQL's implementation? _______________________________________________ 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

1 0

[Maria-discuss] R: default_tmp_storage_engine=NULL
by Federico Razzoli 09 Feb '17

09 Feb '17

Hi Ian I beleive that there is a difference if default_storage_engine != innodb, because in that case, default_tmp_storage_engine will not be InnoDB. It is much less clear to me why default_tmp_storage_engine doesn't default to MEMORY in both MariaDB and MySQL :) Federico -------------------------------------------- Gio 9/2/17, Ian Gilfillan <ian(a)mariadb.org> ha scritto: Oggetto: [Maria-discuss] default_tmp_storage_engine=NULL A: "Maria Discuss" <maria-discuss(a)lists.launchpad.net> Data: Giovedì 9 febbraio 2017, 09:23 What is the purpose/effect of having MariaDB's default_tmp_storage_engine setting default to NULL instead of the default used in MySQL, Innodb? I can't see any obvious differences in behaviour. _______________________________________________ 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

2 1

[Maria-discuss] 2017 MariaDB Developers Conference
by Ian Gilfillan 07 Feb '17

07 Feb '17

The 2017 MariaDB Developers Conference is taking place in New York City from 9-10 April. It's free to attend for everyone interested and you are welcome to sign up on the Meetup Group, as well to propose a topic, or vote for an existing topic. Details at https://mariadb.org/2017-developers-meetup-new-york/ M|17, the MariaDB User's Conference, is taking place directly afterwards, so if you're in the area, why not attend both :) https://m17.mariadb.com/

1 1

[Maria-discuss] CentOS7 Cassandra
by Ian Gilfillan 01 Feb '17

01 Feb '17

Can someone clarify the status of Cassandra in CentOS7? It appears to have been available in 6, but not in 7.

5 5

[Maria-discuss] MariaDB Fedora update - testing
by Michal Schorm 30 Jan '17

30 Jan '17

Hello everybody, I made a (form my POV) bigger change to how MariaDB is packed, and I would be grateful for any feedback. I separated all the non-essential utilities to a standalone sub-package "server-utils". It should be installed automaticly with the "server" package as a weak dendency, so regular user should not spot any change. For example, if you don't need Perl with your server, you can save about 20MB of the space with this update. Rawhide: https://koji.fedoraproject.org/koji/taskinfo?taskID=17426872 F25: https://bodhi.fedoraproject.org/updates/FEDORA-2017-0f44f2b8c8 F24: https://bodhi.fedoraproject.org/updates/FEDORA-2017-801e01d1ed Thanks for any feedback in an advance! -- Michal Schorm Core Services - Databases Team mail: mschorm(a)redhat.com Brno-IRC: mschorm

2 3

[Maria-discuss] 10.1.21 - tests: main.analyze_format_json w4 [ fail ]
by Reindl Harald 26 Jan '17

26 Jan '17

main.analyze_format_json w4 [ fail ] Test ended at 2017-01-21 16:23:31 CURRENT_TEST: main.analyze_format_json --- /usr/share/mysql-test/r/analyze_format_json.result 2017-01-17 20:38:20.000000000 +0100 +++ /usr/share/mysql-test/r/analyze_format_json.reject 2017-01-21 16:23:31.740853974 +0100 @@ -455,7 +455,7 @@ "r_loops": 1, "rows": 10, "r_rows": 10, - "r_total_time_ms": "REPLACED", + "r_total_time_ms": "REPLACED"e-4, "filtered": 100, "r_filtered": 20, "attached_condition": "(tbl2.a in (2,3))" mysqltest: Result length mismatch

2 1

[Maria-discuss] question about generating logs on MariaDB 10.1.21
by Chris Adams 25 Jan '17

25 Jan '17

Hello, I have just moved from a MySQL 5.6 server on CentOS 6.8 to a MariaDB 10.1.21 server on CentOS 7. It is installed and working. I would like to set up some logging, but it has not gone as expected. I have binary logging working. However, I can't generate general logs or error logs. Here is part of the /etc/my.cnf file: user=mysql port = 3306 socket = /var/lib/mysql/mysql.sock datadir = /mnt/mysqldbs log_error = /var/log/mysql/error.log general_log_file = /var/log/mysql/mysql.log general_log = 1 log_bin = /mnt/mysqldbs/logs/mysql-bin I assume that after a restart, the logs will be generated, then logged to as events happen. As it is, no log files are generated. Many thanks.

4 7

[Maria-discuss] MariaDB 10.1.x: tablespace does not exist or is just being dropped
by Reindl Harald 23 Jan '17

23 Jan '17

Hi that crap temp files never deleted are from years ago and a crash until now it was enough to keep that tempfiles, with 10.1.x mariadb don't start at all - *how to get rid of that crap* the idiotic warnings are one thing but the segfauls now... it's about a decade that it's not possible to cleanup such stuff http://grokbase.com/t/mysql/mysql/136kx5qp1w/how-can-i-drop-a-table-that-is… 2017-01-23 22:01:27 139913013700928 [ERROR] InnoDB: Trying to do i/o to a tablespace which exists without .ibd data file. i/o type 10, space id 545, page no 0, i/o length 8192 bytes 2017-01-23 22:01:27 7f40097b2940 InnoDB: Error: trying to access tablespace 545 page no. 0, InnoDB: but the tablespace does not exist or is just being dropped. 2017-01-23 22:01:27 139913013700928 [ERROR] InnoDB: tablespace id is 545 in the data dictionary but in file ./dbmail/#sql2-704-271.ibd it is 690! 2017-01-23 22:01:31 140380157278528 [ERROR] InnoDB: Trying to do i/o to a tablespace which exists without .ibd data file. i/o type 10, space id 545, page no 0, i/o length 8192 bytes 2017-01-23 22:01:31 7faccd687940 InnoDB: Error: trying to access tablespace 545 page no. 0, InnoDB: but the tablespace does not exist or is just being dropped. InnoDB: Error: Unable to read tablespace 545 page no 0 into the buffer pool after 100 attempts InnoDB: The most probable cause of this error may be that the table has been corrupted. InnoDB: You can try to fix this problem by using innodb_force_recovery. InnoDB: Please see reference manual for more details. InnoDB: Aborting... 2017-01-23 22:01:31 7faccd687940 InnoDB: Assertion failure in thread 140380157278528 in file buf0buf.cc line 3080 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 170123 22:01:31 [ERROR] mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. To report this bug, see https://mariadb.com/kb/en/reporting-bugs We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. Server version: 10.1.21-MariaDB key_buffer_size=33554432 read_buffer_size=131072 max_used_connections=0 max_threads=52 thread_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 53739 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0x0 thread_stack 0x48400 /usr/libexec/mysqld(my_print_stacktrace+0x29)[0x560568d7a139] /usr/libexec/mysqld(handle_fatal_signal+0x3ad)[0x5605689d780d] /lib64/libpthread.so.0(+0x10c30)[0x7faccb39cc30] /lib64/libc.so.6(gsignal+0x35)[0x7faccaffe765] /lib64/libc.so.6(abort+0x16a)[0x7faccb00036a] /usr/libexec/mysqld(+0x80a9b9)[0x560568cce9b9] /usr/libexec/mysqld(+0x85426d)[0x560568d1826d] /usr/libexec/mysqld(+0x8593ca)[0x560568d1d3ca] /usr/libexec/mysqld(+0x8440b8)[0x560568d080b8] /usr/libexec/mysqld(+0x7b8978)[0x560568c7c978] /usr/libexec/mysqld(+0x702902)[0x560568bc6902] /usr/libexec/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x5d)[0x5605689d999d] /usr/libexec/mysqld(+0x3dddfb)[0x5605688a1dfb] /usr/libexec/mysqld(_Z11plugin_initPiPPci+0x782)[0x5605688a2c32] /usr/libexec/mysqld(+0x353e75)[0x560568817e75] /usr/libexec/mysqld(_Z11mysqld_mainiPPc+0x35f)[0x56056881c1ef] /lib64/libc.so.6(__libc_start_main+0xf1)[0x7faccafea731] /usr/libexec/mysqld(_start+0x29)[0x560568812eb9] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash.

1 3

[Maria-discuss] 10.1.21 - tests: main.analyze_stmt_orderby 'xtradb' w4 [ fail ]
by Reindl Harald 23 Jan '17

23 Jan '17

main.analyze_stmt_orderby 'xtradb' w4 [ fail ] Test ended at 2017-01-21 18:43:58 CURRENT_TEST: main.analyze_stmt_orderby --- /usr/share/mysql-test/r/analyze_stmt_orderby.result 2017-01-17 20:38:20.000000000 +0100 +++ /usr/share/mysql-test/r/analyze_stmt_orderby.reject 2017-01-21 18:43:58.130938437 +0100 @@ -417,7 +417,7 @@ "r_loops": 1, "rows": 10, "r_rows": 10, - "r_total_time_ms": "REPLACED", + "r_total_time_ms": "REPLACED"e-3, "filtered": 100, "r_filtered": 100 }, @@ -486,7 +486,7 @@ "r_loops": 1, "rows": 7, "r_rows": 7, - "r_total_time_ms": "REPLACED", + "r_total_time_ms": "REPLACED"e-4, "filtered": 100, "r_filtered": 100 }, mysqltest: Result length mismatch

2 2

[Maria-discuss] LTO build fails likely because -static-libgcc
by Reindl Harald 22 Jan '17

22 Jan '17

why does MariaDB use "-g -static-libgcc" in "mysql_release.cmake" and so besides override -g0 break -flto builds?

2 4

[Maria-discuss] 10.1.21 - tests: main.multi_update 'xtradb' w8 [ fail ]
by Reindl Harald 21 Jan '17

21 Jan '17

i guess that below makes not much sense when running with "--binlog-format=row" /mysql-test-run.pl --parallel=8 --max-test-fail=0 --mysqld=--binlog-format=row main.multi_update 'xtradb' w8 [ fail ] Test ended at 2017-01-21 18:43:50 CURRENT_TEST: main.multi_update --- /usr/share/mysql-test/r/multi_update.result 2017-01-17 20:38:20.000000000 +0100 +++ /usr/share/mysql-test/r/multi_update.reject 2017-01-21 18:43:49.979037948 +0100 @@ -1055,7 +1055,6 @@ Warnings: Warning 1264 Out of range value for column 'field1' at row 1 Warning 1264 Out of range value for column 'field1' at row 2 -Note 1592 Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave. UPDATE (SELECT 128 as col1) x, table_11757486 SET field1=x.col1; ERROR 22003: Out of range value for column 'field1' at row 1 UPDATE table_11757486 SET field1=128; @@ -1069,7 +1068,6 @@ Warnings: Warning 1264 Out of range value for column 'field1' at row 1 Warning 1264 Out of range value for column 'field1' at row 2 -Note 1592 Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave. DROP TABLE table_11757486; SET SESSION SQL_MODE=default; end of 10.0 tests mysqltest: Result length mismatch

1 0

[Maria-discuss] for years failing tests
by Reindl Harald 21 Jan '17

21 Jan '17

shouldn't the testsuite at some point in time run without errors? "run STOP SLAVE '' first" - uhm did i start it? it's scripted by shipped scripts [root@testserver:~]$ cat /usr/local/bin/mysql-test.sh #!/usr/bin/dash /usr/bin/su -c 'cd /usr/share/mysql-test; ./mysql-test-run.pl --parallel=1 --max-test-fail=0 --mysqld=--binlog-format=mixed --force' mysql rm -rf /usr/share/mysql-test/var/* rpl.rpl_binlog_index 'row' [ fail ] Test ended at 2017-01-20 16:56:16 CURRENT_TEST: rpl.rpl_binlog_index 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_binlog_index.test at line 20: At line 165: query 'SET GLOBAL gtid_slave_pos= ""' failed: 1198: This operation cannot be performed as you have 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_binlog_index-row/' to '/usr/share/mysql-test/var/log/rpl.rpl_binlog_index-row/' rpl.sec_behind_master-5114 'stmt' [ fail ] Test ended at 2017-01-20 16:58:33 CURRENT_TEST: rpl.sec_behind_master-5114 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/sec_behind_master-5114.test at line 1: At line 165: query 'SET GLOBAL gtid_slave_pos= ""' failed: 1198: This operation cannot be performed as you have a running slave ''; run STOP SLAVE '' first The result from queries just before the failure was: include/master-slave.inc rpl.rpl_semi_sync_event_after_sync 'mix,xtradb' [ fail ] Test ended at 2017-01-20 16:59:24 CURRENT_TEST: rpl.rpl_semi_sync_event_after_sync mysqltest: At line 1: query 'set global rpl_semi_sync_master_wait_point=AFTER_SYNC' failed: 1193: Unknown system variable 'rpl_semi_sync_master_wait_point' The result from queries just before the failure was: set global rpl_semi_sync_master_wait_point=AFTER_SYNC; - saving '/usr/share/mysql-test/var/log/rpl.rpl_semi_sync_event_after_sync-mix,xtradb/' to '/usr/share/mysql-test/var/log/rpl.rpl_semi_sync_event_after_sync-mix,xtradb/'

3 11

[Maria-discuss] 10.1.21 - tests: main.compound w5 [ fail ]
by Reindl Harald 21 Jan '17

21 Jan '17

main.compound w5 [ fail ] Test ended at 2017-01-21 16:21:47 CURRENT_TEST: main.compound --- /usr/share/mysql-test/r/compound.result 2017-01-17 20:38:20.000000000 +0100 +++ /usr/share/mysql-test/r/compound.reject 2017-01-21 16:21:47.413144793 +0100 @@ -28,13 +28,16 @@ include/show_binlog_events.inc Log_name Pos Event_type Server_id End_log_pos Info master-bin.000001 # Gtid # # BEGIN GTID #-#-# -master-bin.000001 # Query # # use `test`; INSERT INTO t1 VALUES (4) +master-bin.000001 # Table_map # # table_id: # (test.t1) +master-bin.000001 # Write_rows_v1 # # table_id: # flags: STMT_END_F master-bin.000001 # Query # # COMMIT master-bin.000001 # Gtid # # BEGIN GTID #-#-# -master-bin.000001 # Query # # use `test`; INSERT INTO t1 VALUES (5) +master-bin.000001 # Table_map # # table_id: # (test.t1) +master-bin.000001 # Write_rows_v1 # # table_id: # flags: STMT_END_F master-bin.000001 # Query # # COMMIT master-bin.000001 # Gtid # # BEGIN GTID #-#-# -master-bin.000001 # Query # # use `test`; INSERT INTO t1 VALUES (6) +master-bin.000001 # Table_map # # table_id: # (test.t1) +master-bin.000001 # Write_rows_v1 # # table_id: # flags: STMT_END_F master-bin.000001 # Query # # COMMIT DROP TABLE t1| CREATE DATABASE mysqltest1| @@ -144,12 +147,17 @@ execute stmt using @a, @b, @c| include/show_binlog_events.inc Log_name Pos Event_type Server_id End_log_pos Info -master-bin.000001 # Gtid # # GTID #-#-# -master-bin.000001 # Query # # use `test`; SELECT `test`.`fn`(9) -master-bin.000001 # Gtid # # GTID #-#-# -master-bin.000001 # Query # # use `test`; SELECT `test`.`fn`(1) master-bin.000001 # Gtid # # BEGIN GTID #-#-# -master-bin.000001 # Query # # use `test`; insert t1 values( NAME_CONST('a',4)+3) +master-bin.000001 # Table_map # # table_id: # (test.t1) +master-bin.000001 # Write_rows_v1 # # table_id: # flags: STMT_END_F +master-bin.000001 # Query # # COMMIT +master-bin.000001 # Gtid # # BEGIN GTID #-#-# +master-bin.000001 # Table_map # # table_id: # (test.t1) +master-bin.000001 # Write_rows_v1 # # table_id: # flags: STMT_END_F +master-bin.000001 # Query # # COMMIT +master-bin.000001 # Gtid # # BEGIN GTID #-#-# +master-bin.000001 # Table_map # # table_id: # (test.t1) +master-bin.000001 # Write_rows_v1 # # table_id: # flags: STMT_END_F master-bin.000001 # Query # # COMMIT drop function fn| drop table t1| mysqltest: Result length mismatch

1 0

[Maria-discuss] 10.1.21 - tests: main.commit_1innodb 'xtradb' w6 [ fail ]
by Reindl Harald 21 Jan '17

21 Jan '17

main.commit_1innodb 'xtradb' w6 [ fail ] Test ended at 2017-01-21 16:21:39 CURRENT_TEST: main.commit_1innodb --- /usr/share/mysql-test/r/commit_1innodb.result 2017-01-17 20:38:20.000000000 +0100 +++ /usr/share/mysql-test/r/commit_1innodb.reject 2017-01-21 16:21:39.268245094 +0100 @@ -710,12 +710,12 @@ # drop temporary table t2; call p_verify_status_increment(1, 0, 1, 0); -SUCCESS - +ERROR +Expected commit increment: 1 actual: 0 commit; call p_verify_status_increment(1, 0, 1, 0); -SUCCESS - +ERROR +Expected commit increment: 1 actual: 0 # 26. Verify that SET AUTOCOMMIT issues an implicit commit # insert t1 set a=3; @@ -831,8 +831,8 @@ Note 1050 Table 't2' already exists # Sic: first commits the statement, and then the transaction. call p_verify_status_increment(0, 0, 0, 0); -SUCCESS - +ERROR +Expected commit increment: 0 actual: 2 create table t3 select a from t2; call p_verify_status_increment(2, 0, 4, 4); SUCCESS mysqltest: Result length mismatch

1 0

[Maria-discuss] what about cleanly deprecation of config options
by Reindl Harald 20 Jan '17

20 Jan '17

what about spit some warnings in 10.0.x releases instead after update to 10.1.x service not starting and you can look what confdig options needs to be removed 2017-01-20 16:34:36 140555676232000 [ERROR] /usr/libexec/mysqld: unknown option '--skip-federated' 2017-01-20 16:34:36 140555676232000 [ERROR] Aborting

3 9

[Maria-discuss] -DWITH_INNODB_DISALLOW_WRITES=OFF and still generated files
by Reindl Harald 20 Jan '17

20 Jan '17

10.1.21 - first try build 10.1.x -DWITH_INNODB_DISALLOW_WRITES=OFF and the stuff below is still built - why? Fehler beim Bauen des RPM: Installierte (aber nicht gepackte) Datei(en) gefunden: /usr/bin/wsrep_sst_common /usr/bin/wsrep_sst_mysqldump /usr/bin/wsrep_sst_rsync /usr/bin/wsrep_sst_xtrabackup /usr/bin/wsrep_sst_xtrabackup-v2 /usr/share/mysql/wsrep.cnf /usr/share/mysql/wsrep_notify

2 2

[Maria-discuss] sanity check: mysql_upgrade MariaDB 5.5 straight to 10.1
by mike bayer 19 Jan '17

19 Jan '17

Hi all - I believe I know the answer to this question, however hoping someone can confirm all the assumptions (looks like there are three) are correct. Basically if one installs mariadb-10.1 on top of a data directory that's currently 5.5, and we run mysql_upgrade, is it as good/compatible/safe as if we had upgraded first to 10.0 in the interim? Per mariadb's documentation: https://mariadb.com/kb/en/mariadb/upgrading-from-mariadb-55-to-mariadb-100/ "There are no changes in table or index formats between MariaDB 5.5 and MariaDB 10.0" https://mariadb.com/kb/en/mariadb/upgrading-from-mariadb-100-to-101/, "There are no changes in table or index formats between MariaDB 10.0 and MariaDB 10.1" So assumption 1, transitively we can conclude there are no changes in table or index formats between 5.5 and 10.1. Next, mysql_upgrade seems like it alters some tables in the mysql database, and runs mysqlcheck --check-upgrade --auto-repair, which itself is mainly running CHECK TABLE. assumption 2 is then: the table changes in mysql_upgrade work against a 5.5 database going straight to 10.1. This would mean that if there were some tables/column changes in 5.5->10.0, and some more in 10.0->10.1, the mysql_upgrade command encapsulates both sets of changes as shipped in 10.1. It looks like this step comes from the .sql files in scripts/ by way of concatenating them into the "comp_sql" tool. Doing a diff of these scripts between 10.0.28 and 10.1.18 seems like only mysql_system_tables_fix.sql has the important bits (we don't use the performance schema stuff) and it looks like it only adds ALTER statements for more columns, the new columns from the 10.0 script are maintained. Not to mention it documents in a very open-ended way "This part converts any old privilege tables to privilege tables suitable for current version of MySQL". assumption 3 is, the Mariadb 10.1 engine running CHECK TABLE against a 5.5 database is fully compatible. The schema changes seem to be straightforward and as CHECK TABLE seems to regard the table and index formats which in assumption 1 have not changed, this should be totally fine as well. Note that I'm being kind of vague about what mysql_upgrade and mysqlcheck do, as I've only read the public documentation, browsed the source code a bit and am hoping this is all there is to it. There are a few blog posts on the web that illustrate a 5.5->10.1 direct upgrade, but these are not "official". Thanks for any guidance people can offer here!

1 0

[Maria-discuss] MariaDB 10.1.21 and other releases now available
by Daniel Bartholomew 18 Jan '17

18 Jan '17

The MariaDB project is pleased to announce the immediate availability of MariaDB 10.1.21, MariaDB 10.0.29, MariaDB Galera Cluster 10.0.29, MariaDB Connector/J 1.5.7, MariaDB Connector/C 2.3.2, and MariaDB Connector/C 3.0.1 Beta. Apart from Connector/C 3.0.1 Beta, these are all stable (GA) releases. See the Release Notes and Changelogs for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB 10.1.21 - Release Notes: https://mariadb.com/kb/en/mdb-10121-rn/ - Changelog: https://mariadb.com/kb/en/mdb-10121-cl/ - Downloads: https://downloads.mariadb.org/mariadb/10.1.21 About MariaDB 10.1: - https://mariadb.com/kb/en/what-is-mariadb-101/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ MariaDB 10.0.29 - Release Notes: https://mariadb.com/kb/en/mdb-10029-rn/ - Changelog: https://mariadb.com/kb/en/mdb-10029-cl/ - Downloads: https://downloads.mariadb.org/mariadb/10.0.29 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 Galera Cluster 10.0.29 - Release Notes: https://mariadb.com/kb/en/mgc-10029-rn/ - Changelog: https://mariadb.com/kb/en/mgc-10029-cl/ - Downloads: https://downloads.mariadb.org/mariadb-galera/10.0.29 About MariaDB Galera Cluster: - https://mariadb.com/kb/en/what-is-mariadb-galera-cluster/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ MariaDB Connector/J 1.5.7 - Release Notes: https://mariadb.com/kb/en/mcj-157-rn/ - Changelog: https://mariadb.com/kb/en/mcj-157-cl/ - Downloads: https://downloads.mariadb.org/connector-java/1.5.7/ About MariaDB Connector/J: - https://mariadb.com/kb/en/about-mariadb-connector-j/ MariaDB Connector/C 2.3.2 - Release Notes: https://mariadb.com/kb/en/mcc-232-rn/ - Changelog: https://mariadb.com/kb/en/mcc-232-cl/ - Downloads: https://downloads.mariadb.org/connector-c/2.3.2/ About MariaDB Connector/C: - https://mariadb.com/kb/en/about-mariadb-connector-c/ MariaDB Connector/C 3.0.1 Beta - Release Notes: https://mariadb.com/kb/en/mcc-301-rn/ - Changelog: https://mariadb.com/kb/en/mcc-301-cl/ - Downloads: https://downloads.mariadb.org/connector-c/3.0.1/ About MariaDB Connector/C: - https://mariadb.com/kb/en/about-mariadb-connector-c/ - - MariaDB Webinars - - - - - - - - - - - - - - - - - - - - - - - - - There are several upcoming MariaDB-focused webinars and many previously held ones available to watch on an on-demand basis at: - https://mariadb.com/news-events/webinars - - MariaDB Books - - - - - - - - - - - - - - - - - - - - - - - - - - There is an ever-growing library of MariaDB books available to help you get the most out of MariaDB. See the MariaDB Books page for details and links: - https://mariadb.com/kb/en/mariadb/books/ - - 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/donate/ We hope you enjoy MariaDB! -- MariaDB Website - http://mariadb.org Twitter - http://twitter.com/mariadbfdn - http://twitter.com/mariadb Google+ - http://google.com/+mariadb Facebook - http://fb.com/MariaDB.dbms Knowledge Base - http://mariadb.com/kb

1 0

[Maria-discuss] Handlersocket and stale data
by Sales 15 Jan '17

15 Jan '17

Is it still the case that Handlersocket may return stale data when the underlying structure is updated? Since there is still no memcached plugin in Mariadb, hoping stale data is not an issue. Steve

1 0

[Maria-discuss] ON update timestamp replication
by Artem Kuchin 14 Jan '17

14 Jan '17

Hello! Both master and slave run: Server version: 10.1.14-MariaDB FreeBSD Ports Replication is based on mixed format. Slave is used for backups without locking and going off line. I have a script that runs once a day and checksums all tables, so all tables are 100% in match (it wait for sync, locks and checksums). One table is very often out of sync. ON MASTER: show create table Message193; CREATE TABLE `Message193` ( `Message_ID` int(11) NOT NULL AUTO_INCREMENT, `User_ID` int(11) NOT NULL, `Subdivision_ID` int(11) NOT NULL, `Sub_Class_ID` int(11) NOT NULL, `Priority` int(11) NOT NULL DEFAULT '0', `Keyword` char(255) NOT NULL, `ncTitle` varchar(255) DEFAULT NULL, `ncKeywords` varchar(255) DEFAULT NULL, `ncDescription` text, `ncSMO_Title` varchar(255) DEFAULT NULL, `ncSMO_Description` text, `ncSMO_Image` char(255) DEFAULT NULL, `Checked` tinyint(4) NOT NULL DEFAULT '1', `IP` char(15) DEFAULT NULL, `UserAgent` char(255) DEFAULT NULL, `Parent_Message_ID` int(11) NOT NULL DEFAULT '0', `Created` datetime NOT NULL, `LastUpdated` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, `LastUser_ID` int(11) NOT NULL, `LastIP` char(15) DEFAULT NULL, `LastUserAgent` char(255) DEFAULT NULL, `Type` char(255) DEFAULT NULL, `Title` char(255) DEFAULT NULL, `Background` char(255) DEFAULT NULL, `Link` char(255) DEFAULT NULL, PRIMARY KEY (`Message_ID`), UNIQUE KEY `Sub_Class_ID` (`Sub_Class_ID`,`Message_ID`,`Keyword`), KEY `User_ID` (`User_ID`), KEY `LastUser_ID` (`LastUser_ID`), KEY `Subdivision_ID` (`Subdivision_ID`), KEY `Parent_Message_ID` (`Parent_Message_ID`), KEY `Priority` (`Priority`,`LastUpdated`), KEY `Checked` (`Checked`), KEY `Created` (`Created`) ) ENGINE=MyISAM AUTO_INCREMENT=5 DEFAULT CHARSET=utf8 | ON SLAVE CREATE TABLE `Message193` ( `Message_ID` int(11) NOT NULL AUTO_INCREMENT, `User_ID` int(11) NOT NULL, `Subdivision_ID` int(11) NOT NULL, `Sub_Class_ID` int(11) NOT NULL, `Priority` int(11) NOT NULL DEFAULT '0', `Keyword` char(255) NOT NULL, `ncTitle` varchar(255) DEFAULT NULL, `ncKeywords` varchar(255) DEFAULT NULL, `ncDescription` text, `ncSMO_Title` varchar(255) DEFAULT NULL, `ncSMO_Description` text, `ncSMO_Image` char(255) DEFAULT NULL, `Checked` tinyint(4) NOT NULL DEFAULT '1', `IP` char(15) DEFAULT NULL, `UserAgent` char(255) DEFAULT NULL, `Parent_Message_ID` int(11) NOT NULL DEFAULT '0', `Created` datetime NOT NULL, `LastUpdated` timestamp NOT NULL, `LastUser_ID` int(11) NOT NULL, `LastIP` char(15) DEFAULT NULL, `LastUserAgent` char(255) DEFAULT NULL, `Type` char(255) DEFAULT NULL, `Title` char(255) DEFAULT NULL, `Background` char(255) DEFAULT NULL, `Link` char(255) DEFAULT NULL, PRIMARY KEY (`Message_ID`), UNIQUE KEY `Sub_Class_ID` (`Sub_Class_ID`,`Message_ID`,`Keyword`), KEY `User_ID` (`User_ID`), KEY `LastUser_ID` (`LastUser_ID`), KEY `Subdivision_ID` (`Subdivision_ID`), KEY `Parent_Message_ID` (`Parent_Message_ID`), KEY `Priority` (`Priority`,`LastUpdated`), KEY `Checked` (`Checked`), KEY `Created` (`Created`) ) ENGINE=MyISAM AUTO_INCREMENT=5 DEFAULT CHARSET=utf8 | Notice that `LastUpdated` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, on slave becomes `LastUpdated` timestamp NOT NULL, This is already bad enough because if master is lost then slave will not be the same as master, trigger are not restored. Now check records: MASTER MariaDB [anapolisdom_ru]> select * from Message193 limit 1\G *************************** 1. row *************************** Created: 2016-11-25 13:25:09 LastUpdated: 2016-11-25 13:25:09 MariaDB [anapolisdom_ru]> select * from Message193 limit 1\G Created: 2016-11-25 13:25:09 LastUpdated: 0000-00-00 00:00:00 As you see lastupdated field is not replicated at all. Two questions, problems: 1) How to replicate default value and on update part for this field? 2) How to make it replicate the timestamp value? Artem

3 5

[Maria-discuss] Enabling Github integration with JIRA
by jocelyn fournier 13 Jan '17

13 Jan '17

Hi all, Currently there's no way when a JIRA ticket is closed to have a direct access to the associated commits in Github. GitHub integration with JIRA is available, and quite easy to configure, so it would be great to have it enabled on MariaDB Server. Do you think it's possible? Thanks! -- Jocelyn Fournier Founder M : +33 6 51 21 54 10 https://www.softizy.com Softizy - At your side to Optimize your PHP / MySQL applications

3 2

[Maria-discuss] Issue with MariaDB-server-5.5.54-1.el6.x86_64
by Clint Dilks 05 Jan '17

05 Jan '17

Hi, Today I have updated a CentOS 6.8 system that has MariaDB-server installed from http://yum.mariadb.org/5.5/centos6-amd64 and found that I had an SELinux issue when I tried to restart the service. Using the information at https://wiki.centos.org/HowTos/SELinux I have created a local policy that seems to fix things module marialocal 1.0; require { type mysqld_safe_t; class capability { setuid setgid }; } #============= mysqld_safe_t ============== allow mysqld_safe_t self:capability setgid; allow mysqld_safe_t self:capability setuid; This seems to fix things for me, but I thought I had better see if others are experiencing the same problem ? It may be useful to know that the particular rpms are MariaDB-server-5.5.54-1.el6.x86_64 and selinux-policy-3.7.19-292.el6_8.2.noarch. If it is a bigger issue than just myself, should I report this somewhere else to see if we can get a fix added to the next MariaDB-server rpm ? Thanks

2 2

[Maria-discuss] limiting memory use by mariadb?
by l vic 05 Jan '17

05 Jan '17

Is there some way to set hard limit for use of RAM by mariaDB server? Thanks, -V

4 16

[Maria-discuss] Fwd: Update of RPM layout
by Michal Schorm 05 Jan '17

05 Jan '17

Hello all, I went through an idea [1] to lighten the server package. I tested it, and I found out, I can save about 40MB of space, if I'd move all Perl utilites to a standalone subpackage. It would make sense to move them, so the users don't need to install Perl with the server package. Especially in technologies like containers (or cloud images) size matters. It all depends on how often are those utilities [2] used together with the server, sice we don't want to displace importatnt scripts. In case, it would look like a good idea, there is also option to move to this subpackage other - infrequently used - utilities. -> Q: Hey, Users and Admins, which utilities do you think are essential for the server? Note: It can be solved by soft dependencies, so those utils would be installed with the server by default. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1205082 [2] mysql_find_rows mysqlaccess mysql_convert_table_format mysql_fix_extensions mysql_setpermission mysql_zap mysqldumpslow mysqld_multi mysqlhotcopy -- Michal Schorm Core Services - Databases Team mail: mschorm(a)redhat.com Brno-IRC: mschorm

3 3

[Maria-discuss] nofile and nproc settings for mysql user in /etc/security/limits.conf
by Kaushal Shriyan 30 Dec '16

30 Dec '16

Hi, What should be the recommended nproc and nofile settings for mariadb or mysql user in /etc/security/limits.conf or /etc/my.cnf? I am running CentOS Linux version 6.8 Any help will be highly appreciable. Regards, Kaushal

2 1

[Maria-discuss] possible bug? #innodb-encryption-threads
by lejeczek 27 Dec '16

27 Dec '16

hi everyone I'm having a peculiar situation, a problem here with my config, which config is pretty galera-vanilla. Namely, if I set these: plugin-load-add = file_key_management.so file-key-management file-key-management-filename = /var/lib/mysql/.keys.txt innodb_file_per_table = 1 innodb-encrypt-log innodb-encryption-threads = 4 <= # this ! one here I get constant load on four cores, it would fluctuate just under %400 CPU (24*7). I'd assume that innodb-encryption-threads value causes it, and whatever the value might be it will be reflected in CPU usage. I wonder if you too see it. I my case I think it does something more to one system, it crashes the bloody thing to the extent where cold reboot is needed. MariaDB-client-10.1.19-1.el7.centos.x86_64 MariaDB-shared-10.1.19-1.el7.centos.x86_64 MariaDB-common-10.1.19-1.el7.centos.x86_64 MariaDB-server-10.1.19-1.el7.centos.x86_64 best, L

3 2

[Maria-discuss] error on show status query
by l vic 26 Dec '16

26 Dec '16

Have the following error trace from running SHOW STATUS LIKE 'wsrep_%' Any idea what could cause it? 2016-12-21 3:39:24 139668819036928 [Note] InnoDB: Online DDL : End of applying row log 2016-12-21 3:39:24 139668819036928 [Note] InnoDB: Online DDL : Completed 2016-12-21 3:43:29 139668818733824 [Note] InnoDB: Online DDL : Start 2016-12-21 3:43:29 139668818733824 [Note] InnoDB: Online DDL : Start reading clustered index of the table and create temporary files 2016-12-21 03:43:29 7f072e53ab00 InnoDB: Error: Write to file (merge) failed at offset 0. InnoDB: 1048576 bytes should have been written, only 901120 were written. InnoDB: Operating system error number 12. InnoDB: Check that your OS and file system support files of this size. InnoDB: Check also that the disk is not full or a disk quota exceeded. InnoDB: Error number 12 means 'Cannot allocate memory'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 2016-12-21 3:43:29 139668818733824 [Note] InnoDB: Online DDL : End of reading clustered index of the table and create temporary files java.sql.SQLNonTransientConnectionException: (conn:17945) Could not read resultset: unexpected end of stream, read 0 bytes from 4 Query is : SHOW STATUS LIKE 'wsrep_%' at org.mariadb.jdbc.internal.util.ExceptionMapper.get(ExceptionMapper.java:132) at org.mariadb.jdbc.internal.util.ExceptionMapper.getException(ExceptionMapper.java:101) at org.mariadb.jdbc.internal.util.ExceptionMapper.throwAndLogException(ExceptionMapper.java:77) at org.mariadb.jdbc.MariaDbStatement.executeQueryEpilog(MariaDbStatement.java:224) at org.mariadb.jdbc.MariaDbStatement.executeInternal(MariaDbStatement.java:258) at org.mariadb.jdbc.MariaDbStatement.executeQuery(MariaDbStatement.java:371) at com.verizon.mesos.Dbcheck.getStatus(Dbcheck.java:153) at com.verizon.mesos.Dbcheck.run(Dbcheck.java:103) at com.verizon.mesos.MariadbTask.handleHealthCheck(MariadbTask.java:310) at com.verizon.mesos.MariadbTask.executeCmd(MariadbTask.java:384) at com.verizon.mesos.MariadbTask.run(MariadbTask.java:450) at com.verizon.mesos.ExecutorTask.executeCmd(ExecutorTask.java:50) at com.verizon.mesos.ExecutorTask.run(ExecutorTask.java:115) at java.lang.Thread.run(Thread.java:745)

2 4

[Maria-discuss] MariaDB 10.2.3 and 5.5.54 now available
by Daniel Bartholomew 24 Dec '16

24 Dec '16

The MariaDB project is pleased to announce the immediate availability of MariaDB 10.2.3 beta and MariaDB 5.5.54 stable (GA). See the Release Notes and Changelogs for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB 10.2.3 - Release Notes: https://mariadb.com/kb/en/mdb-1023-rn/ - Changelog: https://mariadb.com/kb/en/mdb-1023-cl/ - Downloads: https://downloads.mariadb.org/mariadb/10.2.3 About MariaDB 10.2: - https://mariadb.com/kb/en/what-is-mariadb-102/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ MariaDB 5.5.54 - Release Notes: https://mariadb.com/kb/en/mdb-5554-rn/ - Changelog: https://mariadb.com/kb/en/mdb-5554-cl/ - Downloads: https://downloads.mariadb.org/mariadb/5.5.54 About MariaDB 5.5: - https://mariadb.com/kb/en/what-is-mariadb-55/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ - - MariaDB Webinars - - - - - - - - - - - - - - - - - - - - - - - - - There are several upcoming MariaDB-focused webinars and many previously held ones available to watch on an on-demand basis at: - https://mariadb.com/news-events/webinars - - MariaDB Books - - - - - - - - - - - - - - - - - - - - - - - - - - There is an ever-growing library of MariaDB books available to help you get the most out of MariaDB. See the MariaDB Books page for details and links: - https://mariadb.com/kb/en/mariadb/books/ - - 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/donate/ We hope you enjoy MariaDB! -- MariaDB Website - http://mariadb.org Twitter - http://twitter.com/mariadbfdn - http://twitter.com/mariadb Google+ - http://google.com/+mariadb Facebook - http://fb.com/MariaDB.dbms Knowledge Base - http://mariadb.com/kb

1 0

[Maria-discuss] aria engine error
by Roberto Spadim 22 Dec '16

22 Dec '16

hi guys i got a crash and aria engine don't startup, any help? 161222 03:41:13 mysqld_safe Starting mysqld daemon with databases from /home/mysql/data/local/ 2016-12-22 3:41:13 139878188566400 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release. 2016-12-22 3:41:13 139878188566400 [Note] /usr/mariadb/mariadb/bin//mysqld (mysqld 10.1.5-MariaDB-log) starting as process 19217 ... 2016-12-22 3:41:13 139878188566400 [Note] mysqld: Aria engine: starting recovery recovered pages: 0% 3082852397% 0%161222 3:41:13 [ERROR] mysqld got signal 11 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. To report this bug, see http://kb.askmonty.org/en/reporting-bugs We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. Server version: 10.1.5-MariaDB-log key_buffer_size=629145600 read_buffer_size=4194304 max_used_connections=0 max_threads=52 thread_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1041422 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0x0 thread_stack 0x48000 mysys/stacktrace.c:247(my_print_stacktrace)[0x7f37ee645b0b] sql/signal_handler.cc:153(handle_fatal_signal)[0x7f37ee1dfdb5] /lib64/libpthread.so.0(+0x10d00)[0x7f37ecd72d00] maria/ma_recovery.c:2142(exec_REDO_LOGREC_CLR_END)[0x7f37ee5683b7] maria/ma_recovery.c:588(display_and_apply_record)[0x7f37ee56985d] maria/ma_recovery.c:350(maria_apply_log)[0x7f37ee56d45c] maria/ma_recovery.c:242(maria_recovery_from_log)[0x7f37ee56df1e] maria/ha_maria.cc:3594(ha_maria_init)[0x7f37ee546c2d] sql/handler.cc:512(ha_initialize_handlerton(st_plugin_int*))[0x7f37ee1e2518] sql/sql_plugin.cc:1403(plugin_initialize)[0x7f37ee089e65] sql/sql_plugin.cc:1675(plugin_init(int*, char**, int))[0x7f37ee08add2] sql/mysqld.cc:5064(init_server_components)[0x7f37edfc37e8] sql/mysqld.cc:5659(mysqld_main(int, char**))[0x7f37edfc61ca] /lib64/libc.so.6(__libc_start_main+0xf0)[0x7f37ec3a79f0] /usr/mariadb/mariadb/bin//mysqld(+0x39dbad)[0x7f37edfbabad]

1 2

[Maria-discuss] restore problem with xtrabackup
by l vic 21 Dec '16

21 Dec '16

i have installed mariadb 1.10.13 cluster with user "root", password "pass" I have created test database "galeratest": CREATE DATABASE galeratest;USE galeratest;CREATE TABLE test_table ( id INT PRIMARY KEY AUTO_INCREMENT, msg TEXT ) ENGINE=InnoDB;INSERT INTO test_table (msg) VALUES ("Hello cluster."); backup: xtrabackup --user=root --password=pass --backup --target-dir=/media 161219 21:06:00 version_check Connecting to MySQL server with DSN 'dbi:mysql:;mysql_read_default_group=xtrabackup;port=3306;mysql_socket=/var/run/mysqld/mysqld.sock' as 'root' (using password: YES). 161219 21:06:00 version_check Connected to MySQL server 161219 21:06:00 version_check Executing a version check against the server... ... ok .. At this point i drop my database : DROP DATABASE galeratest; and trying to restore: xtrabackup --user=root --password=pass --prepare --target-dir=/media cd /media/ rsync -rvt --exclude 'xtrabackup_checkpoints' --exclude 'xtrabackup_logfile' \ ./ /var/lib/mysql chown -R mysql:mysql /var/lib/mysql/ MariaDB [galeratest]> show tables; +----------------------+ | Tables_in_galeratest | +----------------------+ | test_table | +----------------------+ 1 row in set (0.00 sec) MariaDB [galeratest]> select * from test_table; *ERROR 1932 (42S02): Table 'galeratest.test_table' doesn't exist in engine* *Any idea what the problem is? * Thanks,

2 2

[Maria-discuss] MariaDB 10.1.20 now available
by Daniel Bartholomew 15 Dec '16

15 Dec '16

The MariaDB project is pleased to announce the immediate availability of MariaDB 10.1.20. This is a stable (GA) release. See the Release Notes and Changelog for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB 10.1.20 - Release Notes: https://mariadb.com/kb/en/mdb-10120-rn/ - Changelog: https://mariadb.com/kb/en/mdb-10120-cl/ - Downloads: https://downloads.mariadb.org/mariadb/10.1.20 About MariaDB 10.1: - https://mariadb.com/kb/en/what-is-mariadb-101/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ - - MariaDB Webinars - - - - - - - - - - - - - - - - - - - - - - - - - There are several upcoming MariaDB-focused webinars and many previously held ones available to watch on an on-demand basis at: - https://mariadb.com/news-events/webinars - - MariaDB Books - - - - - - - - - - - - - - - - - - - - - - - - - - There is an ever-growing library of MariaDB books available to help you get the most out of MariaDB. See the MariaDB Books page for details and links: - https://mariadb.com/kb/en/mariadb/books/ - - 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/donate/ We hope you enjoy MariaDB! -- MariaDB Website - http://mariadb.org Twitter - http://twitter.com/mariadbfdn - http://twitter.com/mariadb Google+ - http://google.com/+mariadb Facebook - http://fb.com/MariaDB.dbms Knowledge Base - http://mariadb.com/kb

1 0

Re: [Maria-discuss] Semaphore hangs
by Jon Foster 15 Dec '16

15 Dec '16

On 12/08/2016 04:16 PM, Jon Foster wrote: > On 12/08/2016 03:13 PM, Daniel Black wrote: >> On 09/12/16 09:43, Jon Foster wrote: >>> On 12/07/2016 06:04 PM, Daniel Black wrote: >>>> On 08/12/16 08:51, Jon Foster wrote: >>>>> We are having trouble with MariaDB hanging due to a "semaphore wait". We >>>>> then have to shut MariaDB down as it typically won't recover, unless it >>>>> restarts itself, which happens if we wait long enough. But if its gone >>>>> on long enough MariaDB won't even shutdown, it hangs indefinitely >>>>> waiting for some other internal service. I don't remember the exact name >>>>> and we've been fast enough I haven't seen it in a while. >>>>> >>>>> We've had the database on two completely different servers and still see >>>>> the problem. Both servers were bought new for this project and are a >>>>> year or less old. They are running all SSD drives, Debian 7 64bit with >>>>> MariaDB 10.1 from the MariaDB APT repository. >>>>> >>>>> Since the XtraDB engine was usually mentioned in the logged messages we >>>>> switched back to the Oracle InnoDB engine. Although this seems to have >>>>> reduced the frequency it didn't fix it. >>>>> >>>>> Can anyone give some advice on fixing this. It really seams like a bug >>>>> in MariaDB. I'll try to provide any needed info. >> [...] So its happened again on Tuesday (12/13) morning, early enough the east coasters got it before I was aware of it (they are 3hrs ahead and I was just getting up). Unfortunately I wasn't able to try the "gdb" request from the previous discussion on this topic. So I've been looking for ways to cross reference all the thread and mutexes mentioned to try and pinpoint where the failure is happening. This crash produced over 430MB of log data. I sliced out the first InnoDB monitor dump (a mere 1.5MB) and stripped it down to just the threads and related messages. I'm still reviewing the logs but I found something I thought was interesting enough I'd throw it out here and see if anyone had any thoughts. There were 4,894 threads listed in the dump. But it appears that everyone was waiting for one thread. Here is what the log said about that one thread: 06:01:42 --Thread 139879467059968 has waited at trx0sys.ic line 431 for 0.00 seconds the semaphore: 06:01:42 Mutex at 0x7f3a09a92068 created file trx0sys.cc line 729, lock var 0 06:01:42 Last time reserved by thread 18446744073709551615 in file not yet reserved line 0, waiters flag 0 I trimmed out the data and server name to shorten the lines. Several interesting things to note: 1. Thread 18446744073709551615 doesn't exist in the InnoDB monitor dump. 2. All of the other thread IDs are 15 digits. This one is 20 digits. 3. Over a thousand other threads are waiting on this one because it apparently has the lock_sys->mutex mutex. All of the remaining threads are waiting on those others. 4. This thread shows a 0 second wait time when many of the other threads say they've been waiting over 250 seconds. Sure looks like the mutex is being held by a non-existent thread. Memory corruption? I'm still looking over the logs so I might find some other stuff or something else to point the finger at. But I thought I'd throw this out there and see if anyone has some insight. Or maybe I should be taking this issue to another list or report it as a bug? THX - Jon -- Sent from my Debian Linux workstation -- http://www.debian.org/intro/about Jon Foster JF Possibilities, Inc. jon(a)jfpossibilities.com 541-410-2760 Making computers work for you!

1 0

Re: [Maria-discuss] Semaphore hangs
by Daniel Black 08 Dec '16

08 Dec '16

On 09/12/16 09:43, Jon Foster wrote: > On 12/07/2016 06:04 PM, Daniel Black wrote: >> On 08/12/16 08:51, Jon Foster wrote: >>> We are having trouble with MariaDB hanging due to a "semaphore wait". We >>> then have to shut MariaDB down as it typically won't recover, unless it >>> restarts itself, which happens if we wait long enough. But if its gone >>> on long enough MariaDB won't even shutdown, it hangs indefinitely >>> waiting for some other internal service. I don't remember the exact name >>> and we've been fast enough I haven't seen it in a while. >>> >>> We've had the database on two completely different servers and still see >>> the problem. Both servers were bought new for this project and are a >>> year or less old. They are running all SSD drives, Debian 7 64bit with >>> MariaDB 10.1 from the MariaDB APT repository. >>> >>> Since the XtraDB engine was usually mentioned in the logged messages we >>> switched back to the Oracle InnoDB engine. Although this seems to have >>> reduced the frequency it didn't fix it. >>> >>> Can anyone give some advice on fixing this. It really seams like a bug >>> in MariaDB. I'll try to provide any needed info. Its either a bug or you are running without sufficient hardware. If you rule out the later I suggest opening a report at jira.mariadb.org >>> TIA - Jon >>> >> Needed info: >> * exact MariaDB version 10.1.X >> * mariadb configuration >> * what is the entire mysql log from the startup until the "semaphore >> wait" >> * how are you determining "semaphore wait" >> * is a SHOW FULL PROCESS LIST possible? if so contents? >> * when in a stalled state run on a commmand line (with gdb installed) >> gdb --batch --eval-command="thread apply all bt" program $(pidof mysqld) >> > Version: 10.10.19+maria-1~wheezy, but we started having problems with > 5.5.x which after a few updates prompted us to try 10.1. > > Configuration: > ----------------------- > [mysqld_safe] > socket = /var/run/mysqld/mysqld.sock > nice = -10 Niceing below 0 isn't that productive. -10 might be interfering with kernel IO processes that are needed to enable userspace threads to resume. No high IO/CPU/RAM should be running on the same host however if you do -1 or -2 might help achieve a higher priority than the other process. > [mysqld] > user = mysql > pid-file = /var/run/mysqld/mysqld.pid > socket = /var/run/mysqld/mysqld.sock > port = 3306 > basedir = /usr > datadir = /ssd/mysql > tmpdir = /ssd/tmp > lc_messages_dir = /usr/share/mysql > lc_messages = en_US > skip-external-locking > # NOTE: these two were recently added to troubleshoot > ignore_builtin_innodb > plugin_load=innodb=ha_innodb.so > bind-address = 127.0.0.1 > skip-name-resolve > max_connections = 8000 At the time of the crash you seem to have about 4k threads zgrep 12:35:18 /tmp/mozilla_dan0/mysql-crash-20161207.log.gz | grep ' --Thread' | cut -f 8 -d ' ' | sort -u | wc -l 4158 I suspect you don't have enough grunt in hardware to support this. I do suspect that this level is significantly above standard load. I'd restrict max_connections to something you have seen your hardware handle. > connect_timeout = 5 > wait_timeout = 60 > max_allowed_packet = 1M > thread_cache_size = 100 > sort_buffer_size = 1M > bulk_insert_buffer_size = 16M > tmp_table_size = 32M > max_heap_table_size = 10M > join_buffer_size = 1M > myisam_recover = BACKUP > key_buffer_size = 128M > open-files-limit = 65535 > table_open_cache = 15000 > myisam_sort_buffer_size = 128M > concurrent_insert = 2 > read_buffer_size = 256K > read_rnd_buffer_size = 256K > query_cache_limit = 1M > query_cache_size = 16M > slow_query_log=0 > slow_query_log_file = /var/log/mysql/mariadb-slow.log > long_query_time = 3 > log_slow_verbosity = query_plan > binlog_format = ROW > expire_logs_days = 10 > max_binlog_size = 100M > default_storage_engine = InnoDB > innodb_buffer_pool_size = 2600M > innodb_log_buffer_size = 256M > innodb_file_per_table = 1 > innodb_open_files = 400 > innodb_io_capacity = 400 > innodb_adaptive_hash_index = 0 > # These two were added just prior to this last crash. > innodb_buffer_pool_dump_at_shutdown = 1 > innodb_buffer_pool_load_at_startup = 1 > innodb_flush_log_at_trx_commit = 0 Setting ^ to 0 will mean less IO however it means that you can loose stuff on your expected crash. > innodb_support_xa = 0 > sync_binlog = 0 > ----------------------- > > Logs: This most recent case is about 19M uncompressed. I have hosted it > on my website here: > http://www.jfpossibilities.com/static/pickup/mysql-crash-20161207.log.gz > If you would like it delivered some other way let me know. I have about > 300M of logs from a previous crash situation. That time was particularly > bad since for some reason it would hang again within ten minutes of > being restarted. By limiting the connections on our webservers I was > able to baby it to get it going again. > > I determined "semaphore wait" from the zillions of messages in the logs > that say it. We shut down this one pretty quick. But I usually recognize > the symptoms fairly early on: the number of DB connections escalates > from ~1k up to the max 8k. The number of running queries as shown with > "show processlist" escalates along with it going from less than 10 to > hundreds or thousands depending on how long we wait. sounds like max_connections of 100 might be more suitable. Matches thread_cache_size. > Then too the Apache > connections on the web servers escalate. And of course the "load factor" > on all the servers jumps up. Icinga usually gives us the heads up. Is apache on the same machine? If so you configured Apache so that it doesn't consume more memory and leave MySQL with no headroom. Of course its better to have it on a different host. Make sure Icinga doesn't show swapping. Check your read and write latency on the SSD. > Obviously your last two requests will have to wait until we are having a > problem again. But I have gdb installed and ready to go... I think. I > don't know much about it. SHOW ENGINE INNODB STATUS would be good too. experiment with gdb on a test machine in the same way. Even if its a different process.

1 0

[Maria-discuss] HDF5 and storage engine
by Roberto Spadim 08 Dec '16

08 Dec '16

Hi guys, does anyone know if mariadb/mysql have a storage engine with read access to HDF5 file format? https://support.hdfgroup.org/HDF5/ thanks -- Roberto Spadim SPAEmpresarial - Software ERP Eng. Automação e Controle

2 1

[Maria-discuss] Semaphore hangs
by Jon Foster 08 Dec '16

08 Dec '16

We are having trouble with MariaDB hanging due to a "semaphore wait". We then have to shut MariaDB down as it typically won't recover, unless it restarts itself, which happens if we wait long enough. But if its gone on long enough MariaDB won't even shutdown, it hangs indefinitely waiting for some other internal service. I don't remember the exact name and we've been fast enough I haven't seen it in a while. We've had the database on two completely different servers and still see the problem. Both servers were bought new for this project and are a year or less old. They are running all SSD drives, Debian 7 64bit with MariaDB 10.1 from the MariaDB APT repository. Since the XtraDB engine was usually mentioned in the logged messages we switched back to the Oracle InnoDB engine. Although this seems to have reduced the frequency it didn't fix it. Can anyone give some advice on fixing this. It really seams like a bug in MariaDB. I'll try to provide any needed info. TIA - Jon -- Jon Foster jon(a)jfpossibilities.com

2 1

[Maria-discuss] dead server joins the cluster?
by l vic 05 Dec '16

05 Dec '16

Hello, I see the problem with one of the secondary nodes successfully joining the cluster: the cluster_size=3 and it stays this way but database server in container is dead, e.g. nothing listening on the port 3306 Is there possible scenario for the node with failed database server to join the cluster? Thanks,

1 0

[Maria-discuss] New MariaDB releases and EOL distros
by Ian Gilfillan 01 Dec '16

01 Dec '16

Hi From what I understand, 10.2 is currently not being built on Ubuntu 12.04, as after 10.2.2 it required lots of effort to get it working on the platform, too much for a distro about to reach end of life. Currently, it's still built on Centos5, but I understand that this also isn't ideal. The current deprecation dates are listed at: https://mariadb.com/kb/en/mariadb/deprecation-policy/ What about simplifying these decisions with a guideline, such as that major new releases will not be built on distros that reach end-of-life within, say, 6 months of the expected stable release date. So if a new release is expected to be stable in December (understandably always an estimate), we won't bother to build it on distros that EOL before June. Currently, that would mean not building 10.2 on CentOS 5, which I think would be welcomed.

1 0

[Maria-discuss] rejoin timeout
by l vic 01 Dec '16

01 Dec '16

How long can it take for a node to sync during a rejoin? Is there system variable setting that limit? Thanks, -V

1 0

[Maria-discuss] rejoin timeout?
by l vic 30 Nov '16

30 Nov '16

How long can it take for a node to sync during a rejoin? Is there environmental variable for that? Thanks, -V

1 0

Re: [Maria-discuss] Aborted connection (CLOSE_CONNECTION)
by Federico Razzoli 30 Nov '16

30 Nov '16

Woops, sorry, I missed the GLOBAL word :) Federico -------------------------------------------- Mer 30/11/16, Ian Gilfillan <ian(a)mariadb.org> ha scritto: Oggetto: Re: [Maria-discuss] Aborted connection (CLOSE_CONNECTION) A: maria-discuss(a)lists.launchpad.net Data: Mercoledì 30 novembre 2016, 15:13 On 30/11/2016 15:13, Federico Razzoli wrote: > This always shows the global value: > SHOW VARIABLES LIKE ... > > This always shows the current session value: > SHOW SESSION VARIABLES LIKE ... This is not correct. SHOW VARIABLES shows the session value: SET GLOBAL wait_timeout=601; SET SESSION wait_timeout=599; SHOW SESSION VARIABLES LIKE 'wait_%'; +---------------+-------+ | Variable_name | Value | +---------------+-------+ | wait_timeout | 599 | +---------------+-------+ SHOW GLOBAL VARIABLES LIKE 'wait_%'; +---------------+-------+ | Variable_name | Value | +---------------+-------+ | wait_timeout | 601 | +---------------+-------+ SHOW VARIABLES LIKE 'wait_%'; +---------------+-------+ | Variable_name | Value | +---------------+-------+ | wait_timeout | 599 | +---------------+-------+ _______________________________________________ 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

1 0

Re: [Maria-discuss] Aborted connection (CLOSE_CONNECTION)
by Federico Razzoli 30 Nov '16

30 Nov '16

This always shows the global value: SHOW VARIABLES LIKE ... This always shows the current session value: SHOW SESSION VARIABLES LIKE ... Global value is read from the files when the server starts, and later can be changed with SET GLOBAL var = val. Session value is copied from global value when the session starts (so changing the global value doesn't affect existing sessions) and can later be changed with SET var = val. In other words, the global value is important because it is used by all new sessions by default, but the session value is what really takes effect. I beleive that your application sets a session value. Federico -------------------------------------------- Mer 30/11/16, Florent B <florent(a)coppint.com> ha scritto: Oggetto: Re: [Maria-discuss] Aborted connection (CLOSE_CONNECTION) A: "Federico Razzoli" <federico_raz(a)yahoo.it>, maria-discuss(a)lists.launchpad.net Data: Mercoledì 30 novembre 2016, 10:44 Ok, I found the problem thanks to you Federico. On Debian, mysql-common package provided by MariaDB repository contains "wait_timeout = 600" in my.cnf. This is not the default value specified in documentation (28800). And when I use "mysql -u root -p -h my_host" command to show variables, the default value is displayed (28800), I never saw 600 in here ! Why ? But displaying variables in my PHP app showed me that wait_timeout was effectively set to 600. Setting wait_timeout=28800 in a config file in /etc/mysql/conf.d directory fixes this. Should we consider "wait_timeout = 600" in my.cnf as a bug ? That's not default value... On 11/29/2016 11:17 PM, Federico Razzoli wrote: > Interesting. A couple ideas: > > 1 > Try this query: > SHOW SESSION VARIABLES LIKE '%timeout%'; > But this time, this should be executed by PHP, using the same library used by the application. Why? To check if a library changes a timeout at session level. > > 2 > Have you checked if your application reconnects N times? For example, 600 could be a 60 seconds timeout * 10 attempts. > > Federico > > > -------------------------------------------- > Mar 29/11/16, Florent B <florent(a)coppint.com> ha scritto: > > Oggetto: Re: [Maria-discuss] Aborted connection (CLOSE_CONNECTION) > A: "Reindl Harald" <h.reindl(a)thelounge.net>, maria-discuss(a)lists.launchpad.net > Data: Martedì 29 novembre 2016, 12:22 > > On 11/29/2016 12:03 PM, > Reindl Harald wrote: > > > > > > Am 29.11.2016 um > 11:49 schrieb Florent B: > >> For > example, if I try this in PHP: > >> > >> 1/ Connect to mariadb > >> > >> 2/ sleep 610 > seconds > >> > >> 3/ > ping mariadb > >> > >> => I got Server has gone away > error. > >> > >> > With a 590 sleep time, no error. > >> > >> I use MariaDB 10.1, didn't change > any "timeout" value in MariaDB : > >> interactive_timeout & wait_timeout > are 28800 > > > > http://php.net/manual/en/mysqlnd.config.php#ini.mysqlnd.net-read-timeout > > > > Hi, and > thank you. But I cannot find any timeout of 600 > seconds... > default_socket_timeout = 60 > mysqlnd.net_read_timeout = 31536000 > > And I have the exactly same > problem using this algorithm in Python, it's > not related to PHP... > > _______________________________________________ > 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 > > > _______________________________________________ > 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

2 1

Re: [Maria-discuss] Aborted connection (CLOSE_CONNECTION)
by Federico Razzoli 29 Nov '16

29 Nov '16

Interesting. A couple ideas: 1 Try this query: SHOW SESSION VARIABLES LIKE '%timeout%'; But this time, this should be executed by PHP, using the same library used by the application. Why? To check if a library changes a timeout at session level. 2 Have you checked if your application reconnects N times? For example, 600 could be a 60 seconds timeout * 10 attempts. Federico -------------------------------------------- Mar 29/11/16, Florent B <florent(a)coppint.com> ha scritto: Oggetto: Re: [Maria-discuss] Aborted connection (CLOSE_CONNECTION) A: "Reindl Harald" <h.reindl(a)thelounge.net>, maria-discuss(a)lists.launchpad.net Data: Martedì 29 novembre 2016, 12:22 On 11/29/2016 12:03 PM, Reindl Harald wrote: > > > Am 29.11.2016 um 11:49 schrieb Florent B: >> For example, if I try this in PHP: >> >> 1/ Connect to mariadb >> >> 2/ sleep 610 seconds >> >> 3/ ping mariadb >> >> => I got Server has gone away error. >> >> With a 590 sleep time, no error. >> >> I use MariaDB 10.1, didn't change any "timeout" value in MariaDB : >> interactive_timeout & wait_timeout are 28800 > > http://php.net/manual/en/mysqlnd.config.php#ini.mysqlnd.net-read-timeout > Hi, and thank you. But I cannot find any timeout of 600 seconds... default_socket_timeout = 60 mysqlnd.net_read_timeout = 31536000 And I have the exactly same problem using this algorithm in Python, it's not related to PHP... _______________________________________________ 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

1 0

Re: [Maria-discuss] Aborted connection (CLOSE_CONNECTION)
by Reindl Harald 29 Nov '16

29 Nov '16

Am 29.11.2016 um 12:22 schrieb Florent B: > On 11/29/2016 12:03 PM, Reindl Harald wrote: >> Am 29.11.2016 um 11:49 schrieb Florent B: >>> For example, if I try this in PHP: >>> >>> 1/ Connect to mariadb >>> 2/ sleep 610 seconds >>> 3/ ping mariadb >>> => I got Server has gone away error. >>> With a 590 sleep time, no error. >>> I use MariaDB 10.1, didn't change any "timeout" value in MariaDB : >>> interactive_timeout & wait_timeout are 28800 >> >> http://php.net/manual/en/mysqlnd.config.php#ini.mysqlnd.net-read-timeout > > Hi, and thank you. But I cannot find any timeout of 600 seconds... > default_socket_timeout = 60 > mysqlnd.net_read_timeout = 31536000 > > And I have the exactly same problem using this algorithm in Python, it's > not related to PHP... then pretty sure you mysqld timeouts are not what you think, otherwise we would see the same issues on our dbmail machines when after hours of idle postfix tries to re-use it's connections (and we did have such events when that values where too low) so why don't you ask the server instead pretend they are not lowered? MariaDB [(none)]> show variables like 'wait_timeout'; +---------------+-------+ | Variable_name | Value | +---------------+-------+ | wait_timeout | 300 | +---------------+-------+ 1 row in set (0.00 sec) MariaDB [(none)]> show variables like 'wait_timeout'; +---------------+--------+ | Variable_name | Value | +---------------+--------+ | wait_timeout | 604800 | +---------------+--------+ 1 row in set (0.00 sec) wait_timeout = 604800 interactive_timeout = 604800

1 0