- discuss - lists.mariadb.org

[Maria-discuss] 10.2.9: failing innodb tests
by Reindl Harald 29 Sep '17

29 Sep '17

that looks not good innodb.table_flags '32k,innodb' w1 [ fail ] Test ended at 2017-09-29 14:17:44 CURRENT_TEST: innodb.table_flags /usr/bin/mysqltest: Error on delete of '/usr/share/mysql-test/var/1/tmp/table_flags/ibtmp1' (Errcode: 2 "No such file or directory") --- /usr/share/mysql-test/suite/innodb/r/table_flags,32k.result~ 2017-09-26 17:07:32.071814438 +0200 +++ /usr/share/mysql-test/suite/innodb/r/table_flags,32k.reject 2017-09-29 14:17:44.692570878 +0200 @@ -176,7 +176,6 @@ SELECT * FROM tp; a DROP TABLE tr,tc,td,tz,tp; -ib_buffer_pool ib_logfile0 ib_logfile1 ibdata1 mysqltest: Result length mismatch - saving '/usr/share/mysql-test/var/1/log/innodb.table_flags-32k,innodb/' to '/usr/share/mysql-test/var/log/innodb.table_flags-32k,innodb/' ***Warnings generated in error logs during shutdown after running tests: innodb.table_flags 2017-09-29 14:17:39 139655137466688 [ERROR] InnoDB: Table `test`.`tc` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=129 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:17:39 139655137466688 [ERROR] InnoDB: Refusing to load './test/td.ibd' (id=3, flags=0x1a1); dictionary contains id=3, flags=0x101a1 2017-09-29 14:17:39 139655137466688 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2017-09-29 14:17:39 139655137466688 [ERROR] InnoDB: The error means the system cannot find the path specified. 2017-09-29 14:17:39 139655137466688 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2017-09-29 14:17:39 139655137466688 [Warning] InnoDB: Ignoring tablespace for `test`.`td` because it could not be opened. 2017-09-29 14:17:39 139655137466688 [ERROR] InnoDB: Table `test`.`tp` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=289 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:17:39 139655137466688 [ERROR] InnoDB: Table `test`.`tr` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=65 SYS_TABLES.MIX_LEN=4294967295 2017-09-29 14:17:39 139655137466688 [ERROR] InnoDB: Table `test`.`tz` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=12321 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:17:39 139654955267840 [ERROR] InnoDB: Table `test`.`tr` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=65 SYS_TABLES.MIX_LEN=4294967295 2017-09-29 14:17:39 139654955267840 [ERROR] InnoDB: Table `test`.`tc` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=129 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:17:39 139654955267840 [ERROR] InnoDB: Refusing to load './test/td.ibd' (id=3, flags=0x1a1); dictionary contains id=3, flags=0x101a1 2017-09-29 14:17:39 139654955267840 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2017-09-29 14:17:39 139654955267840 [ERROR] InnoDB: The error means the system cannot find the path specified. 2017-09-29 14:17:39 139654955267840 [ERROR] InnoDB: Table `test`.`tz` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=12321 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:17:39 139654955267840 [ERROR] InnoDB: Table `test`.`tp` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=289 SYS_TABLES.N_COLS=2147483649 innodb.table_flags '64k,innodb' w4 [ fail ] Test ended at 2017-09-29 14:17:46 CURRENT_TEST: innodb.table_flags /usr/bin/mysqltest: Error on delete of '/usr/share/mysql-test/var/4/tmp/table_flags/ibtmp1' (Errcode: 2 "No such file or directory") --- /usr/share/mysql-test/suite/innodb/r/table_flags,64k.result~ 2017-09-26 17:07:29.435940019 +0200 +++ /usr/share/mysql-test/suite/innodb/r/table_flags,64k.reject 2017-09-29 14:17:46.209498842 +0200 @@ -176,7 +176,6 @@ SELECT * FROM tp; a DROP TABLE tr,tc,td,tz,tp; -ib_buffer_pool ib_logfile0 ib_logfile1 ibdata1 mysqltest: Result length mismatch - saving '/usr/share/mysql-test/var/4/log/innodb.table_flags-64k,innodb/' to '/usr/share/mysql-test/var/log/innodb.table_flags-64k,innodb/' ***Warnings generated in error logs during shutdown after running tests: innodb.table_flags 2017-09-29 14:17:40 139995643373888 [ERROR] InnoDB: Table `test`.`tc` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=129 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:17:40 139995643373888 [ERROR] InnoDB: Refusing to load './test/td.ibd' (id=3, flags=0x1e1); dictionary contains id=3, flags=0x101e1 2017-09-29 14:17:40 139995643373888 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2017-09-29 14:17:40 139995643373888 [ERROR] InnoDB: The error means the system cannot find the path specified. 2017-09-29 14:17:40 139995643373888 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2017-09-29 14:17:40 139995643373888 [Warning] InnoDB: Ignoring tablespace for `test`.`td` because it could not be opened. 2017-09-29 14:17:40 139995643373888 [ERROR] InnoDB: Table `test`.`tp` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=289 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:17:40 139995643373888 [ERROR] InnoDB: Table `test`.`tr` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=65 SYS_TABLES.MIX_LEN=4294967295 2017-09-29 14:17:40 139995643373888 [ERROR] InnoDB: Table `test`.`tz` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=12321 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:17:41 139995554035456 [ERROR] InnoDB: Table `test`.`tr` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=65 SYS_TABLES.MIX_LEN=4294967295 2017-09-29 14:17:41 139995554035456 [ERROR] InnoDB: Table `test`.`tc` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=129 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:17:41 139995554035456 [ERROR] InnoDB: Refusing to load './test/td.ibd' (id=3, flags=0x1e1); dictionary contains id=3, flags=0x101e1 2017-09-29 14:17:41 139995554035456 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2017-09-29 14:17:41 139995554035456 [ERROR] InnoDB: The error means the system cannot find the path specified. 2017-09-29 14:17:41 139995554035456 [ERROR] InnoDB: Table `test`.`tz` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=12321 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:17:41 139995554035456 [ERROR] InnoDB: Table `test`.`tp` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=289 SYS_TABLES.N_COLS=2147483649 innodb.table_flags '4k,innodb' w2 [ fail ] Test ended at 2017-09-29 14:18:19 CURRENT_TEST: innodb.table_flags /usr/bin/mysqltest: Error on delete of '/usr/share/mysql-test/var/2/tmp/table_flags/ibtmp1' (Errcode: 2 "No such file or directory") --- /usr/share/mysql-test/suite/innodb/r/table_flags,4k.result~ 2017-09-26 17:08:10.304992901 +0200 +++ /usr/share/mysql-test/suite/innodb/r/table_flags,4k.reject 2017-09-29 14:18:18.954943828 +0200 @@ -174,7 +174,6 @@ SELECT * FROM tp; a DROP TABLE tr,tc,td,tz,tp; -ib_buffer_pool ib_logfile0 ib_logfile1 ibdata1 mysqltest: Result length mismatch - saving '/usr/share/mysql-test/var/2/log/innodb.table_flags-4k,innodb/' to '/usr/share/mysql-test/var/log/innodb.table_flags-4k,innodb/' ***Warnings generated in error logs during shutdown after running tests: innodb.table_flags 2017-09-29 14:18:13 140291687692608 [ERROR] InnoDB: Table `test`.`tc` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=129 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:18:13 140291687692608 [ERROR] InnoDB: Refusing to load './test/td.ibd' (id=3, flags=0xe1); dictionary contains id=3, flags=0x100e1 2017-09-29 14:18:13 140291687692608 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2017-09-29 14:18:13 140291687692608 [ERROR] InnoDB: The error means the system cannot find the path specified. 2017-09-29 14:18:13 140291687692608 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2017-09-29 14:18:13 140291687692608 [Warning] InnoDB: Ignoring tablespace for `test`.`td` because it could not be opened. 2017-09-29 14:18:13 140291687692608 [ERROR] InnoDB: Table `test`.`tp` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=289 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:18:13 140291687692608 [ERROR] InnoDB: Table `test`.`tr` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=65 SYS_TABLES.MIX_LEN=4294967295 2017-09-29 14:18:13 140291687692608 [ERROR] InnoDB: Table `test`.`tz` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=12323 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:18:13 140291589162752 [ERROR] InnoDB: Table `test`.`tr` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=65 SYS_TABLES.MIX_LEN=4294967295 2017-09-29 14:18:13 140291589162752 [ERROR] InnoDB: Table `test`.`tc` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=129 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:18:13 140291589162752 [ERROR] InnoDB: Refusing to load './test/td.ibd' (id=3, flags=0xe1); dictionary contains id=3, flags=0x100e1 2017-09-29 14:18:13 140291589162752 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2017-09-29 14:18:13 140291589162752 [ERROR] InnoDB: The error means the system cannot find the path specified. 2017-09-29 14:18:13 140291589162752 [ERROR] InnoDB: Table `test`.`tz` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=12323 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:18:13 140291589162752 [ERROR] InnoDB: Table `test`.`tp` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=289 SYS_TABLES.N_COLS=2147483649 sys_vars.innodb_file_per_table_basic 'innodb' w2 [ pass ] 4 innodb.index_tree_operation 'innodb' w1 [ pass ] 19 innodb.innodb_bug60049 'innodb' w3 [ pass ] 2522 innodb.create_isl_with_direct 'innodb' w2 [ pass ] 8 innodb.innodb_force_pk 'innodb' w2 [ pass ] 13 innodb.101_compatibility '8k,innodb' w4 [ pass ] 4519 main.flush_block_commit_notembedded 'innodb' w3 [ pass ] 2061 binlog.binlog_checksum 'innodb,row' w2 [ pass ] 834 main.mysql_upgrade 'innodb' w3 [ skipped ] Test requires partitioning innodb.alter_missing_tablespace '8k,innodb' w4 [ pass ] 2518 innodb.innodb_bug14147491 'innodb' w1 [ pass ] 4107 innodb.innodb_autoinc_lock_mode_zero 'innodb' w3 [ pass ] 12 innodb.innodb-mdev-7408 'innodb' w1 [ pass ] 6 innodb.innodb_bug42101-nonzero 'innodb' w3 [ pass ] 5 innodb.innodb-alter-nullable '8k,innodb' w4 [ pass ] 52 innodb.innodb_information_schema_buffer 'innodb' w1 [ pass ] 25 innodb.innodb-alter-table '8k,innodb' w4 [ pass ] 523 binlog.binlog_commit_wait 'innodb,row' w2 [ pass ] 5275 binlog.binlog_dmls_on_tmp_tables_readonly 'innodb,row' w2 [ pass ] 11 innodb.innodb_bug39438 'innodb' w3 [ pass ] 8 main.bug46760 'innodb' w1 [ pass ] 12 main.row-checksum-old 'innodb' w3 [ pass ] 16 innodb.innodb_trx_weight 'innodb' w1 [ pass ] 40 innodb.innodb-alter 'innodb' w3 [ pass ] 245 main.row-checksum 'innodb' w1 [ pass ] 10 innodb.temporary_table_optimization 'innodb' w3 [ pass ] 47 innodb.data_types 'innodb' w1 [ pass ] 5 innodb.innodb-index-online-norebuild 'innodb' w3 [ pass ] 8 innodb.innodb-stats-modified-counter 'innodb' w1 [ pass ] 8 innodb.table_flags '8k,innodb' w4 [ fail ] Test ended at 2017-09-29 14:18:40 CURRENT_TEST: innodb.table_flags /usr/bin/mysqltest: Error on delete of '/usr/share/mysql-test/var/4/tmp/table_flags/ibtmp1' (Errcode: 2 "No such file or directory") --- /usr/share/mysql-test/suite/innodb/r/table_flags,8k.result~ 2017-09-26 17:08:28.249137992 +0200 +++ /usr/share/mysql-test/suite/innodb/r/table_flags,8k.reject 2017-09-29 14:18:40.460922576 +0200 @@ -174,7 +174,6 @@ SELECT * FROM tp; a DROP TABLE tr,tc,td,tz,tp; -ib_buffer_pool ib_logfile0 ib_logfile1 ibdata1 mysqltest: Result length mismatch - saving '/usr/share/mysql-test/var/4/log/innodb.table_flags-8k,innodb/' to '/usr/share/mysql-test/var/log/innodb.table_flags-8k,innodb/' ***Warnings generated in error logs during shutdown after running tests: innodb.table_flags 2017-09-29 14:18:35 139736414353728 [ERROR] InnoDB: Table `test`.`tc` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=129 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:18:35 139736414353728 [ERROR] InnoDB: Refusing to load './test/td.ibd' (id=3, flags=0x121); dictionary contains id=3, flags=0x10121 2017-09-29 14:18:35 139736414353728 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2017-09-29 14:18:35 139736414353728 [ERROR] InnoDB: The error means the system cannot find the path specified. 2017-09-29 14:18:35 139736414353728 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2017-09-29 14:18:35 139736414353728 [Warning] InnoDB: Ignoring tablespace for `test`.`td` because it could not be opened. 2017-09-29 14:18:35 139736414353728 [ERROR] InnoDB: Table `test`.`tp` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=289 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:18:35 139736414353728 [ERROR] InnoDB: Table `test`.`tr` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=65 SYS_TABLES.MIX_LEN=4294967295 2017-09-29 14:18:35 139736414353728 [ERROR] InnoDB: Table `test`.`tz` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=12323 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:18:35 139736317077248 [ERROR] InnoDB: Table `test`.`tr` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=65 SYS_TABLES.MIX_LEN=4294967295 2017-09-29 14:18:35 139736317077248 [ERROR] InnoDB: Table `test`.`tc` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=129 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:18:35 139736317077248 [ERROR] InnoDB: Refusing to load './test/td.ibd' (id=3, flags=0x121); dictionary contains id=3, flags=0x10121 2017-09-29 14:18:35 139736317077248 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2017-09-29 14:18:35 139736317077248 [ERROR] InnoDB: The error means the system cannot find the path specified. 2017-09-29 14:18:35 139736317077248 [ERROR] InnoDB: Table `test`.`tz` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=12323 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:18:35 139736317077248 [ERROR] InnoDB: Table `test`.`tp` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=289 SYS_TABLES.N_COLS=2147483649 innodb.innodb_information_schema_tables 'innodb' w3 [ pass ] 17 innodb.innodb-trim 'innodb' w1 [ pass ] 1101 innodb.innodb-autoinc-56228 'innodb' w1 [ pass ] 4 innodb.innodb_mysql_rbk 'innodb' w3 [ pass ] 3885 binlog.binlog_implicit_commit 'innodb,row' w2 [ pass ] 16518 binlog.binlog_innodb 'innodb,row' w2 [ pass ] 2708 innodb.innodb-lock-schedule-algorithm 'innodb' w4 [ pass ] 10193 main.commit_1innodb 'innodb' w2 [ fail ] Test ended at 2017-09-29 14:18:51 CURRENT_TEST: main.commit_1innodb --- /usr/share/mysql-test/r/commit_1innodb.result 2017-09-25 08:33:24.000000000 +0200 +++ /usr/share/mysql-test/r/commit_1innodb.reject 2017-09-29 14:18:51.351405429 +0200 @@ -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 - saving '/usr/share/mysql-test/var/2/log/main.commit_1innodb-innodb/' to '/usr/share/mysql-test/var/log/main.commit_1innodb-innodb/'

1 0

[Maria-discuss] perl-dbi
by Ruben Safir 26 Sep '17

26 Sep '17

Does anything need to be ported to mariabd if we are using perl::DBI or can I just pull the files from cpan. I have a large number of legacy applications I need to adapt based on MYSQL::DBI modules. Ruben -- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www2.mrbrklyn.com/resources - Unpublished Archive http://www.coinhangout.com - coins! http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and and extermination camps, but incompatible with living as a free human being. -RI Safir 2013

1 0

[Maria-discuss] mysqld_safe and pid files
by Ruben Safir 26 Sep '17

26 Sep '17

hello monty et al i'm trying to write an init script for maria and artix, which is using openrc I got it to start up but the pid-file is a problem and I think that the command line options for mysqld_safe is not working. it doesnt create the specified pid file [www3 ~]# /usr/bin/mysqld_safe --pid-file=/run/mariadb.pid 170926 10:41:52 mysqld_safe Logging to '/usr/local/var/www3.err'. 170926 10:41:52 mysqld_safe Starting mysqld daemon with databases from /usr/local/var [www3 ~]# cat /run/mariadb.pid cat: /run/mariadb.pid: No such file or directory [www3 ~]# tail -f /usr/local/var/www3.err 2017-09-26 10:41:53 139828287336192 [Note] InnoDB: 128 rollback segment(s) are active. 2017-09-26 10:41:53 139828287336192 [Note] InnoDB: Waiting for purge to start 2017-09-26 10:41:53 139828287336192 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.0 started; log sequence number 1601111 2017-09-26 10:41:53 139828287336192 [Note] Plugin 'FEEDBACK' is disabled. 2017-09-26 10:41:53 139827658368768 [Note] InnoDB: Dumping buffer pool(s) not yet started 2017-09-26 10:41:53 139828287171328 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1146: Table 'mysql.gtid_slave_pos' doesn't exist 2017-09-26 10:41:53 139828287336192 [Note] Server socket created on IP: '::'. 2017-09-26 10:41:53 139828286868224 [ERROR] mysqld: Can't create/write to file '/run/mariadb.pid' (Errcode: 13 "Permission denied") 2017-09-26 10:41:53 139828286868224 [ERROR] Can't start server: can't create PID file: Permission denied 170926 10:41:53 mysqld_safe mysqld from pid file /run/mariadb.pid ended drwxr-xr-x 16 root root 620 Sep 25 21:45 run what do you recommend to do? The system is uniform -- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www2.mrbrklyn.com/resources - Unpublished Archive http://www.coinhangout.com - coins! http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and and extermination camps, but incompatible with living as a free human being. -RI Safir 2013

3 6

Re: [Maria-discuss] URI data source for XML/JSON CONNECT tables?
by Olivier Bertrand 14 Sep '17

14 Sep '17

Hi! Le 18/02/2015 à 08:05, Kolbe Kegel a écrit : > Hi! > > I had some fun using the JSON table type recently. But what fun is it to read JSON from a file. FYI, CONNECT new versions (already distributed in 10.2) include getting Json info directly from MongoDB collections. > JSON comes from RESTful APIs :) > > Has there been any thought about functionality to read JSON from a URI? See above and the attached doc. > This introduces loads of complications and dependencies, but maybe it'd be worth looking into. Or maybe that's something that could be provided by some other plugin that'd handle the HTTP heavy lifting? > > We'd want to take into account that most RESTful APIs worth pulling JSON from would require some form of authentication that we probably would not want to force users to store in their table definition. > > Kolbe > Olivier

1 0

[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