The following chapter includes a number of suggested functional tests that can be performed following installation in a Testing/POC environment
For a test to be successful, normal operations should be restored after every test. The default Primary server should regain Primary role with all replicators and data sources ONLINE
The tests are split into the following categories:
A PDF version of these tests can be downloaded by clicking here
Failover Test 1 - Administrator uses Tungsten to promote new Primary
Scenario |
shell> |
Expectation |
|
Failover Test 2 – Manually kill the Primary database process
Scenario |
shell> |
Expectation |
|
Failover Test 3 – Remove power from the Primary database server
Scenario |
Pull the power plug on the Primary server or run a restart command if that is not an option. |
Expectation |
|
Failover Test 4 – Manually kill a Replica database process
Backup Test 1 – Take a backup of a Replica and restore it to the same server
Scenario |
shell> |
Expectation |
|
Backup Test 2 – Restore the backup to another server
Scenario |
shell> |
Expectation |
|
Backup Test 3 – Take a backup of the Primary and restore to a Replica
Scenario |
shell> |
Expectation |
|
Connectivity Test 1 – Connect to the connector and verify Primary host
Scenario |
shell>
|
Expectation |
|
Connectivity Test 2 – Verify access to Replicas
This test is only required if read/write splitting has been enabled. It should be run from a connector running on a server other than the Primary.
Scenario |
shell>
|
Expectation |
|
Connectivity Test 3 – Verify access to the Primary before and after a switch
Performance Test 1 – Run a load test against the cluster
Scenario |
Run load tests of some variety against the cluster to ensure the Connector and Replicator properly handle the load. Recommended load test tools are:
|
Expectation |
Solution can handle 1TB of data with a minimum of 24k reads per minute and 1k writes per minute, over three tests.
|
Replicator Testing
Scenario |
Evaluate system responsiveness in conjunction with performance tests (above). This is not a test of network speed |
Expectation |
Quick replication latency betweens regions (<100ms greater than the current ping latency) |
Network Partition Testing
Scenario |
Simulate a partitioned network (for example, by modifying security group rules in AWS), and continue to do reads and writes on multiple clusters for 30 minutes. |
Expectation |
After resolving the partition, clusters should resync. |
Scenario |
Create a similar network partition, and write the same record on both sides of the partition |
Expectation |
After resolving the partition, the replicators on both sides should report errors. Demonstrate possible resolutions:
|