On 28.09.09 15:04, Chris Hostetter wrote:
My company currently runs several clusters of application servers
behind load balancers, which are each in turn sitting behind a cluster
of squid machines configured as accelerators. each squid cluster is then
sitting behind a load balancer that is
: Couldn't the same thing be done with ACLs? (deny icp/htcp from
: localhost)
: The problem is multi-stage loops: proxyA-proxyB-proxyA which only shows
: up in the two headers.
:
: The first-degree example I list above can be solved by ACL in icp_access,
: but when you go another level out
Chris Hostetter wrote:
: Couldn't the same thing be done with ACLs? (deny icp/htcp from
: localhost)
: The problem is multi-stage loops: proxyA-proxyB-proxyA which only shows
: up in the two headers.
:
: The first-degree example I list above can be solved by ACL in icp_access,
: but when
: For a bit of leverage; every time the config changes squid needs to be
: reconfigured, which causes a short outage.
:
: I've been thinking about it, and the multiple-IPs for a cache_peer might
: work when a DNS name is entered as first parameter of cache_peer. But only
: the IPs detected at
: Another solution could be to use a multi-level CARP config, which incidentally
: scales far better horizontally than ICP/HTCP, as it eliminates the iterative
: sideways queries altogether by hashing URLs to parent cache_peers. In this
...
: different IP or TCP port that actually does
: What would be really nice is a command line option and a bit of code
: in the cache peer setup that recognizes own IP and ignores the entry,
: to make this problem just all go away...
That would be awesome, but if i'm understanding you correctly it would
only address the talking to myself
Chris Hostetter wrote:
: What would be really nice is a command line option and a bit of code
: in the cache peer setup that recognizes own IP and ignores the entry,
: to make this problem just all go away...
That would be awesome, but if i'm understanding you correctly it would
On Tue, 29 Sep 2009 12:59:52 -0700 (PDT), Chris Hostetter
hossman_sq...@fucit.org wrote:
: What would be really nice is a command line option and a bit of code
: in the cache peer setup that recognizes own IP and ignores the entry,
: to make this problem just all go away...
That would be
Background Information...
My company currently runs several clusters of application servers behind
load balancers, which are each in turn sitting behind a cluster of squid
machines configured as accelerators. each squid cluster is then sitting
behind a load balancer that is hit by our
On Mon, 28 Sep 2009 15:04:35 -0700 (PDT), Chris Hostetter
hossman_sq...@fucit.org wrote:
Background Information...
My company currently runs several clusters of application servers
behind
load balancers, which are each in turn sitting behind a cluster of
squid
machines configured as
: The DNS way would indeed be nice. It's not possible in current Squid
: however, if anyone is able to sponsor some work it might be doable.
If i can demonstrate enough advantages in getting peering to work i might
just be able to convince someone to think about doing that ... but that
also
On Mon, 28 Sep 2009 17:24:16 -0700 (PDT), Chris Hostetter
hossman_sq...@fucit.org wrote:
: The DNS way would indeed be nice. It's not possible in current Squid
: however, if anyone is able to sponsor some work it might be doable.
If i can demonstrate enough advantages in getting peering to
On Mon, Sep 28, 2009 at 5:24 PM, Chris Hostetter
hossman_sq...@fucit.org wrote:
: The DNS way would indeed be nice. It's not possible in current Squid
: however, if anyone is able to sponsor some work it might be doable.
If i can demonstrate enough advantages in getting peering to work i
On Mon, 28 Sep 2009 17:57:02 -0700, George Herbert
george.herb...@gmail.com wrote:
On Mon, Sep 28, 2009 at 5:24 PM, Chris Hostetter
hossman_sq...@fucit.org wrote:
: The DNS way would indeed be nice. It's not possible in current Squid
: however, if anyone is able to sponsor some work it might
Barring the development of an in-code fix, I think your best bet is to
take the config generator route you describe, but then run the
generator from your squid initscript triggered by start or reload.
Beyond pushing out an updated text file to your boxes and building the
cache_peer lines
15 matches
Mail list logo
