- developers - lists.mariadb.org

[Maria-developers] MDEV-7502 Automatic provisioning of slave - error reporting
by Martin Kaluznik 26 Jun '15

26 Jun '15

Hello Kristian, with general idea working (sending of database / table structures + table data), my next plan is to improve / introduce error handling in existing code along with error handling on slave side (ddl events not from provisioning, ignore errors when updating not yet existing rows, ...). What are general guidelines for introduction of new error codes? Is there anything else I need to do except adding it to /sql/share/errmsg-utf8.txt ? I would create only one new error code - ER_PROVISIONING_FAILED - and place specific messages inside formatted text - same way as ER_MASTER_FATAL_ERROR_READING_BINLOG works. It doesn't go well with translations, but... you can decide. Maybe create different error codes at least for errors, where we are expecting user to fix them - table without index, statement mode. Also, how to tell slave from master that provisioning finished? Is introduction of new error code ER_PROVISIONING_DONE acceptable solution? The error itself would never produce error message in logs. Alternatively I can reuse / create similar event to Stop_log_event, note - provisioning is completed after SQL thread processes whole relay log, not when IO thread receives this event, so even reuse would require additional code. And side question, is there any log event other than Query_log_event which can produce ddl statement? Martin

2 1

Re: [Maria-developers] [Commits] 2cf747e: MDEV-8219: enforce_storage_engine cannot be set globally
by Sergei Golubchik 26 Jun '15

26 Jun '15

Hi, Jan! On Jun 26, Jan Lindström wrote: > revision-id: 2cf747e885603122b2adbefc131516cd12dc953c > parent(s): d3b7eb7b99ef7dae79c20b5beb63acdfdf6d8046 > committer: Jan Lindström > branch nick: 10.1-bugs > timestamp: 2015-06-26 08:56:50 +0300 > message: > > MDEV-8219: enforce_storage_engine cannot be set globally > > Change session only variable enforce_storage_engine to be > session variable and make sure that also global value > is used if session variable is not set. Ok to push, thanks! Regards, Sergei

1 0

[Maria-developers] Please review: MDEV-7824 [Bug #68041] Zero date can be inserted in strict no-zero mode through a default value
by Alexander Barkov 25 Jun '15

25 Jun '15

Hi Sergei, Please review a patch for mdev-7824. It's based on a MySQL patch for http://bugs.mysql.com/bug.php?id=68041 and is a blocker for: MDEV-3929 Add full support for auto-initialized/updated timestamp and datetime Thanks.

2 9

[Maria-developers] MDEV-6877 - binlog_row_image implementation advice
by Vicențiu Ciorbaru 25 Jun '15

25 Jun '15

Hi Sergei! This past week I've done quite a bit of reading regarding the replication code and how the binlog is used by both mysqlbinlog and the slaves in order to do replication. I think I now have a good enough understanding of the flow of the code for both MySQL and MariaDB to actually start coding the feature into MariaDB. I do have a couple of unknowns still. I don't quite understand what's the use for the TABLE_MAP event. My intuition tells me its some sort of id we assign to a table name (test.t1 for example) that gets used afterwards in the binlog row events. We seem to be using a bitmap of columns that we want to log into the binlog. MySQL does extend the TABLE class to flip the bits according to the binlog_row_image variable. That seems like the first place to start with the addition. I could not find any other "hidden" logic that we use to choose how we log row operations in the binlog. What I would like to know is if there are any other pitfalls that I am supposed to watch out for, or if there is anything else I may be missing regarding the logging part. When it comes to actually doing the replication, I concluded that Log_event::do_apply_event is the place where we begin translating the event from the binlog to an SQL statement. Another concern that I have is how to test the implementation. Right now, I run the test, get the binlog file and print it with mysqlbinlog and see if the output is what I expect. Do we have something within mysql-test-run that automates this? Regards, Vicentiu

2 7

Re: [Maria-developers] [Commits] 9f00950: MDEV-7631 : Invalid WSREP_SST rows appear in mysqld-bin.index file
by Sergei Golubchik 25 Jun '15

25 Jun '15

Hi, Nirbhay! On Jun 24, Nirbhay Choubey wrote: > revision-id: 9f00950d2ad9be5533e66a5fa87a795a9574585f > parent(s): 0f4478105f5027ce589a0f08c6019d906d632029 > committer: Nirbhay Choubey > branch nick: 10.0-galera.b7631 > timestamp: 2015-06-24 23:25:22 -0400 > message: > > MDEV-7631 : Invalid WSREP_SST rows appear in mysqld-bin.index file > > Try not to release 0 (STDIN_FILENO) file descriptor as it can > incorrectly get reused by streams opened later. This really deserved a more descriptive comment. There's nothing wrong when fd 0 is reused by other streams. The problem was that because of a bug (arguably) in old glibc in CentOS6/RHEL6 freopen remapped stdout/stderr to fd 0 and 1. Which is, on itself, is not a problem either, but when mysqld forked other processes, these children had no access to stdout and stderr. it's too late to recommit now and, luckily, MDEV-7631 has all the information about this issue. Regards, Sergei

1 0

Re: [Maria-developers] [Commits] aff5606: Add close-on-exec flag to open(), socket(), accept() & fopen().
by Sergei Golubchik 24 Jun '15

24 Jun '15

Hi, Nirbhay! On Jun 24, Nirbhay Choubey wrote: > revision-id: aff560696cac5e081d19f4460ccd9c906ddc9d84 > parent(s): 70714d3597ec9ffa742cc9e173d4ad32f294cc51 > committer: Nirbhay Choubey > branch nick: 10.0-galera.b7631 > timestamp: 2015-06-24 11:58:11 -0400 > message: > > Add close-on-exec flag to open(), socket(), accept() & fopen(). > > @@ -1026,7 +1026,8 @@ static inline void inline_mysql_socket_register( > (&state, socket_listen.m_psi, PSI_SOCKET_CONNECT, (size_t)0, src_file, src_line); > > /* Instrumented code */ > - socket_accept.fd= accept(socket_listen.fd, addr, &addr_length); > + socket_accept.fd= accept4(socket_listen.fd, addr, &addr_length, > + SOCK_CLOEXEC); Note that, according to the manpage, "accept4() is a nonstandard Linux extension". It needs a configure-time check and ifdef. Alternatively, don't use it at all, do fcntl(FD_CLOEXEC) instead. > /* Instrumentation end */ > if (locker != NULL) > @@ -1036,7 +1037,8 @@ static inline void inline_mysql_socket_register( > #endif > { > /* Non instrumented code */ > - socket_accept.fd= accept(socket_listen.fd, addr, &addr_length); > + socket_accept.fd= accept4(socket_listen.fd, addr, &addr_length, > + SOCK_CLOEXEC); > } Regards, Sergei

2 1

Re: [Maria-developers] [Commits] 99ca8b9: MDEV-8219: enforce_storage_engine cannot be set globally
by Sergei Golubchik 24 Jun '15

24 Jun '15

Hi, Jan! On Jun 23, Jan Lindström wrote: > revision-id: 99ca8b9ea8ee1b756fbf1edc567f6d06c9cf63fd > parent(s): d3b7eb7b99ef7dae79c20b5beb63acdfdf6d8046 > committer: Jan Lindström > branch nick: 10.1-bugs > timestamp: 2015-06-23 13:14:46 +0300 > message: > > MDEV-8219: enforce_storage_engine cannot be set globally > > Change session only variable enforce_storage_engine to be > session variable and make sure that also global value > is used if session variable is not set. > > diff --git a/mysql-test/suite/sys_vars/r/sysvars_innodb.result b/mysql-test/suite/sys_vars/r/sysvars_innodb.result > index 927cd05..1c59391 100644 > --- a/mysql-test/suite/sys_vars/r/sysvars_innodb.result > +++ b/mysql-test/suite/sys_vars/r/sysvars_innodb.result > @@ -355,6 +355,20 @@ NUMERIC_BLOCK_SIZE 1048576 > ENUM_VALUE_LIST NULL > READ_ONLY YES > COMMAND_LINE_ARGUMENT REQUIRED > +VARIABLE_NAME INNODB_BUF_DUMP_STATUS_FREQUENCY > +SESSION_VALUE NULL > +GLOBAL_VALUE 0 > +GLOBAL_VALUE_ORIGIN COMPILE-TIME > +DEFAULT_VALUE 0 > +VARIABLE_SCOPE GLOBAL > +VARIABLE_TYPE BIGINT UNSIGNED > +VARIABLE_COMMENT A number between [0, 100] that tells how oftern buffer pool dump status in percentages should be printed. E.g. 10 means that buffer pool dump status is printed when every 10% of number of buffer pool pages are dumped. Default is 0 (only start and end status is printed). please, no unrelated changes. If you want to fix forgotten result files, do it in a separate commit. > +NUMERIC_MIN_VALUE 0 > +NUMERIC_MAX_VALUE 100 > +NUMERIC_BLOCK_SIZE 0 > +ENUM_VALUE_LIST NULL > +READ_ONLY NO > +COMMAND_LINE_ARGUMENT REQUIRED > VARIABLE_NAME INNODB_BUF_FLUSH_LIST_NOW > SESSION_VALUE NULL > GLOBAL_VALUE OFF > diff --git a/sql/sql_table.cc b/sql/sql_table.cc > index 954970d..f18e6a2 100644 > --- a/sql/sql_table.cc > +++ b/sql/sql_table.cc > @@ -9772,7 +9772,7 @@ static bool check_engine(THD *thd, const char *db_name, > DBUG_ENTER("check_engine"); > handlerton **new_engine= &create_info->db_type; > handlerton *req_engine= *new_engine; > - handlerton *enf_engine= thd->variables.enforced_table_plugin ? plugin_hton(thd->variables.enforced_table_plugin) : NULL; > + handlerton *enf_engine= thd->variables.enforced_table_plugin ? plugin_hton(thd->variables.enforced_table_plugin) : global_system_variables.enforced_table_plugin ? plugin_hton(global_system_variables.enforced_table_plugin) : NULL; Please, no. Global variable should not be used like that, it simply sets a default value for the session variable for new connections. The way you've done it now, one cannot disable enforced_table_plugin per session at all. > bool no_substitution= thd->variables.sql_mode & MODE_NO_ENGINE_SUBSTITUTION; > *new_engine= ha_checktype(thd, req_engine, no_substitution); Regards, Sergei

1 0

[Maria-developers] GSoc2015
by Diwas Joshi 24 Jun '15

24 Jun '15

hii, please find a patch for MDEV-8343 <https://mariadb.atlassian.net/browse/MDEV-8343> attached to this mail. I have also included a test case in the patch. regards Diwas Joshi

2 2

[Maria-developers] Can't find messagefile '/usr/share/mysql/errmsg.sys'
by Sylvain Raybaud 24 Jun '15

24 Jun '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I built mariadb galera cluster 10.0.17 from source. Starting it with mysql_safe fails with: Can't find messagefile '/usr/share/mysql/errmsg.sys' This file does not exist indeed. It seems to not exist at all in mariadb-galera-10.0.17.tar.gz. Is it supposed to be installed separately? Am I missing something? Regards, - -- Sylvain Raybaud www.green-communications.fr -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJVeAYZAAoJEEkkwl4JtJ9yvfoP/jTnvj7V1Ze+E7sFE7Rz4Hsm +4Ga8f9MKCr5VxBZky3wMb8EgWmfcWDHbKqu4httTMH2RS6CCv7aiBeRfrMHMW5I NHl+k9CPUrDs03n4Vg12G2M33IIRfdEBgYf2xZ3sp3kBJ07MUWZPvlVL6ch+Aybn oOVzQ1rbUpxrkX2gj4XZ/wtXmy8vN6s9L3jy+o5HU4JZJcFyp1IpCwCE0OneI81V EiHs8dbpsUstr/32TaQ7gCBN9Hb25i5aVwRCD7UXE6kFt6OD6ifv8mw5KfmdtjHc i/0OotnOOsfj7tgDXKoPOltauGdSADJm2VSp8/nsfd6MR2nxMGZcw/Xbhj5l4FkY jWZf7uRAiKsYlmZEaJlb0WZrCTGSe6pcO82hObhv/vD0O55gKCdOM2rAExRiuxFn IPAuKGAKhzegxXxmmBTQv09tjSY3WTNZfFbDKGDQe4EYmCJ0K14cq37gC+TYI+xb Jr9SI5WBAvVVrCvhRktloEf03jVqXMH3H03DBjxGDB9KRc3Vr6AGhQmg0ixC2ZHC uTbRcx+R5mEn40TVwzLEnsUfiV+0MuJ5YYM5brYYRmXRg4ipwTcts1byKTHpvy69 PrDF1mzStInfex2ntkmw7puX8CQ4uebCLzHWSPODDa1n66D1vaEYCbZV7hEg25dH ox0Iptm4REWGyxgNeQxB =0Ydk -----END PGP SIGNATURE-----

3 4

[Maria-developers] doubt about query cache and write locks
by Roberto Spadim 24 Jun '15

24 Jun '15

hi guys, i'm with a doubt when i execute LOCK TABLE xxx WRITE any query at query cache could be executed without locking (waiting for table lock state) shouldn't the lock table invalidade the table query cache when using a write lock? -- Roberto Spadim

2 2