- 19 Sep, 2013 1 commit
-
-
unknown authored
Add another test case.
-
- 17 Sep, 2013 2 commits
- 16 Sep, 2013 1 commit
-
-
unknown authored
Add a simple test case. Fix bugs found.
-
- 13 Sep, 2013 1 commit
-
-
unknown authored
Some after-review fixes.
-
- 12 Jul, 2013 3 commits
-
-
unknown authored
Move annotate-event stuff from Relay_log_info to rpl_group_info, to make it thread safe.
-
unknown authored
Remove Relay_log_info::group_info. (It is not thread safe).
-
unknown authored
Move the deferred event stuff from Relay_log_info to rpl_group_info to make it thread safe for parallel replication.
-
- 09 Jul, 2013 1 commit
-
-
unknown authored
Fix a number of failures in the test suite.
-
- 08 Jul, 2013 1 commit
-
-
unknown authored
Fix a bunch of issues found with locking, ordering, and non-thread-safe stuff in Relay_log_info. Now able to do a simple benchmark, showing 4.5 times speedup for applying a binlog with 10000 REPLACE statements.
-
- 04 Jul, 2013 3 commits
-
-
unknown authored
Impement options --binlog-commit-wait-count and --binlog-commit-wait-usec. These options permit the DBA to deliberately increase latency of an individual commit to get more transactions in each binlog group commit. This increases the opportunity for parallel replication on the slave, and can also decrease I/O load on the master. The options also make it easier to test the parallel replication with mysql-test-run.
-
unknown authored
Fix some bugs around waiting for worker threads to end during SQL slave stop. Free Log_event after parallel execution (still needs to be made thread-safe by using rpl_group_info rather than rli).
-
unknown authored
Wait for all worker threads to finish when stopping the SQL thread. (Only a basic wait; this still needs to be fixed to include timeout logic as in sql_slave_killed()).
-
- 03 Jul, 2013 2 commits
-
-
unknown authored
Pass down rpl_group_info * to remove one instance of non-threadsafe use of rli->group_info.
-
unknown authored
Hook in the wait-for-prior-commit logic (not really tested yet). Clean up some resource maintenance around rpl_group_info (may still be some smaller issues there though). Add a ToDo list at the top of rpl_parallel.cc
-
- 28 Jun, 2013 1 commit
-
-
unknown authored
First step of splitting out part of Relay_log_info, so that different event groups being applied in parallel can each use their own copy.
-
- 26 Jun, 2013 1 commit
-
-
unknown authored
Implement facility for the commit in one thread to wait for the commit of another to complete first. The wait is done in a way that does not hinder that a waiter and a waitee can group commit together with a single fsync() in both binlog and InnoDB. The wait is done efficiently with respect to locking. The patch was originally made to support TaoBao parallel replication with in-order commit; now it will be adapted to also be used for parallel replication of group-committed transactions. A waiter THD registers itself with a prior waitee THD. The waiter will then complete its commit at the earliest in the same group commit of the waitee (when using binlog). The wait can also be done explicitly by the waitee.
-
- 25 Jun, 2013 2 commits
- 24 Jun, 2013 1 commit
-
-
unknown authored
First very rough sketch. We spawn and retire a pool of slave threads. Test main.alias works, most likely not much else does.
-
- 08 Jun, 2013 1 commit
-
-
unknown authored
-
- 07 Jun, 2013 4 commits
-
-
unknown authored
Now whenever we reach the GTID point requested from the slave (when using GTID position to connect), we send a fake Gtid_list event. This event is used by the slave to know the current old-style position for MASTER_POS_WAIT(), and later the similar binlog position for MASTER_GTID_WAIT(). Without this fake event, if the slave is already fully up-to-date with the master, there may be no events sent at the given position for an indeterminate time.
-
unknown authored
If the mysql.gtid_slave_pos table is not available, we cannot load nor update the current GTID position persistently. This can happen eg. after an upgrade, before mysql_upgrade_db is run, or if the table is InnoDB and the server is restarted without the InnoDB storage engine enabled. Before, replication always failed to start if the table was unavailable. With this patch, we try to continue with old-style replication, after suitable complaints in the error log. In strict mode, or if slave is configured to use GTID, slave still refuses to start.
-
unknown authored
Now we give an error on attempts to set @@SESSION.gtid_domain_id or @@SESSION.gtid_seq_no when a transaction is active.
-
unknown authored
There was some old code that cleared the position in CHANGE MASTER, it was forgotten to be removed. In addition, add code that saves/restores the old-style position when we nuke the old relay logs as part of GTID slave start. Normally we will not use these, but it could be useful in case the GTID connect fails and user wants to go back to the old-style coordinates.
-
- 06 Jun, 2013 3 commits
-
-
Sergei Golubchik authored
-
Vladislav Vaintroub authored
-
Michael Widenius authored
mysql-test/include/wait_show_condition.inc: Print failing statement if timeout mysql-test/r/myisam-metadata.result: Updated DBUG_SYNC mysql-test/t/myisam-metadata.test: Updated DBUG_SYNC. Removed wait_show_condtion, as this is not needed when we use DBUG_SYNC This should fix timing issues with the test mysys/thr_mutex.c: Added comments sql/sql_acl.cc: atoi -> atoll() (Safety) storage/myisam/ha_myisam.cc: Send signal before mi_repair_by_sort.
-
- 05 Jun, 2013 2 commits
-
-
unknown authored
-
unknown authored
Fix problems related to reconnect. When we need to reconnect (ie. explict stop/start of just the IO thread by user, or automatic reconnect due to loosing network connection with the master), it is a bit complex to correctly resume at the right point without causing duplicate or missing events in the relay log. The previous code had multiple problems in this regard. With this patch, the problem is solved as follows. The IO thread keeps track (in memory) of which GTID was last queued to the relay log. If it needs to reconnect, it resumes at that GTID position. It also counts number of events received within the last, possibly partial, event group, and skips the same number of events after a reconnect, so that events already enqueued before the reconnect are not duplicated. (There is no need to keep any persistent state; whenever we restart slave threads after both of them being stopped (such as after server restart), we erase the relay logs and start over from the last GTID applied by SQL thread. But while the SQL thread is running, this patch is needed to get correct relay log).
-
- 03 Jun, 2013 1 commit
-
-
unknown authored
There were several cases where the slave GTID position was not loaded correctly before being used. This caused various failures such as corrupting the position at slave start and empty values of @@gtid_slave_pos and @@gtid_current_pos. Fixed by adding more checks for loaded position, and by always loading the position at server startup.
-
- 01 Jun, 2013 2 commits
-
-
Vladislav Vaintroub authored
-
Vladislav Vaintroub authored
Problem : libreadline.so was already present on the machine, however the cmake check NEW_READLINE_INTERFACE was unsuccessfull indicating, thus bundled library had to be used instead of system library. The problem was that the value for HAVE_HIST_ENTRY cmake variable was cached with incorrect value (1 on NetBSD). The fix is to change HAVE_HIST_ENTRY to 0 with CACHE FORCE, after switching to bundled readline.
-
- 30 May, 2013 1 commit
-
-
unknown authored
MDEV-4520: Assertion `0' fails in Query_cache::end_of_result on concurrent drop event and event executio Fix for embedded library, where thd->net.vio is not set which efficently switched off QC in emmbedded server for previous patch.
-
- 29 May, 2013 2 commits
-
-
unknown authored
Fix the error handling when access to the table mysql.gtid_slave_pos fails for whatever reason. Add some test cases.
-
unknown authored
MDEV-4485: Master did not allow slave to connect from the very start (empty GTID pos) if GTIDs from other multi_source master was present The idea in the code was to protect the user that tries to connect a slave to a master with completely different domains than what was intended. If none of the domains in the start position are present at all in the master binlog, we gave an error. However, this is a stupid idea. Because when a slave connects to a master to start replication from the very start of binlogs - such as when setting up new master->slave servers from scratch - there will be just this situation, the requested slave position is empty for all the domains in the master's binlog. So the code that gives this error is wrong, and the solution is simply to remove it.
-
- 28 May, 2013 3 commits
-
-
Sergei Golubchik authored
remove the workaround from cmake/os/FreeBSD.cmake
-
unknown authored
-
unknown authored
When @@GLOBAL.gtid_strict_mode=1, then certain operations result in error that would otherwise result in out-of-order binlog files between servers. GTID sequence numbers are now allocated independently per domain; this results in less/no holes in GTID sequences, increasing the likelyhood that diverging binlogs will be caught by the slave when GTID strict mode is enabled.
-
- 25 May, 2013 1 commit
-
-
unknown authored
-