Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 729
  • Last Modified:

Load balancing Squid and Web Servers with Squid

Greetings,

We have 2 squid servers (each one with a public IP) and 2 web servers.


We have 2 DNS records published so users will load balance across the 2 squid servers, but how do I load balance the squid servers across the 2 web servers?

for example, users go to www.test.com.

they arrive at either cache1 or cache2.

How do I tell cache1 to load balance between web1 and web2? same with cache2?

We are doing this through multiple DNS entries which our local DNS server respond with both web server IP addresses; but what happens if one web server goes down?

How can I tell squid to load balance across multiple web servers for the same domain and if one of the web servers go down to easily take it of the configuration? We have implemented round robin DNS but the problem is that if a server goes down DNS won't know about it and even if we remove it from DNS the cache server will have that IP address in dns cache


What's the better way to do this?
0
ddiazp
Asked:
ddiazp
  • 5
  • 4
1 Solution
 
mooodiecrCommented:
Squid has a similar round -robin technique you can try.  We use this very successfully for an extremely busy website.  In the squid configuration file add:

http_port 1.2.3.4.:80 defaultsite=www.thefraggle.com vhost
cache_peer 1.2.3.5 parent 80 0 no-query originserver round-robin
cache_peer 1.2.3.6 parent 80 0 no-query originserver round-robin

This can be placed at the very top of the squid config file.
0
 
mooodiecrCommented:
0
 
ddiazpAuthor Commented:
We already have something similar:


http_port 80 accel defaultsite=www.test.com vhost
cache_peer www1.test.com parent 80 0 no-query no-digest originserver name=cache_www default

where www1.test.com is our other cache server. Is this wrong?



Or do we need to remove:

cache_peer www1.test.com parent 80 0 no-query no-digest originserver name=cache_www default

and add:

cache_peer web1.test.com parent 80 0 no-query no-digest originserver name=cache_www default
cache_peer web2.test.com parent 80 0 no-query no-digest originserver name=cache_www default
0
Lessons on Wi-Fi & Recommendations on KRACK

Simplicity and security can be a difficult  balance for any business to tackle. Join us on December 6th for a look at your company's biggest security gap. We will also address the most recent attack, "KRACK" and provide recommendations on how to secure your Wi-Fi network today!

 
mooodiecrCommented:
That is correct:
"
Or do we need to remove:

cache_peer www1.test.com parent 80 0 no-query no-digest originserver name=cache_www default

and add:

cache_peer web1.test.com parent 80 0 no-query no-digest originserver name=cache_www default
cache_peer web2.test.com parent 80 0 no-query no-digest originserver name=cache_www default
"

the port and accel entry is the site that is to be used and then there needs to be two separate entries for the load balancing sites.  Just to note the IP address or DNS name can resolve locally if needed.  i.e. web2.test.com can read 127.0.0.1
0
 
ddiazpAuthor Commented:
Awesome, one last question.

What will Squid do in the event that one of the webX.test.com is down or cannot contact it?
0
 
mooodiecrCommented:
Squid tracks the reachability status of its neighbour caches. When using ICP, or any other protocol you choose, Squid marks a neighbour as down when the neighbour fails to reply to 20 consecutive ICP queries. As soon as a reply is received again, the neighbour is marked up.

In addition to ICP, Squid also monitors TCP connections. When a TCP connection to a neighbour fails, Squid marks the neighbour down and begins a process to periodically (every 80 seconds) retry a diagnostic TCP connection. When the diagnostic connection succeeds, the neighbour is marked up.

So, in order for Squid to consider a neighbour cache as up, these two conditions must be true:

   1. The last TCP connection must have been successful.
   2. There must be fewer than 20 consecutive unacknowledged ICP queries.
0
 
ddiazpAuthor Commented:
You say cache neighbors. Are these the actual webservers? We'll implement this and give it a shot.

Thanks
0
 
mooodiecrCommented:
In your scenario it would be whatever site is being served/cached so yes.
0
 
ddiazpAuthor Commented:
This worked, forgot about closing this ages ago!
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now