July 2014 - discuss - lists.mariadb.org

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

05 Dec '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.

3 2

[Maria-discuss] Spider and query cache
by Roberto Spadim 23 Sep '14

23 Sep '14

Hi guys! I'm with a doubt, spider engine don't allow query cache right? But does it use sql_cache sql_no_cache when possible? -- Roberto Spadim SPAEmpresarial Eng. Automação e Controle

5 18

[Maria-discuss] 5.5.38: compiler warnings
by Reindl Harald 05 Aug '14

05 Aug '14

maybe worth a look /mariadb-5.5.38/strings/decimal.c:2139:55: warning: array subscript is below array bounds [-Warray-bounds] /mariadb-5.5.38/strings/decimal.c:2139:59: warning: array subscript is below array bounds [-Warray-bounds] /mariadb-5.5.38/strings/decimal.c:2154:52: warning: array subscript is below array bounds [-Warray-bounds] /mariadb-5.5.38/strings/decimal.c:2154:56: warning: array subscript is below array bounds [-Warray-bounds] /mariadb-5.5.38/strings/decimal.c:264:56: warning: array subscript is below array bounds [-Warray-bounds] /mariadb-5.5.38/strings/decimal.c:264:60: warning: array subscript is below array bounds [-Warray-bounds] /mariadb-5.5.38/strings/decimal.c:300:26: warning: array subscript is above array bounds [-Warray-bounds] /mariadb-5.5.38/strings/decimal.c:300:30: warning: array subscript is above array bounds [-Warray-bounds] /mariadb-5.5.38/strings/decimal.c:478:31: warning: array subscript is below array bounds [-Warray-bounds] /mariadb-5.5.38/strings/decimal.c:478:35: warning: array subscript is below array bounds [-Warray-bounds] /mariadb-5.5.38/strings/decimal.c:496:29: warning: array subscript is above array bounds [-Warray-bounds] /mariadb-5.5.38/strings/decimal.c:496:33: warning: array subscript is above array bounds [-Warray-bounds] ___________________________________________________________________________ /mariadb-5.5.38/client/mysql.cc:3488:1: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/mysys/lf_alloc-pin.c:337:13: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/mysys/mf_iocache2.c:345:8: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/mysys/mf_qsort.c:95:9: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/mysys/mf_qsort.c:98:9: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/plugin/feedback/sender_thread.cc:170:13: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/sql-common/client.c:2379:12: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/sql-common/client.c:2462:12: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/sql/field.cc:8567:1: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/sql/ha_partition.cc:2377:6: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/sql/ha_partition.cc:2775:6: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/sql/log_event.cc:9998:1: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/sql/log_event_old.cc:2019:1: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/sql/log_event_old.cc:516:1: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/sql/opt_range.cc:13595:5: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/sql/opt_range.cc:13832:5: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/sql/opt_range.cc:13973:5: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/sql/sql_acl.cc:8047:13: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/sql/sql_insert.cc:1580:5: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/sql/sql_plugin.cc:1212:13: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/sql/sql_plugin.cc:1509:5: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/sql/sql_plugin.cc:1896:6: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/sql/sql_plugin.cc:2308:6: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/sql/sql_plugin.cc:2739:21: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/sql/sql_plugin.cc:2780:21: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/sql/unireg.cc:112:6: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/maria/ma_blockrec.c:2412:16: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/maria/ma_blockrec.c:5140:9: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/maria/ma_check.c:3210:12: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/maria/ma_check.c:5974:5: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/maria/ma_check.c:848:12: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/maria/ma_delete.c:197:9: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/maria/ma_delete.c:282:12: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/maria/ma_delete.c:547:12: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/maria/ma_dynrec.c:1550:9: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/maria/ma_dynrec.c:1588:9: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/maria/ma_dynrec.c:243:9: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/maria/ma_dynrec.c:273:9: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/maria/ma_open.c:1770:9: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/maria/ma_pagecache.c:3947:9: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/maria/maria_chk.c:1742:12: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/maria/maria_chk.c:1936:12: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/maria/maria_pack.c:2101:17: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/maria/maria_pack.c:2402:12: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/maria/maria_pack.c:850:12: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/maria/ma_rt_index.c:1121:9: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/maria/ma_rt_index.c:1266:9: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/maria/ma_rt_index.c:324:12: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/maria/ma_rt_index.c:57:12: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/maria/ma_rt_index.c:605:12: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/maria/ma_rt_index.c:727:5: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/maria/ma_rt_index.c:924:12: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/maria/ma_rt_split.c:367:5: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/maria/ma_write.c:613:12: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/myisam/mi_check.c:2010:12: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/myisam/mi_check.c:4227:5: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/myisam/mi_check.c:731:12: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/myisam/mi_delete.c:146:12: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/myisam/mi_delete.c:215:12: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/myisam/mi_delete.c:401:12: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/myisam/mi_open.c:72:10: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/myisam/mi_write.c:335:12: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/myisam/myisamchk.c:1439:12: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/myisam/myisamchk.c:1618:12: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/myisam/myisampack.c:2132:17: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/myisam/myisampack.c:2435:12: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/myisam/myisampack.c:873:12: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/myisam/rt_index.c:1035:9: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/myisam/rt_index.c:292:12: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/myisam/rt_index.c:539:12: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/myisam/rt_index.c:54:12: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/myisam/rt_index.c:764:12: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/myisam/rt_index.c:908:5: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/myisam/rt_split.c:244:5: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/xtradb/log/log0log.c:277:1: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/storage/xtradb/log/log0recv.c:2971:1: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/strings/decimal.c:1310:5: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector] /mariadb-5.5.38/strings/decimal.c:2114:12: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector]

2 1

[Maria-discuss] Need input on crashes on 3rd mariaDB server
by Jeroen Andriessen 30 Jul '14

30 Jul '14

Hi all, We’re currently using a system with three clustered maria-db masters. We are experiencing occasional (once every three weeks or so) crashes of one of the server, namely our third server, which we use as a dedicated donor for the other two. The crashes point to a BF-BF X lock conflict in the same table. I was wondering how to proceed with identifying and localising the problem and counteracting it. We have already tried to rebuild the database in question from an earlier mysql dump, to no effect. Any input is welcome, thanks. —— BF-BF X lock conflict RECORD LOCKS space id 36361 page no 10 n bits 264 index `***REDACTED***` of table `***REDACTED***`.`***REDACTED***` trx id D860A49 lock_mode X locks rec but not gap 140724 6:10:53 [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 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: 5.5.38-MariaDB-wsrep-log key_buffer_size=134217728 read_buffer_size=131072 max_used_connections=7 max_threads=1002 thread_count=20 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2329723 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0x7f57b3412000 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 = 0x7f5c1a16b940 thread_stack 0x48000 (my_addr_resolve failure: fork) /usr/sbin/mysqld(my_print_stacktrace+0x2b) [0xa95bab] /usr/sbin/mysqld(handle_fatal_signal+0x398) [0x6ebc58] /lib64/libpthread.so.0() [0x34e7e0f710] /lib64/libc.so.6(gsignal+0x35) [0x34e7632925] /lib64/libc.so.6(abort+0x175) [0x34e7634105] /usr/sbin/mysqld() [0x50e940] /usr/sbin/mysqld() [0x92c0ff] /usr/sbin/mysqld() [0x931799] /usr/sbin/mysqld() [0x932566] /usr/sbin/mysqld() [0x968a65] /usr/sbin/mysqld() [0x85fe3b] /usr/sbin/mysqld() [0x863ada] /usr/sbin/mysqld() [0x8642de] /usr/sbin/mysqld() [0x84e571] /usr/sbin/mysqld() [0x8337b2] /usr/sbin/mysqld(handler::ha_delete_row(unsigned char const*)+0xb0) [0x6f3640] /usr/sbin/mysqld(Delete_rows_log_event::do_exec_row(Relay_log_info const*)+0x10d) [0x7a41dd] /usr/sbin/mysqld(Rows_log_event::do_apply_event(Relay_log_info const*)+0x26a) [0x798e2a] /usr/sbin/mysqld(wsrep_apply_cb(void*, void const*, unsigned long, unsigned int, wsrep_trx_meta const*)+0x598) [0x69f988] /usr/lib64/galera/libgalera_smm.so(galera::TrxHandle::apply(void*, wsrep_cb_status (*)(void*, void const*, unsigned long, unsigned int, wsrep_trx_meta const*), wsrep_trx_meta const&) const+0xb1) [0x7f5c197462c1] /usr/lib64/galera/libgalera_smm.so(+0x1aaf95) [0x7f5c1977df95] /usr/lib64/galera/libgalera_smm.so(galera::ReplicatorSMM::apply_trx(void*, galera::TrxHandle*)+0x283) [0x7f5c1977ee03] /usr/lib64/galera/libgalera_smm.so(galera::ReplicatorSMM::process_trx(void*, galera::TrxHandle*)+0x45) [0x7f5c1977f6f5] /usr/lib64/galera/libgalera_smm.so(galera::GcsActionSource::dispatch(void*, gcs_action const&, bool&)+0x2c9) [0x7f5c1975c349] /usr/lib64/galera/libgalera_smm.so(galera::GcsActionSource::process(void*, bool&)+0x63) [0x7f5c1975c823] /usr/lib64/galera/libgalera_smm.so(galera::ReplicatorSMM::async_recv(void*)+0x93) [0x7f5c1977b3f3] /usr/lib64/galera/libgalera_smm.so(galera_recv+0x23) [0x7f5c19790743] /usr/sbin/mysqld() [0x6a037f] /usr/sbin/mysqld(start_wsrep_THD+0x365) [0x527415] /lib64/libpthread.so.0() [0x34e7e079d1] /lib64/libc.so.6(clone+0x6d) [0x34e76e8b5d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x0): is an invalid pointer Connection ID (thread ID): 17 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=off 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. 140724 06:10:53 mysqld_safe Number of processes running now: 0 140724 06:10:53 mysqld_safe WSREP: not restarting wsrep node automatically 140724 06:10:53 mysqld_safe mysqld from pid file /var/lib/mysql/***hostnameredacted***.pid ended

1 0

[Maria-discuss] cross-compiling mariadb-galera
by Sylvain Raybaud 25 Jul '14

25 Jul '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear MariaDB community, I've got a question regarding the cross-compilation of MariaDB. More specifically I'm trying to create a buildroot package for MariaDB Galera cluster. I added mariadb-galera to buildroot/package/Config.in and created a folder buildroot/package/mariadb-galera containing the following files (normal buildroot procedure): buildroot/package/mariadb-galera/Config.in buildroot/package/mariadb-galera/mariadb-galera.mk mariadb-galera.mk contains, among other things: MARIADB_GALERA_CONF_OPT = -DCMAKE_CROSSCOMPILING=1 -DWITH_WSREP=ON - -DWITH_INNODB_DISALLOW_WRITES=1 I'm building for Raspberry Pi. I'm using version 10.0.12. The build fails with: CMake Error at storage/xtradb/CMakeLists.txt:434 (MESSAGE): Percona XtraDB is not supported on this platform This error is trigger in storage/xtradb/CMakeLists.txt when XTRADB_OK is not set; it seems to me that XTRADB_OK is set in either one of the following cases: 1) CMAKE_CROSSCOMPILING is NOT set and some tests are successful (thus setting HAVE_IB_GCC_ATOMIC_BUILTINS) or 2) We're compiling for MSVC or CMAKE_SYSTEM_NAME is "SunOS" and some other conditions are met. Since I'm not compiling for MSVC or SunOS and I'm crosscompiling indeed, XTRADB_OK is not set and the error is triggered. Here I'm stuck. I've got the feeling that as such one cannot cross-compile xtradb because XTRADB_OK will never be set; or maybe with proper options passed to cmake the tests would be made elsewhere and HAVE_IB_GCC_ATOMIC_BUILTINS would be set beforehand? Or maybe I should patch this CMakeLists.txt? Or maybe I should just compile without xtradb altogether, if that's possible? Any guidance would be appreciated. Cheers, Sylvain Raybaud PS: I was not sure whether to post this on -discuss or -devel so I opted for the most general list. Don't hesitate to ask me to repost elsewhere if you feel this would be more appropriate. - -- Sylvain Raybaud www.green-communications.fr -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJT0hcjAAoJEEkkwl4JtJ9yJx8P/3tGWbYBK+WFAmG0qWH8AJkI UjwNkNBri+p7GwaaHl/cnNrerTaNSFsRrusUvwr9UwSjn2xZgsYd+v/I97tMzORi sjLFYt7JM42/Hm3PmMshpr+B+8CX3oZ9NQa/vy6sJ4jZrYZ/GsjsFMB14HD8FG0I qbySRVxssrixl856ZVPae9W1aVK06oEAiANAQhZ/+ZJOdIMKB+32rXfdDHJR8jGA pseZG74xoZfjWkNQ0D4qmZfkJpeAk1wR1mAU1QE5nFSauvjqGEgYzzUokh3Tp/2/ zyl+dMgu6eG3rl+zrF8Pf6cDoLr2cM6SjlTq4ggMVITLl0CT6x2r9xJQVe8XdqrM LDAhjeHhzKrPbq3AmKKX3UBTj+01v/VdSp3ro73I4ruu8g6XSqF+2DQAOqLZ4qDH 66KZLewagdsuekwCx07jDHRFg840lKchUhXxtuu8GLb1KFIgdbYa4th2rP1U+idf NFHYmOMVyOE20hYa1F4mOI0bAYHThY3oqr4SxnqVYVl6+Rxu9OfBEEfkTi1i4wTz S807RR4N7LC7SbiNxaU3DULycZIDysaOv6f5xoJf8VvUBCis0cwahYzqUj1B97p9 fAYmEhmS7W/YS0R56dhi2S7v//VNbdpLhmpIXPhmwHjvBeyBoEskXovHcdu1wgSQ 58S1ykhVWcHgNpXvZa55 =OFL8 -----END PGP SIGNATURE-----

1 0

[Maria-discuss] race conditions after SIGTERM
by Reindl Harald 24 Jul '14

24 Jul '14

how can that script lead to a race condition where files are not fully written to disk? that never happens if the systemd-unit for the replication instance has "ExecStopPost=/usr/bin/sleep 1" and waits a while my only explaination is that mysqld returns after the SIGTERM from systemd before all data are completly written in some racy situations and so rsynced incompletly to the datadir of the other instance _________________________________________________________ #!/bin/bash systemctl stop replication.service systemctl stop mysqld.service rsync $RSYNC_PARAMS /mysql_replication/ /mysql_data/ systemctl start replication.service systemctl start mysqld.service _________________________________________________________ [Unit] Description=MariaDB Replication [Service] Type=simple PIDFile=/run/mysqld/mysqld_replication.pid ExecStart=/usr/libexec/mysqld --defaults-file=/etc/my-replication.cnf --pid-file=/run/mysqld/mysqld_replication.pid --socket=/var/lib/mysql/mysql_replication.sock --open-files-limit=30000 --basedir=/usr --user=mysql Environment="LANG=en_GB.UTF-8" Restart=always RestartSec=1 _________________________________________________________ 140724 12:22:59 [Note] /usr/libexec/mysqld: Shutdown complete 140724 12:23:01 [Note] Plugin 'InnoDB' is disabled. Cannot find checkpoint record at LSN (1,0x35767) 140724 12:23:01 [ERROR] mysqld: Aria recovery failed. Please run aria_chk -r on all Aria tables and delete all aria_log.######## files 140724 12:23:01 [ERROR] Plugin 'Aria' init function returned error. 140724 12:23:01 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed. 140724 12:23:01 [Note] Plugin 'FEDERATED' is disabled. 140724 12:23:01 [Note] Plugin 'FEEDBACK' is disabled. 140724 12:23:01 [ERROR] Aria engine is not enabled or did not start. The Aria engine must be enabled to continue as mysqld was configured with --with-aria-tmp-tables 140724 12:23:01 [ERROR] Aborting 140724 12:23:01 [Note] /usr/libexec/mysqld: Shutdown complete 140724 12:23:03 [Note] Plugin 'InnoDB' is disabled. Cannot find checkpoint record at LSN (1,0x35767)

1 0

[Maria-discuss] New Question: ST_Transform missing?
by AskMonty KB 24 Jul '14

24 Jul '14

Hello, A new question has been asked in "MariaDB community" by ronna: -------------------------------- Hi there, I just started using MariaDB. Mainly because of the support for GIS. But now I am trying to reproject some geometric objects and I find out there is no ST_Transform function? How can this be? I need it ;-) Is there another function for it? Or will there be support for it soon? I am now using 10.0.11 Thanks for the reply. Ron. -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/st_transform-missing/

1 0

[Maria-discuss] MariaDB 10.1 as drop in replacement for mysql55-server-5.5.38-1.ius.el5
by Eero Volotinen 23 Jul '14

23 Jul '14

Hi List, Is it possible to use MariaDB 10.1 as drop-in replacement for mysql55-server-5.5.38-1.ius.el5? like: rpm -e mysql55.. files and then just use yum to install mariadb without reinstalling databases content? br, -- Eero

1 0

[Maria-discuss] Aria engine
by Roberto Spadim 22 Jul '14

22 Jul '14

Hi guys Why aria engine is a beta/alpha engine? -- Roberto Spadim SPAEmpresarial Eng. Automação e Controle

2 4

[Maria-discuss] Galera cluster with asynchronous slave
by Johnny Antonsen 21 Jul '14

21 Jul '14

Hi! First off let show you what we are trying to achieve, as a picture says more than a thousand words. galera I'm currently working on a high-availability project where we want to use MariaDB 10 and Galera as the backend. Running this system as it is with Haproxy and keepalived works great. We are able to write to the VIP that is being moved between each node and haproxy takes care of redirecting the server with least connections. The problem comes when we want to do a standard master/slave replication from the cluster to an external slave. The slave is set up to connect to the VIP (or I have also been testing with connecting directly to the haproxied ip), and Using_gtid is set to Slave_pos. However, after some time, once the connection changes to a different node through haproxy, the following error occurs: Got fatal error 1236 from master when reading data from binary log: 'Error: connecting slave requested to start from GTID 3-1-422, which is not in the master's binlog' And the Slave_IO_State shows that it's no longer in sync. I have run SELECT @@GLOBAL.gtid_slave_pos; to check what the current GTID for each node is, and they all return: 1-1-2145, however, sometimes if I add a lot of data, that value is different on some nodes, which is why I think the slave gets confused. On the slave, when activating using_gtid=slave_pos, the following gtid_IO_pos appear: 1-1-2464,2-3-420,3-1-422 From what I have read, this should be somewhat correct, as the first value is the server id. However, in the config I have specified that node 1 has server id 1, node 2 has id 2 and so on, and that the same goes for gtid_domain_id. Is this the correct setup or do the nodes need to have the same server-id or gtid_domain_id? Surely there must be a good way to solve this? Is the system not built to handle an asynchronous slave replicating from one random node? Hope I can get some good feedback on this. Just as a side-note, I'm fairly new to mariadb and galera cluster, so be gentle :) With best regards Johnny Antonsen

3 5