|
Was this task about the MTR test suite?
It would be a very tempting idea, but is it actually possible?
MTR configures the server to run on a certain port and uses the generated config both for the server(s) and the clients. Would it instead need to configure the server run on one port, but the clients connect to another?
Also, MTR doesn't just send queries on a single server, it can run multiple servers, restart them between or during the tests, tamper with data, use both socket and ports. Would it still be possible, and would MaxScale as a middleman be able to keep up with this?
|
|
Yes, it was about the MTR test suite. However, I suppose it in practice might have to be a subset of the MTR test suite. Configuring the server to run on one port and clients to connect to another would allow, as far as I can tell, allow MaxScale to be inserted in between. MaxScale should be configured for read-write-splitting (as that stresses more), but then be configured with just a single server. Restarting and manipulating the server behind MaxScale's back should work just fine.
|