Fixed - master node shouldn't be initialized as slave in single mode. #4011

pull/4031/head
Nikita Koksharov 3 years ago
parent e3b3c5b52e
commit cc4c5b25a0

@ -448,9 +448,12 @@ public class MasterSlaveEntry {
slaveDown(oldMaster.getClient().getAddr(), FreezeReason.MANAGER); slaveDown(oldMaster.getClient().getAddr(), FreezeReason.MANAGER);
// check if at least one slave is available, use master as slave if false // check if at least one slave is available, use master as slave if false
if (!config.checkSkipSlavesInit() if (!config.checkSkipSlavesInit()) {
&& slaveBalancer.getAvailableClients() == 0) { if (slaveBalancer.getAvailableClients() == 0) {
slaveUp(newMasterClient.getAddr(), FreezeReason.SYSTEM); slaveUp(newMasterClient.getAddr(), FreezeReason.SYSTEM);
} else {
slaveDown(newMasterClient.getAddr(), FreezeReason.SYSTEM);
}
} }
oldMaster.shutdownAsync(); oldMaster.shutdownAsync();
log.info("master {} has changed to {}", oldMaster.getClient().getAddr(), masterEntry.getClient().getAddr()); log.info("master {} has changed to {}", oldMaster.getClient().getAddr(), masterEntry.getClient().getAddr());

Loading…
Cancel
Save