Merge lp://qastaging/~patrick-crews/drizzle/randgen_rpl_crash_tests into lp://qastaging/~drizzle-trunk/drizzle/development
Status: | Merged |
---|---|
Approved by: | Brian Aker |
Approved revision: | 2250 |
Merged at revision: | 2252 |
Proposed branch: | lp://qastaging/~patrick-crews/drizzle/randgen_rpl_crash_tests |
Merge into: | lp://qastaging/~drizzle-trunk/drizzle/development |
Diff against target: |
75 lines (+12/-2) 5 files modified
tests/lib/server_mgmt/server.py (+1/-0) tests/lib/server_mgmt/server_management.py (+6/-0) tests/lib/test_mgmt/test_execution.py (+3/-0) tests/randgen_tests/innodb_trx_log/multi_thread1_crash_recover.cnf (+1/-1) tests/randgen_tests/slave_plugin/multi_thread1_crash_recover.cnf (+1/-1) |
To merge this branch: | bzr merge lp://qastaging/~patrick-crews/drizzle/randgen_rpl_crash_tests |
Related bugs: | |
Related blueprints: |
Replication - Testing
(High)
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Drizzle Merge Team | Pending | ||
Review via email: mp+54774@code.qastaging.launchpad.net |
Description of the change
Added some code + randgen_test .cnf files so we now have crash tests for the innodb rpl log and the slave plugin (not yet hacked up for the file-based log)
slave_plugin.
innodb_
We kill the server mid-randgen run (while multiple-threads are executing queries), we then restart the server and compare master and slave states (for slave plugin)
for the innodb log, we restart the master, then dump the sql from the log, populate a validation server, then compare master and slave contents.
These tests help us know that in the event of a crash the log will reflect the state of the data and the slave accurately reflects the master's state : )