THR is back up.  Thanks for your patience.

Click here to return to THR.

In the long run we’ll be doing this periodically, like early in the morning on the first day of every month.

We’re doing this one manually though, as the database could really stand to be defragmented after the recent move.  Estimated down-time is approximately one hour.

Sorry for the inconvenience.

Edited to add: The process was started at ~ 9:15 Eastern time.  The time estimate was made based on the old database server, so I can’t say for certain that the new server will take the same time to complete.

I’ll record the time here though, and that will be the estimate next time.

10:36 Update: It’s still chugging.  I’m here watching it, so as soon as the database is running again I’ll take a quick couple of minutes to check its performance over the last couple of days, maybe tweak a setting or two, and put things back up online.

If you’re watching this page rather than refreshing THR, I’ll put up  a notice here in red that’s hard to miss.

For future reference: downtime associated with defragging the database and tweaking MySQL a bit based on historic performance was ~ 105 minutes.

Tagged with:
 

5 Responses to Scheduled Downtime: Wednesday morning, 5/17/2011

  1. CoRoMo says:

    Scheduled Downtime: Wednesday morning, 5/17/2011

    Is today May 17th? Or is today Wednesday?

    .45acp vs. 9mm… which should I choose?

  2. Tom Pelle says:

    Sorry, but at 1:00 PM EDT you’re still not back up.

  3. some dude says:

    Actually it isn’t up…

  4. saenzrich says:

    THR is back up. Thanks for your patience…………………..not working for me?

  5. Derek says:

    Sorry folks. In the past THR’s messages would eventually turn into blank pages or database errors as database maintenance was performed.

    I changed this so that I could shut down THR’s servers and you would all see the message you saw. Unfortunately, some people continued to see the status message rather than the web page once we were back up.

    I’ll do things differently in the future. I value clear communication about outages, but don’t want that to be at the cost of continued downtime for some users.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Set your Twitter account name in your settings to use the TwitterBar Section.