Denise (
denise) wrote in
dw_maintenance2011-08-19 07:04 am
![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png)
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
This morning's downtime
The downtime we had earlier this morning was due to a server upgrade at our hosting company -- we asked them to upgrade one of our machines from 4GB of RAM to 8GB of RAM, and to do it this time between 5AM and 6AM CDT (their timezone) with 12 hours' notice so we could let y'all know about the planned downtime. Well, they caught the requested window of upgrade time this time, but they missed the "with 12 hours' notice" part!
The machine that was taken out of the pool in order to upgrade happened to be a critical part of our infrastructure (the load balancer -- the machine that "listens" for traffic and directs it to the appropriate places on the network). We have our servers set up so that an outage of one machine, even if it's the load balancer, shouldn't cause the site to be completely down, but this morning exposed a glitch in our configuration that caused the "failover" to the backup load balancer to not kick in the way it was supposed to.
So, once the upgrade was complete,
alierak (who is rocking the sysadmin stuff this month) took some time out of his hectic morning to make sure everything went back to running along nicely so I didn't have to wake up
mark in the middle of his night, and we'll do what we can to make sure that in the future, losing the main load balancer will cause traffic to fail over to our backup load balancer more seamlessly.
Thanks, as always, to y'all for your patience with us, and for your continued support!
The machine that was taken out of the pool in order to upgrade happened to be a critical part of our infrastructure (the load balancer -- the machine that "listens" for traffic and directs it to the appropriate places on the network). We have our servers set up so that an outage of one machine, even if it's the load balancer, shouldn't cause the site to be completely down, but this morning exposed a glitch in our configuration that caused the "failover" to the backup load balancer to not kick in the way it was supposed to.
So, once the upgrade was complete,
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png)
Thanks, as always, to y'all for your patience with us, and for your continued support!
no subject
no subject
no subject
no subject
no subject
no subject
no subject
no subject
no subject
no subject
People in other countries may not know the US time zones, and the names may be ambiguous if two different countries use the same names for different zones.
At the same time, many Americans don't know what UTC is or what the numbers mean.
The best policy may be to give it in both formats, as in "CDT (UTC-5)". There will still be some who won't be able to figure it out, but hopefully most will.
no subject
no subject
no subject
Put in details (time, date, timezone) of your event and it returns a page with worldwide local times. Paste the resulting url into your post.
Eg: Unexpected memory upgrade
No confusion there :-)
(Still doesn't help when the hosting company decides to do it without notice though)
no subject
no subject
But really I just wanted to say that I'm new here and really like this place! :)
no subject
no subject
no subject
no subject
no subject
But, thanks to a prompt tweet I knew what was going on right away, and thanks to DW's awesomeness I could just back-button, and the comment I was trying to post was still there \o/
I'm glad things should be fixed for now.
no subject
Seems I was right :-)
Good to have you back!
(Hosting company need serious prodding)
no subject
no subject
no subject
no subject
You guys are awesome. <3
no subject
no subject
Wow! Only 8 gig of RAM. Cool. 8^)
no subject