- discuss - lists.mariadb.org

[Maria-discuss] connection handling is buggy (HY000/2002): Resource temporarily unavailable)
by Reindl Harald 19 Aug '17

19 Aug '17

i started to play around with "thread_handling = pool-of-threads" with 10.2.7 and removed at that time the @mysqli_real_connect() error supression of my database-layer which also has a usleep() and retry-loop in case connection failed on so completly burried the issue PHP Warning: mysqli_real_connect() [<a href='http://at.php.net/manual/de/function.mysqli-real-connect.php'>function.mysqli-real-connect.php</a>]: (HY000/2002): Resource temporarily unavailable you should not see such messages when run a "ab -c 200 -n 500000 -k http://corecms/show_content.php?sid=2" with "max_connections = 300" _____________________________________ thread_handling = one-thread-per-connection [root@srv-rhsoft:~]$ cat php_error.log | wc -l 52596 thread_handling = pool-of-threads thread_pool_idle_timeout = 900 [root@srv-rhsoft:~]$ cat php_error.log | wc -l 39282 thread_handling = pool-of-threads thread_pool_oversubscribe = 10 thread_pool_idle_timeout = 900 thread_pool_priority = high [root@srv-rhsoft:~]$ cat php_error.log | wc -l 24849 since my database-layer makes a usleep(100000) before each retry and the retry-lop still has error-supression that means the cms waits 10% of all requests at least 0.1 seconds for the mariadb server which means the 4300 Requests/Second could be much higher if every connection suceeds at the first try (at least the thread pool seems to work slightly better then without) _____________________________________ what makes me really worry here is while the load is running (mysqld each time restartet before start apache-benchmark) +-------------------------+-------+ | Variable_name | Value | +-------------------------+-------+ | Threadpool_idle_threads | 181 | | Threadpool_threads | 189 | +-------------------------+-------+ after the benchmark has finished and the machine is idle: +-------------------------+-------+ | Variable_name | Value | +-------------------------+-------+ | Threadpool_idle_threads | 207 | | Threadpool_threads | 208 | +-------------------------+-------+ frankly i would expect at least that this numbers are going up while the load is running to at least 200 or not going up that high at all but don't refuse conncetions which is IMHO the point of a pool _____________________________________ the core-cms itself makes exactly two queries per request over 3 MyISAM tables, one cache-table with a pirmary key and the second one is a simple join on two tables with only 2 records, so not really something one should call real load select SQL_NO_CACHE * from cms1_cache where `hash`='fullmenu_1_2_0de0_0' select SQL_NO_CACHE * from `cms1_sub` join `cms1_haupt` on sid=2 and hid=shid mysqld as well as httpd had "LimitNOFILE=infinity" in the systemd-unit, the connection type is unix socket, so that all should not be a problem on a i7-3770 CPU @ 3.40GHz with 32 GB RAM it takes some time until the errors start to appear in the log, likely after httpd (mod_prefork) had forked enough worker to introduce real concurrency to the database

3 15

[Maria-discuss] Pacemaker and mariadb semi-sync
by Nils Carlson 10 Aug '17

10 Aug '17

Hi, I've been working on developing a pacemaker resource-agent for mariadb semi-sync replication. There is a pull request here on github: https://github.com/ClusterLabs/resource-agents/pull/929 I would be very happy for some review (and even testing) of this resource-agent from somebody with expertise in mariadb replication. The general idea is to select the master at startup and failure as the node with the highest GTID. AFTER_SYNC is used to ensure at least one slave will have all the updates. mariadb is started with --log-slave-updates to ensure that slaves log all events, so the binary log on each node should always be complete. The parameter set on each node is as follows: SET GLOBAL rpl_semi_sync_slave_enabled='ON', \ rpl_semi_sync_master_enabled='ON', \ rpl_semi_sync_master_wait_point='AFTER_SYNC', \ gtid_strict_mode='ON', \ sync_binlog=1, \ sync_master_info=1, \ sync_relay_log=1, \ sync_relay_log_info=1; I suspect this may be overkill, but I don't have the competence to judge. I have also found that calling "SHOW SLAVE STATUS;" may take a long time to display data when the slave is very busy (typically replicating after a failure). Is there any way to make sure it doesn't block? All feedback very welcome. Best Regards, Nils Carlson

3 2

[Maria-discuss] question about fast path for TRUNCATE TABLE
by MARK CALLAGHAN 06 Aug '17

06 Aug '17

This started as a question on a MyRocks list. MyRocks comes from MariaDB in this case and the code that determines whether the truncate table fast path is used looks different in MariaDB than in FB MySQL. By "fast path" for truncate I mean the use of drop/recreate for truncate. The slow path is delete one row at a time. In this case, truncate is doing delete one row at a time for MyRocks in MariaDB but drop/recreate in FB MySQL. https://groups.google.com/forum/#!topic/myrocks-dev/dhweTwN-9xg -- Mark Callaghan mdcallag(a)gmail.com

3 6

[Maria-discuss] Debian 9 support for MaxScale
by Martin Toth 03 Aug '17

03 Aug '17

Hi all, I would like to ask if there is some release date for fixing https://jira.mariadb.org/browse/MXS-1292 . Debian 9 should be included as a build target ASAP. I am installing only D9 systems on new servers and I am unable to use builds for MaxScale, so its unusable in D9. Thanks. Martin

2 4

[Maria-discuss] MariaDb 10.2 in RHEL 5.3
by Karthick Subramanian 03 Aug '17

03 Aug '17

Did anyone install the Maria DB 10.2 in RHEL Red Hat Enterprise Linux Server release 5.3 (Tikanga). I am planning to install this in Dev env, its not prod, Shall I try this. Regards, Karthick

3 2

[Maria-discuss] 2nd 2017 Developers Unconference
by Ian Gilfillan 03 Aug '17

03 Aug '17

The 2017 MariaDB Developers Unconference will be our first in Asia, and will be held in Shenzhen, China from 13 November - 17 November. There are 3 related events: 13 November - new contributor day 14-15 November - traditional developers unconference 16-17 November - patch days As always it's free to attend, and open to anyone interested in MariaDB development. Details at https://mariadb.org/2017-2-developers-unconference-and-related-events-shenz…

1 0

[Maria-discuss] Tokudb 5.7.18-16 fixes in Mariadb 10.2.8
by Reinis Rozitis 02 Aug '17

02 Aug '17

Hello, is there any chance/possibility for these fixes from Percona Server 5.7.18-16 to land in 10.2.8 release? Row counts in TokuDB could be lost intermittently after restarts ( https://jira.percona.com/browse/TDB-2 ) In TokuDB, two races in the fractal tree lock manager .. ( https://jira.percona.com/browse/TDB-3 ) rr

3 4

[Maria-discuss] 10.2.7 - Specified key was too long; max key length is 1000 bytes
by Reindl Harald 31 Jul '17

31 Jul '17

what the hell is this when the MYISAM database has a utf8 charset while this don't happen with latin1_german1_ci - this seems to be a regression in 10.2 and wasted an hour of time to realize what is going on just because anotehr guy did not take care of the database charset create table `cms1_formmailer_generic_cc` (`fg_key` mediumint(7) unsigned not null auto_increment, `fg_form` varchar(255) not null default '', `fg_email` varchar(255) not null default '', primary key(`fg_key`), key`fg_key` (`fg_form`, `fg_email`)) - Specified key was too long; max key length is 1000 bytes

2 3

[Maria-discuss] MariaDB unable to read the /etc/krb5.keytab
by Ali, Saqib 24 Jul '17

24 Jul '17

I am trying to setup MariaDB 10 with GSSAPI support. I following the instructions here: https://mariadb.com/kb/en/mariadb/gssapi-authentication-plugin/ However, whenever I try to start Maria DB I get the following [Warning] mysqld: GSSAPI plugin : default principal 'mariadb/hostname.tld@REALM' not found in keytab [ERROR] mysqld: Server GSSAPI error (major 851968, minor 2529639093) : gss_acquire_cred failed -Unspecified GSS failure. Minor code may provide more information. Keytab FILE:/etc/krb5.keytab is nonexistent or empty. [ERROR] Plugin 'gssapi' init function returned error. Sincerely, Saqib http://saqib.org

2 3

[Maria-discuss] TokuDB performance hit after 10.0.25
by Alessandro Ren 24 Jul '17

24 Jul '17

Hello, I've noticed a great performance hit after I upgraded my MariaDB install to 10.0.28, 10.0.29, 10.0.30 and 10.0.31. I even tried upgrading to MariaDB 10.2.7 and had the same problem. Bellow de details. MariaDB 10.0.25 - 13 rows in set (1.67 sec) MariaDB 10.0.31 - 13 rows in set (29.06 sec) The query: SELECT metric_id,date_format(entry_time, '%m:%Y') as date_group, unix_timestamp(entry_time) as entry_time, entry_time as datetime, avg(perf_value) as perf_value, warning, critical, baseline, lower_limit, upper_limit from service_perf_651 where service_id='56551' and metric_id='90183701' and entry_time>='2016-07-24 09:41:42' and entry_time<='2017-07-24 09:41:42' and ( (date_format(entry_time,'%w')=0 and ((date_format(entry_time,'%H')>=0 and date_format(entry_time,'%H') < 24))) or (date_format(entry_time,'%w')=1 and ((date_format(entry_time,'%H')>=0 and date_format(entry_time,'%H')<24) )) or (date_format(entry_time,'%w')=2 and ((date_format(entry_time,'%H')>=0 and date_format(entry_time,'%H')<24) )) or (date_format(entry_time,'%w')=3 and ((date_format(entry_time,'%H')>=0 and date_format(entry_time,'%H')<24) )) or (date_format(entry_time,'%w')=4 and ((date_format(entry_time,'%H')>=0 and date_format(entry_time,'%H')<24) )) or (date_format(entry_time,'%w')=5 and ((date_format(entry_time,'%H')>=0 and date_format(entry_time,'%H')<24) )) or (date_format(entry_time,'%w')=6 and ((date_format(entry_time,'%H')>=0 and date_format(entry_time,'%H')<24) )) ) group by date_group order by entry_time Explain query: +------+-------------+------------------+-------+----------------------------+---------+---------+------+------+----------------------------------------------+ | id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra | +------+-------------+------------------+-------+----------------------------+---------+---------+------+------+----------------------------------------------+ | 1 | SIMPLE | service_perf_651 | range | PRIMARY,service_perf_1_idx | PRIMARY | 16 | NULL | 1 | Using where; Using temporary; Using filesort | +------+-------------+------------------+-------+----------------------------+---------+---------+------+------+----------------------------------------------+ 1 row in set (0.06 sec) The table: CREATE TABLE `service_perf_651` ( `entry_time` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `service_id` int(11) unsigned NOT NULL DEFAULT '0', `metric_id` int(11) unsigned NOT NULL DEFAULT '0', `perf_value` float(13,3) DEFAULT NULL, `warning` float(13,3) DEFAULT NULL, `critical` float(13,3) DEFAULT NULL, `baseline` float(13,3) DEFAULT NULL, `lower_limit` float(13,3) DEFAULT NULL, `upper_limit` float(13,3) DEFAULT NULL, `reserved0` float(13,3) DEFAULT NULL, `reserved1` float(13,3) DEFAULT NULL, `reserved2` float(13,3) DEFAULT NULL, PRIMARY KEY (`entry_time`,`service_id`,`metric_id`), KEY `service_perf_1_idx` (`service_id`,`metric_id`,`entry_time`) ) ENGINE=TokuDB DEFAULT CHARSET=utf8 `compression`='tokudb_snappy' The size: 32497415 records Any idea what could be wrong? I even tried everything above on a different HW where the databse fit in memory in TokuDB, with the same performance hit. Tks for the help Alessandro Ren

6 8