• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Technical question re: load balancers

B

Buddha Bart

Diamond Member
I saw some of the other threads about how the load balancers failed.

I'm about to deploy a webserver setup using LVS as well, I'd be curious to know what went wrong?

How did your implementation of LVS failover to serving that "you shouldn't be here" message? Did they run thier own small webserver?

Did the secondary load balancer not takeover when heartbeat failed to detect the primary? Or did it take over and then fail for whatever reason the first did (this is a big worry of mine, because if one fails for a configuration reason, and the other is identically configured, the failover probably won't help much).

bart
 
I believe it just ended up being the build of the LVS software they were using. They had some test pages up, and that was the page, somehow the LVS stopped sending requests and was responding itself. The issue was the same for both as they are identical.
 
I'd highly recommed the LVS stuff, it handles load well, our issue was a config issue, along with a the build we were using. I don't know the specifics of build #'s etc we are using at this point.
 
thats interesting. LVS itself can't act as a webserver, so they must have been also running something (apache, whatever) on the load balancers.

what happens if you load the IP of one of the load balancers in your browser? Not the virtual IP they share (depending on whoever's up and 'doign the job') but the actual IP they start up with before one of them alias's the virtual IP. I wouldn't be suprised if it was serving that page.

Hmm... In order for the LVS rules to have changed, it was probably your mon scritpts that bugged out. I was never a huge fan of the default httpd one, it doest close the connection properly.

That or your network hiccuped just long enough for the load balaners to decide everyone was dead in the water. Although thats not likely cuz usualy the mon scripts keep going and will put the servers back in rotation whenever they reappear.

I'd be curious to poke at the issue a bit more, is it the Pogo Linux guys who do your setup, or people from the LVS project?

bart
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top