I'd like to enable SPDY protocol using nginx. For this to work, do the
frontend haproxy load balancers need to operate in tcp mode only? Or, can they
use http mode to pass the SPDY requests to nginx?
I think you might have misunderstood. By adding new server, I mean to add it
as a server in HAProxy configuration. That is, the effect is to add the
server line for the new server into the config file. This has nothing to do
with launching the server in the cloud. It is the reverse of
Willy,
Thanks for your thoughts. I see that you have thought about these issues much
more than I have. I just wanted to get you some feedback from a potential
haproxy user.
As for your point that I would need to edit the static configuration file
incase of a complete restart of HAProxy, I
Zachary,
I guess I'll have to spend some time researching puppet (and/or chef). Thanks
for the reference.
Kevin
On Jan 9, 2013, at 6:18 PM, Zachary Stern z...@enternewmedia.com wrote:
Case in point for why puppet (and probably also chef) is perfect here.
You can manage the config with
,
On Fri, Jan 04, 2013 at 03:44:40PM -0500, KT Walrus wrote:
HAProxy also does all this stuff too (more or less). I plan on using HAProxy
if NGINX doesn't support everything I need done.
I have a preference to use as few software packages as possible so I keep the
system as simple
HAProxy also does all this stuff too (more or less). I plan on using HAProxy
if NGINX doesn't support everything I need done.
I have a preference to use as few software packages as possible so I keep the
system as simple and maintainable as possible. Being able to eliminate HAProxy
would be
if this wasn't the case, but I can't think of how to avoid
this possibility. If I could, I could probably set MAXCONN to utilize 80% of
the backend rather than a more conservative 50%, eventually, saving significant
money in scale out.
On Jan 3, 2013, at 2:56 AM, KT Walrus ke...@my.walr.us wrote:
Thanks
to the surviving DC to
minimize user perceived downtime (at DNSMadeEasy, they say that Failover can
happen fully in under 5 minutes if TTLs are set low and DNS caching respects
TTLs).
Kevin
On Jan 3, 2013, at 3:45 AM, Baptiste bed...@gmail.com wrote:
On Thu, Jan 3, 2013 at 8:56 AM, KT Walrus ke
, KT Walrus ke...@my.walr.us wrote:
One more tweak… I think the frontend LBs could be made to distribute the
load so that requests go to the backend that has the sessionDB that will be
used for the request rather than simple RR (by using cookies). This would
keep most requests handled entirely
on the web servers,
especially having two MySQL instances on *each* machine that will be serving
PHP...
Cheers,
Pedro.
On 3 Jan 2013, at 09:25, KT Walrus ke...@my.walr.us wrote:
basically, you need persistence :)
Well, I only need persistence to optimize traffic flow so the correct
Nevermind. I solved my problem by having the backend save the sessionDB server
id in its SESSION_ID cookie. If the SESSION_ID cookie isn't the same server id
as the localhost sessionDB, it knows a change has been made and it will first
copy the session data out of the read-only slave
I'm setting up a new website in the next month or two. Even though the traffic
won't require a scalable HA website, I'm going to start out as if the website
needs to support huge traffic so I can get some experience running such a
website.
I'd like any feedback on what I am thinking of doing…
can support both DNS Global
Traffic Director (east coast and west coast IP Anycast) and DNS Failover
(incase one datacenter goes offline).
cheers
On Thu, Jan 3, 2013 at 12:20 AM, KT Walrus ke...@my.walr.us wrote:
I'm setting up a new website in the next month or two. Even though
On May 8, 2012, at 2:01 PM, Willy Tarreau wrote:
That's why with the guys from Squid, Varnish and Wingate we presented
an concurrent proposal to the IETF one month ago :
http://tools.ietf.org/html/draft-tarreau-httpbis-network-friendly-00
I hope that HTTP 2.0 requires
14 matches
Mail list logo
