Open danrange opened 8 years ago
Hi @danrange
the bogus IPv6 address shown by the sentinel slaves mymaster
command were valid address at same point in your network?
As far as I know there isn't a way to configure the service not to use IPv6.
To understand what is going on it would help to know the output of the ipconfig command on each server to check all the IPs exposed.
Hello, I have 5 Windows Servers (in a production environment) each running a Redis server and a Sentinel (v2.8.2400). One Redis is a Master and the rest Slaves. The Sentinels all point to the master with quorum 3. Servers have IPv4 static addresses but also IPv6 (set to automatically obtain addresses). All configuration files use IPv4 addresses.
My problem is that the Sentinels are registering a large number of slaves, with apparently bogus IPv6 addresses. When I try to perform a failover test the elected sentinel aborts because it cannot find a suitable slave to promote.
When I query a Sentinel with
sentinel slaves mymaster
it gives me the following IPs:(The one IPv4 address above is where I have disabled IPv6 on a server - have not tried a failover with this). None of these addresses (apart from the IPv4) correspond to the 5 servers, and don't/no longer exist on the network. When I query the master about its slaves it gives me:
Why are slave0/1/2 all the same address? The Slaves themselves are replicating okay, but an
info replication
shows me that they are using local DNS names.So several questions really - Why are the sentinels picking up all these IPv6 addressed? Why are they not picking up the actual IPv6 addresses of the 5 servers? And is there a way to configure Redis/Sentinel not to use IPv6?
Thanks.