noise from a mozilla IT/Operations wrangler
Three years ago this coming December I went to Amsterdam and installed our first non-US data center location. I remember coming back and was up late at night (fighting jetlag) setting up the Netscaler load balancers. By early January we had a CVS mirror up and running and a week later had staged www.mozilla.com and… Read more
I mentioned briefly in Monday’s meeting the performance issues we’re having with our load balancers. Since then, we’ve been hustling to turn up something in the short term to handle Thursday’s Major Update and Firefox 3.0.5/2.0.0.19 release (see here). For a number of months we’ve been looking at Zeus and their ZXTM product. It has… Read more
The Mozilla community is blessed with a lot of freely donated bandwidth through our mirror network. This network handles product downloads through bouncer and a subset of this handles releases.mozilla.org, which carries contains Firefox, Thunderbird, Camino, Seamonkey, and Sunbird releases and Add-ons (and is huge, clocking in around 100-130G). releases.mozilla.org is handled through round-robin DNS. … Read more
We’ve been pushing production traffic out of our China colo for about a month now. One of my concerns was how well this site would serve our global user base and how well the Netscaler’s dynamic GSLB would work. I didn’t want users being sent to this data center who should really goto San Jose… Read more
Mozilla’s current GSLB (global server load balancing[1]) solution (Citrix Netscalers) is a mix of active proximity probes and static map assignments. The algorithm first checks to see if there’s a match in the static maps and then falls back to proximity metrics. If that’s missing, it’ll round-robin through all the GSLB sites (effectively three –… Read more