[MXS-1563] Test: Switchover under harder conditions Created: 2017-12-04  Updated: 2018-01-16  Resolved: 2018-01-16

Status: Closed
Project: MariaDB MaxScale
Component/s: mariadbmon
Affects Version/s: None
Fix Version/s: 2.2.2

Type: Task Priority: Major
Reporter: Johan Wikman Assignee: Johan Wikman
Resolution: Fixed Votes: 0
Labels: None

Epic Link: Failover/Switchover/Rejoin Testing
Sprint: 2017-47, 2017-48, 2017-49

 Description   
  • Create a master-slave replication setup.
  • Generate some traffic and if possible arrange things so that slaves will lag behind the master.
  • Start a read-write transaction.
  • Initiate switchover to some slave.
  • Check that any new update in the previously started transaction fails.
  • Check that it no longer is possible to initiate new writes through MaxScale.
  • Wait for the switchover operation to finish (the switchover mechanism should wait for the chosen slave to catch up, and then promote it to master).
  • Verify that the specified slave is now the new master and that the old master is a slave.

Generated at Thu Feb 08 04:07:42 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.