On Fri, Apr 25, 2014 at 02:40:57AM +0200, Alexander Bluhm wrote: > On Fri, Apr 25, 2014 at 09:09:03AM +0900, Ryan McBride wrote: > > Part of the reason it's there is to make carp work properly for services > > listening on the carp interface, in particular so that hosts in the > > BACKUP state will reach the MASTER rather than trying and failing to > > connect to their own carp interface. Maybe not needed in all setups, but > > likely to break things if we simply remove it. > > Why do you want to connect from the BACKUP machine to the MASTER > using CARP addresses? Just add another fixed address and you can > do that.
Two reasons that come to mind are: 1) For troubleshooting, so I can ping or otherwise monitor the MASTER host. 2) In some cases it's undisireable (or even not possible) to run services on other IP addresses. For example, services that only allow you to configure 1 listening IP, or services where you wish to avoid users connecting to anything but the MASTER server. > The current implementation may change the routing table in subtile > ways until nothing works. In IPv6 the routes are fixed and there > are less problems. In my opinion the current (intended) behaviour is correct; my preference would be to see this fixed rather than removed.
