August 2017 - discuss - lists.mariadb.org

[Maria-discuss] Galera 23.2.7 mariadb 5.5.33a msvc 1600 binaries available
by Yann Nayn 18 Nov '24

18 Nov '24

Binaries have been uploaded for both x86 and amd64 platforms. due to github file size limitations , the directories have been uploaded unarchived. for Win33 binaries , please checkout https://github.com/YannNayn/galera-mariadb-win32.git and for Win64(amd64) binaries (being uploaded/pushed): https://github.com/YannNayn/galera-mariadb-win64.git they are not recommended for a production environment. in the my.cnf file: _________ wsrep_provider=galera_smm.dll wsrep_sst_method=msqldump # percona xtrabackup will be tested soon _________ libevent and openssl(the provided binaries use respectively 2.1.3-alpha and 1.1.0-dev versions ) will be added next on github some limitations are stated on openssl website copied here for convenience: ____________ from http://www.openssl.org/ ____________ This software package uses strong cryptography, so even if it is created, maintained and distributed from liberal countries in Europe (where it is legal to do this), it falls under certain export/import and/or use restrictions in some other parts of the world. PLEASE REMEMBER THAT EXPORT/IMPORT AND/OR USE OF STRONG CRYPTOGRAPHY SOFTWARE, PROVIDING CRYPTOGRAPHY HOOKS OR EVEN JUST COMMUNICATING TECHNICAL DETAILS ABOUT CRYPTOGRAPHY SOFTWARE IS ILLEGAL IN SOME PARTS OF THE WORLD. SO, WHEN YOU IMPORT THIS PACKAGE TO YOUR COUNTRY, RE-DISTRIBUTE IT FROM THERE OR EVEN JUST EMAIL TECHNICAL SUGGESTIONS OR EVEN SOURCE PATCHES TO THE AUTHOR OR OTHER PEOPLE YOU ARE STRONGLY ADVISED TO PAY CLOSE ATTENTION TO ANY EXPORT/IMPORT AND/OR USE LAWS WHICH APPLY TO YOU. THE AUTHORS OF OPENSSL ARE NOT LIABLE FOR ANY VIOLATIONS YOU MAKE HERE. SO BE CAREFUL, IT IS YOUR RESPONSIBILITY. ________________________________________________ msvc 1600 redistributables SP1 need to be installed/available on the target machine: vcredist_x86.exe : http://www.microsoft.com/en-us/download/details.aspx?id=8328 vcredist_x64.exe : http://www.microsoft.com/en-us/download/details.aspx?id=13523 MSys binaries are provided and msqld.bat should then be used instead of mysqld.exe (e.g. mysld.bat --console --wsrep_cluster_address=gcomm:// ) in order to have a working sh shell(cygwin has been proved to do it as well) Please note that oqgraph is disabled (boost trunk is used , that is 1.55) Comments and suggestions are welcome.

2 1

[Maria-discuss] why stdout? -> [Note] /usr/libexec/mysqld (mysqld 10.0.20-MariaDB) starting as process 115096
by Reindl Harald 05 Jul '20

05 Jul '20

Aug 6 12:24:24 testserver mysqld: 150806 12:24:24 [Note] /usr/libexec/mysqld (mysqld 10.0.20-MariaDB) starting as process 115096 ... why is this now stdout instead mysql logs? on systemd based distributions that spits now to the global syslog and finally on machines restarting 2 instances every hour for backup reasons it annoys until 10.0.19 or 10.0.20 that was not this way

5 13

[Maria-discuss] Charsets and collations
by Peter Laursen 20 Apr '18

20 Apr '18

Does anybody know if there are any plans to bring collations added in MySQL 8 - refer http://mysqlserverteam.com/new-collations-in-mysql-8-0-0/ - to MariaDB and are there any plans to change the default charset to a unicode-based one? -- Peter -- Webyog

2 2

[Maria-discuss] Mariadb cluster on windows
by vv2599 06 Sep '17

06 Sep '17

Hello Guys, I would like to know if there is a way to setup mariadb cluster on windows or is there any way that a high availability system can be setup on windows server 2008. Appreciate any response. Regards, Vino

4 7

[Maria-discuss] Issues with get SSL replication going (I.e. Encrypting Replication Traffic as well as Encrypting SST Traffic)
by Brent Clark 30 Aug '17

30 Aug '17

Good day Guys Im trying to get SSL replication going (I.e. Encrypting Replication Traffic as well as Encrypting SST Traffic). For the likes of me I just cant get it working. If I set the variable, encrypt = 0 (i.e. encryption off) replication works. Please can I ask if someone could please review my logs / setup are see where my issue lays. Here is my configuration setup https://pastebin.com/9JDP4LCr This is the /var/log/mysql/error.log of First node (i.e. Donor) https://pastebin.com/MrWDcECA This is the /var/log/mysql/error.log of 2nd node (i.e. joiner) https://pastebin.com/wZiNDP4P If anyone can assist, it would most appreciated. Kind Regards Brent Clark

1 0

Re: [Maria-discuss] Pacemaker and mariadb semi-sync
by Pavel Ivanov 23 Aug '17

23 Aug '17

Yes, having processlist while it's hung might be handy. On Tue, Aug 22, 2017 at 3:45 PM, Nils Carlson <nils.carlson(a)ludd.ltu.se> wrote: > On 08/22/2017 10:42 PM, Pavel Ivanov wrote: > >> Can you clarify what SHOW SLAVE STATUS blocks on for you? > > Not really. Basically, just after performing a failover, I run SHOW SLAVE > STATUS on the slave and that can take up to 30 seconds sometimes before the > query returns. Once it does return everything looks like normal. I can try > to dump the thread status maybe. > > /Nils > > > >> On Sun, Aug 20, 2017 at 9:47 AM, Nils Carlson <nils.carlson(a)ludd.ltu.se> >> wrote: >>> >>> Hi Pavel and Kristian, >>> >>> On 08/10/2017 10:58 PM, Pavel Ivanov wrote: >>>> >>>> Note also that you don't want to set rpl_semi_sync_master_enabled='ON' >>>> on all your slaves, it should be set only on the master. With the >>>> setting your slaves' SQL threads will hang waiting for semi-sync ack >>>> as well, and they will hang forever if >>>> rpl_semi_sync_master_wait_no_slave is set to ON too. >>>> >>> Thank you. >>> >>>> On Wed, Aug 9, 2017 at 2:30 AM, Kristian Nielsen >>>> <knielsen(a)knielsen-hq.org> wrote: >>>>> >>>>> Hope this helps, >>> >>> >>> And thank you for all this! >>> >>> I have updated the resource-agent based on this and run some light >>> testing. >>> I will try to write automated tests soon. >>> >>> I was also wondering about one thing, the block SHOW SLAVE STATUS >>> command. >>> Is there any way to ensure this doesn't block? Maybe this is something to >>> suggest to the development mailing list? >>> >>> Thanks again. >>> >>> Cheers, >>> Nils >>> >>> >>>>> - Kristian. >>>>> >>>>> _______________________________________________ >>>>> 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] Pacemaker and mariadb semi-sync
by Pavel Ivanov 23 Aug '17

23 Aug '17

Can you clarify what SHOW SLAVE STATUS blocks on for you? On Sun, Aug 20, 2017 at 9:47 AM, Nils Carlson <nils.carlson(a)ludd.ltu.se> wrote: > Hi Pavel and Kristian, > > On 08/10/2017 10:58 PM, Pavel Ivanov wrote: >> >> Note also that you don't want to set rpl_semi_sync_master_enabled='ON' >> on all your slaves, it should be set only on the master. With the >> setting your slaves' SQL threads will hang waiting for semi-sync ack >> as well, and they will hang forever if >> rpl_semi_sync_master_wait_no_slave is set to ON too. >> > Thank you. > >> On Wed, Aug 9, 2017 at 2:30 AM, Kristian Nielsen >> <knielsen(a)knielsen-hq.org> wrote: >>> >>> Hope this helps, > > > And thank you for all this! > > I have updated the resource-agent based on this and run some light testing. > I will try to write automated tests soon. > > I was also wondering about one thing, the block SHOW SLAVE STATUS command. > Is there any way to ensure this doesn't block? Maybe this is something to > suggest to the development mailing list? > > Thanks again. > > Cheers, > Nils > > >>> >>> - Kristian. >>> >>> _______________________________________________ >>> 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] connection handling is buggy (HY000/2002): Resource temporarily unavailable)
by Reindl Harald 20 Aug '17

20 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 11 Aug '17

11 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