Assuming server A with IP M, server B with IP N, and DNS entry X
currently pointing at IP M:
1) Add heartbeat on servers A and B, with heartbeat managing a new IP
address O (this is your virtual IP -- nothing to do with VRRP, that's
for your routers to failover your gateway).
2) If you
J Potter wrote:
Assuming server A with IP M, server B with IP N, and DNS entry X
currently pointing at IP M:
1) Add heartbeat on servers A and B, with heartbeat managing a new IP
address O (this is your virtual IP -- nothing to do with VRRP, that's
for your routers to failover your
Yes, I normally want one server handling the full load to maximize the
cache hits. But the other one should be up and running.
So, active/standby. Easier config. Squid won't even be aware that
heartbeat is running; just keep it running on both servers all the time.
See my install notes at
I'm running a pair of squids as an internal cache for some intermediate
data used by a web server farm and currently doing failover by going
through an F5 bigip. However, I'd like to avoid the bigip and use
heartbeat since there are only two machines. I don't need to sync any
content since
Les Mikesell wrote:
I'm running a pair of squids as an internal cache for some intermediate
data used by a web server farm and currently doing failover by going
through an F5 bigip. However, I'd like to avoid the bigip and use
heartbeat since there are only two machines. I don't need to
nate wrote:
I'm running a pair of squids as an internal cache for some intermediate
data used by a web server farm and currently doing failover by going
through an F5 bigip. However, I'd like to avoid the bigip and use
heartbeat since there are only two machines. I don't need to sync any
6 matches
Mail list logo
