Testing Tasks for 1.3 release (MXS-319)

[MXS-208] Load Test MaxScale 1.3 Created: 2015-06-17  Updated: 2016-02-08  Resolved: 2016-02-08

Status: Closed
Project: MariaDB MaxScale
Component/s: test
Affects Version/s: None
Fix Version/s: 1.3.0

Type: Sub-Task Priority: Major
Reporter: Dipti Joshi (Inactive) Assignee: Timofey Turenko
Resolution: Fixed Votes: 0
Labels: None

Sprint: 1.4.0-1, 1.4.0-2

 Description   

Run Heavy Traffic against MaxScale
(1) Overnight(12 hours) - collect log files, any crash files/backtrace - provide it to development for diagnosis
(2) 24 hours - collect error log files, any crash files/backtrace - provide it to development for diagnosis
(3) 7 days - collect error log files, any crash files/backtrace - provide it to development for diagnosis

The above set should be tested for (a) read connect routing (b) readwrite splitter (c) schema routing (d) with filters (e) without filters

tturenko Please estimate resources needed for this task - how many virtual machines/servers in parallel. These tests need to run continuously in parallel to our functional and regression testing.

 Comments   
Comment by Timofey Turenko [ 2015-06-17 ]

It can be done with existing setup. I consider just constantly running test (do not interrupt after 12 or 24 hours).
We need to define the list of filters and their sequence in the configuration (testing of all combinations can eat a lot of resources and do not give a good result).

Such testing can be started after merging at least reload config branch and clarification of binlog status.

Comment by Dipti Joshi (Inactive) [ 2015-08-04 ]

tturenko Did we do this testing in 1.2 ? What were the results ? If this task is complete - can this item be closed now ?

Comment by Timofey Turenko [ 2016-02-08 ]

long_sysbench test added, it runs until stopped by user, logs are copied and published periodically

Generated at Thu Feb 08 03:57:35 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.