Stop MaxScale before fixing replication

Before the state of the backend servers is checked, MaxScale needs to be
stopped to prevent the automated failover from interfering in the start-up
process.
This commit is contained in:
Markus Mäkelä 2018-07-05 21:03:57 +03:00
parent 5c610503ba
commit cb05199bac
No known key found for this signature in database
GPG Key ID: 72D48FCE664F7B19

View File

@ -238,6 +238,15 @@ TestConnections::TestConnections(int argc, char *argv[]):
maxscales->use_ipv6 = use_ipv6;
maxscales->ssl = ssl;
// Stop MaxScale to prevent it from interfering with the replication setup process
if (!maxscale::manual_debug)
{
for (int i = 0; i < maxscales->N; i++)
{
maxscales->stop(i);
}
}
if (maxscale::required_repl_version.length())
{
int ver_repl_required = get_int_version(maxscale::required_repl_version);
@ -643,11 +652,6 @@ void TestConnections::init_maxscale(int m)
{
const char * template_name = get_template_name(test_name);
if (!maxscale::manual_debug)
{
stop_maxscale(m);
}
process_template(m, template_name, maxscales->access_homedir[m]);
maxscales->ssh_node_f(m, true,
"cp maxscale.cnf %s;rm -rf %s/certs;mkdir -m a+wrx %s/certs;",