- discuss - lists.mariadb.org

[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 24 Feb '17

24 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