We have a setup with a load balancer that points to 2 squid servers listening and serving as cache to 4 machines, and we have it in pairs:
squid1
|-www1
|-www2
squid2
|-www3
|-www4
Each squid is configure to send requests to their requests:
# this is squid.conf for squid1
# www1
cache_peer 192.168.1.110 parent 80 0 no-query originserver weight=1 round-robin
# www1
cache_peer 192.168.1.111 parent 80 0 no-query originserver weight=1 round-robin
# this is squid.conf for squid2
# www3
cache_peer 192.168.1.112 parent 80 0 no-query originserver weight=1 round-robin
# www4
cache_peer 192.168.1.113 parent 80 0 no-query originserver weight=1 round-robinThe settings.php of each machine only points to the squid server that applies (www1 points to squid1 as reverse proxy and www3 points to squid2)
We applied the reverse proxy patch found here http://2bits.com/articles/increasing-drupals-speed-squid-caching-reverse...
All of them serve the same site, and we are having some problems were apparently the session is lost and depending the page we hit the user seems to be logged in or not (the loggen in user cookie IS set, btw)
So, a few questions: should the settings.php point to both squid servers and include all servers on the round-robin on the squid confs? Besides the cookie checking configuration explained there do we have to change something else on the squid.conf?
My understanding is that drupal marks as non cacheable all content as soon as you log in, so that's why we are a little confused when we log in and depending on the page we hit we get the "you're logged in" or "welcome, log in" message...
Thanks