summaryrefslogtreecommitdiff
path: root/mysql-test/suite/rpl
Commit message (Collapse)AuthorAgeFilesLines
* 5.5-mergeSergei Golubchik2011-07-02616-5553/+5299
|\
| * Increase test timeout for rpl.rpl_typeconvBjorn Munch2011-05-251-0/+1
| | | | | | | | | | | | Not for test itself but because it procuces large number of warnings, and this may take >90s to filter on slow boxes
| * Replaced all bug numbers with Oracle bugDB numbersAnitha Gopi2011-05-231-3/+3
| |
| * BUG#11746302Luis Soares2011-05-192-22/+32
| |\ | | | | | | | | | | | | | | | | | | | | | | | | | | | Manual merged mysql-5.1-gca into latest mysql-5.5. Conflicts ========= Text conflict in mysql-test/suite/rpl/r/rpl_relayspace.result Text conflict in mysql-test/suite/rpl/t/rpl_relayspace.test
| | * BUG#11746302: 25228: RPL_RELAYSPACE.TEST FAILS ON POWERMACG5, Luis Soares2011-05-192-20/+32
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | VM-WIN2003-32-A, SLES10-IA64-A The test case waits for master_pos_wait not to timeout, which means that the deadlock between SQL and IO threads was succesfully and automatically dealt with. However, very rarely, master_pos_wait reports a timeout. This happens because the time set for master_pos_wait to wait was too small (6 seconds). On slow test env this could be a problem. We fix this by setting the timeout inline with the one used in sync_slave_with_master (300 seconds). In addition we refactored the test case and refined some comments.
| * | auto-mergeTatjana Azundris Nuernberg2011-05-1233-55/+93
| |\ \
| | * \ BUG#12416700Luis Soares2011-05-112-5/+3
| | |\ \ | | | | | | | | | | | | | | | Automerged bzr bundle from bug report into latest mysql-5.5.
| | | * | BUG#12416700: RPL_SHOW_SLAVE_HOSTS FAILS SPORADICALLY (TIMEOUT Luis Soares2011-05-102-5/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | IN WAIT_SHOW_CONDITION) There was a typo in the name of one of the parameters to the include file wait_show_condition. The parameter name was being set to "connection" instead of "condition". We fix this typo, improve one instruction in the test case and deploy parameter checks inside wait_show_condition.inc.
| | * | | Bug#12384993 EXTRA/RPL_TEST/CHECK_TYPE.INC NEED SUPPORT FOR SPECIFIC ENGINEMagnus Blåudd2011-05-112-2/+2
| | |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - add support for choosing the engine of test table(t1) with $engine_type - add primary key to the test table(t1) to support replication of BLOB/TEXT (also with ENGINE=ndb) - change the suppression since the warning printed to error log now says "Column 1"
| | * | BUG#11762616: BUG#55229: 'POSTION'Luis Soares2011-05-063-8/+8
| | |\ \ | | | |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Manual merge from mysql-5.1 into mysql-5.5. Conflicts ========= Text conflict in mysql-test/suite/rpl/t/rpl_row_until.test Text conflict in sql/handler.h Text conflict in storage/archive/ha_archive.cc
| | | * BUG#11762616: BUG#55229: 'POSTION' Luis Soares2011-05-063-7/+7
| | | | | | | | | | | | | | | | | | | | | | | | Fix for all "postion" in Oracle files (s/postion/position). Updated the copyright notices where needed.
| | * | autocommit 5.1->5.5Serge Kozlov2011-04-142-0/+34
| | |\ \ | | | |/
| | | * WL#5867, reorganize test cases of bugs suiteSerge Kozlov2011-04-142-0/+34
| | | |
| | | * merge from 5.1 mainBjorn Munch2011-03-316-11/+27
| | | |\
| | | | * mergeGeorgi Kodinov2011-03-253-9/+23
| | | | |\
| | * | | \ merge from 5.5 mainBjorn Munch2011-03-317-11/+28
| | |\ \ \ \
| | | * | | | Fixing test case that is sporadically failing.Alfranio Correia2011-03-251-0/+1
| | | | | | |
| | | * | | | mergeGeorgi Kodinov2011-03-253-9/+23
| | | |\ \ \ \
| | | | * \ \ \ BUG#11766865: Automerged mysql-5.1 into mysql-5.5.Luis Soares2011-03-253-9/+23
| | | | |\ \ \ \ | | | | | | |_|/ | | | | | |/| |
| | | | | * | | Automerging bzr bundle attached to bug report into latest mysql-5.1.Luis Soares2011-03-243-9/+23
| | | | | |\ \ \
| | | | | | * | | BUG#11766865: 60091: RBR + NO PK + UPDATE NULL VALUE --> SLAVE BREAK WITH ↵Luis Soares2011-03-243-9/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ERROR HA_ERR_END_OF_ The slave was not able to find the correct row in the innodb table, because the row fetched from the innodb table would not match the before image. This happened because the (don't care) bytes in the NULLed fields would change once the row was stored in the storage engine (from zero to the default value). This would make bulk memory comparison (using memcmp) to fail. We fix this by taking a preventing measure and avoiding memcmp for tables that contain nullable fields. Therefore, we protect the slave search routine from engines that return arbitrary values for don't care bytes (in the nulled fields). Instead, the slave thread will only check null_bits and those fields that are not set to NULL when comparing the before image against the storage engine row. mysql-test/extra/rpl_tests/rpl_record_compare.test: Added test case to the include file so that this is tested with more than one engine. mysql-test/suite/rpl/r/rpl_row_rec_comp_innodb.result: Result update. mysql-test/suite/rpl/r/rpl_row_rec_comp_myisam.result: Result update. mysql-test/suite/rpl/t/rpl_row_rec_comp_myisam.test: Moved the include file last, so that the result from BUG#11766865 is not intermixed with the result for BUG#11760454. sql/log_event.cc: Skips memory comparison if the table has nullable columns and compares only non-nulled fields in the field comparison loop.
| | | * | | | | | Merged bug #11766769 to 5.5. Georgi Kodinov2011-03-253-2/+4
| | | |\ \ \ \ \ \ | | | | |/ / / / / | | | |/| | | | / | | | | | |_|_|/ | | | | |/| | | Added back the specific warning number.
| | | | * | | | Bug #11766769: 59959: SMALL VALUES OF --MAX-ALLOWED-PACKET Georgi Kodinov2011-03-253-2/+4
| | | | |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ARE NOT BEING HONORED max_allowed_packet works in conjunction with net_buffer_length. max_allowed_packet is an upper bound of net_buffer_length. So it doesn't make sense to set the upper limit lower than the value. Added a warning (using ER_UNKNOWN_ERRROR and a specific message) when this is done (in the log at startup and when setting either max_allowed_packet or the net_buffer_length variables) Added a test case. Fixed several tests that broke the above rule.
| | * | | | | Small followup fix after MTR warning cleanupBjorn Munch2011-03-312-10/+0
| | |\ \ \ \ \ | | | | |_|_|/ | | | |/| | |
| | | * | | | Small followup fix after MTR warning cleanupBjorn Munch2011-03-312-24/+0
| | | | | | |
| | * | | | | mtr: cleaned up some superfluos global warning suppressionsBjorn Munch2011-03-302-6/+6
| | |\ \ \ \ \ | | | |/ / / / | | | | / / / | | | |/ / / | | |/| | |
| | | * | | mtr: cleaned up some superfluos global warning suppressionsBjorn Munch2011-03-302-18/+18
| | | |/ /
| | * | | merge from 5.5 mainBjorn Munch2011-03-2217-33/+49
| | |\ \ \
| | | * | | Bug # 11766011: mysql.user.authentication_string column causes Georgi Kodinov2011-03-182-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | configuration wizard to fail Made the fields mysql.user.plugin and mysql.user.authentication_string nullable to conform with some older clients doing inserts instead of using the commands.
| | | * | | merge mysql-5.5 (local) --> mysql-5.5Alfranio Correia2011-03-1712-17/+17
| | | |\ \ \
| | | | * | | BUG#11877568 - RPL_SEMI_SYNC FAILS IN PBAlfranio Correia2011-03-1612-17/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently, rpl_semi_sync is failing in PB due to the warning message: "Slave SQL: slave SQL thread is being stopped in the middle of " "applying of a group having updated a non-transaction table; " "waiting for the group completion ..." The problem started happening after the fix for BUG#11762407 what was automatically suppressing some warning messages. To fix the current issue, we suppress the aforementioned warning message and exploit the opportunity to make the sentence clearer.
| | * | | | | upmerge 11762804Bjorn Munch2011-03-151-0/+1
| | |\ \ \ \ \
| * | \ \ \ \ \ auto-mergeTatjana Azundris Nuernberg2011-05-122-0/+78
| |\ \ \ \ \ \ \ | | |_|_|/ / / / | |/| | | | | |
| | * | | | | | Bug#11902767/Bug#60580: Statement improperly replicated crashes slave SQL threadTatjana Azundris Nuernberg2011-05-122-0/+78
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If LOAD DATA INFILE featured a SET clause, the name=value pairs would be regenerated using item::print. Unfortunately, that code is mostly optimized for EXPLAIN EXTENDED output and such, and can not be relied on to return valid SQL. We now name each value its original, user-supplied form and use that to create LOAD DATA INFILE statements for statement-based replication. mysql-test/suite/binlog/r/binlog_stm_mix_innodb_myisam.result: minor change in syntactic sugar mysql-test/suite/rpl/r/rpl_loaddatalocal.result: add test case mysql-test/suite/rpl/t/rpl_loaddatalocal.test: add test case sql/sql_load.cc: Do not try to item::print values in LOAD DATA INFILE's SET clause; they might not even be valid SQL at this point. Use our saved version instead. sql/sql_yacc.yy: If LOAD DATA INFILE has SET name=val clauses, tag the individual val-parts with the user's version so we can later replicate that, rather than the smashed pieces we'd get from item::print once the optimizer's through with our poor values.
| * | | | | | | Fix for BUG#11868903 (BUG#59717).Luis Soares2011-03-162-2/+5
| |\ \ \ \ \ \ \ | | |_|_|_|/ / / | |/| | | | / / | | | |_|_|/ / | | |/| | | | Automerge: mysql-5.1 --> mysql-5.5
| | * | | | | Fix for BUG#11868903 (BUG#59717)Luis Soares2011-03-162-2/+5
| | | |_|/ / | | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There is a race between two threads: user thread and the dump thread. The former sets a debug instruction that makes the latter wait before processing an Xid event. There can be cases that the dump thread has not yet processed the previous Xid event, causing it to wait one Xid event too soon, thus causing sync_slave_with_master never to resume. We fix this by moving the instructions that set the debug variable after calling sync_slave_with_master.
| * | | | | BUG#11872422: rpl_slave_load_remove_tmpfile fails sporadically in pb2Sven Sandberg2011-03-153-12/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: the test failed because errors were found in the error log. The test case contains suppressions for an old version of the error message, but the format of the error message has changed without updating the suppression. Fix: Update the suppression. Also small fixes to improve the test. mysql-test/suite/rpl/r/rpl_slave_load_remove_tmpfile.result: update result file mysql-test/suite/rpl/t/rpl_slave_load_remove_tmpfile-slave.opt: Use variables instead of .opt files to avoid server restarts. mysql-test/suite/rpl/t/rpl_slave_load_remove_tmpfile.test: 1. To fix the bug, we update the regular expression in mtr.add_suppression so that it matches the real error text. 2. Use wait_for_slave_sql_error.inc when we wait for an error. This makes the test easier to understand and will produce better debug info if the test fails. 3. Use server variables instead of command line options to set the @@GLOBAL.DEBUG variable. This avoids server restarts when running the test suite. 4. Clarify the comment at the top of the file and add bug reference.
| * | | | | Add warning suppression to test rpl.rpl_slave_load_remove_tmpfileBjorn Munch2011-03-152-0/+2
| | |_|/ / | |/| | |
| * | | | 11762407 follow-up fixes to a few testsBjorn Munch2011-02-244-0/+4
| | | | |
| * | | | merge from 5.5 mainBjorn Munch2011-02-246-24/+31
| |\ \ \ \
| | * | | | Disable this test when running 'mtr --mem'Tor Didriksen2011-02-171-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | With --mem if fails with +UNEXPECTED ERROR NUMBER: 1290 In var/log/mysqld.2.err we have: [ERROR] LOAD DATA INFILE in the slave SQL Thread can only read from --slave-load-tmpdir. Please, report a bug. [ERROR] Slave SQL: Error 'The MySQL server is running with the --slave-load-tmpdir option so it cannot execute this statement' on query. Default database: 'test'. Query: 'LOAD DATA INFILE '../../tmp/SQL_LOAD-2-1-1.data' INTO TABLE `t1` FIELDS TERMINATED BY '\t' ENCLOSED BY '' ESCAPED BY '\\' LINES TERMINATED BY '\n' (`a`, `b`)', Error_code: 1290 getcwd() in the server yields something like: /dev/shm/var_auto_iv5Q/mysqld.2/data
| | * | | | BUG#11754075: BUG#45621: A FEW TEST FILES ARE DISABLED DUE TO WL#4284Luis Soares2011-02-153-15/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Backporting the patch from BUG#11753506 into mysql-5.5 as it is already in mysql-trunk but not in mysql-5.5.
| | * | | | BUG#11754075: BUG#45621: A FEW TEST FILES ARE DISABLED DUE TO WL#4284Luis Soares2011-02-153-9/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Backporting the patch from BUG#11753489 into mysql-5.5 as it is already in mysql-trunk but not in mysql-5.5.
| * | | | | Upmerge 11762407 (54999) with additionsBjorn Munch2011-02-2363-16/+115
| |\ \ \ \ \ | | |/ / / / | |/| / / / | | |/ / /
| | * | | Bug #11762407 54999: MTR GLOBAL SUPPRESSION HIDES SQL THREAD EXECUTION ↵Bjorn Munch2011-02-2353-9/+96
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | UNEXPECTED ERRORS Removed the global suppression, added lots of local ones to affected tests Re-commit, now kept "Slave SQL" at start of patterns.
| * | | | Merge from mysql-5.5.9-releaseJonathan Perkin2011-02-082-2/+39
| |\ \ \ \
| | * | | | BUG#59267 LOAD DATA LOCAL INFILE not executed on slave with SBRAlfranio Correia2011-01-122-2/+39
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | On windows, an #endif in a wrong place was causing an early return from mysql_load and thus the LOAD DATA LOCAL was not executed. This problem was fixed by moving the #endif to the right place. The following code was missing if ((stat_info.st_mode & S_IFIFO) == S_IFIFO) is_fifo = 1; which is required to properly configure and read from the IO_CACHE when a named pipe is used. So it was re-introduced before the #endif.
| * | | | | Bug#43828, Bug#59494. Serge Kozlov2011-02-042-15/+34
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | After introducing new way of initialization of replication the setting different heartbeat periods for slaves was missed. Added asserts
| * | | | | BUG#59147: automerge mysql-5.1 into mysql-5.5.Luis Soares2011-02-042-4/+4
| |\ \ \ \ \ | | | |/ / / | | |/| | |
| | * | | | BUG#59147: rpl_circular_for_4_hosts fails sporadicallyLuis Soares2011-02-032-4/+4
| | | |_|/ | | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There is one part of the test case that needs to break and re-establish the circular topology. For this the test stops the slave threads on a couple of servers and restarts them with START SLAVE. However, no check is done on the status of the IO or SQL threads before proceeding with the subsequent commands. Because rpl_only_running_threads is set to 1 this can lead to silently not syncing all slave threads as expected, ultimately resulting in unexpected results (and consequently on a failing test run). We fix this by replacing the START SLAVE instructions with calls to --source include/start_slave.inc, which will wait for the slave threads to be running (show 'Yes' in Slave_IO|SQL_Running fields of SHOW SLAVE STATUS) before proceeding. Additionally, we change rpl_sync.inc to make the IO thread report that it is running when its running status is any other than 'No'.
View Lorry Controller Status