Mark Smith (
mark) wrote in
dw_maintenance2009-08-16 11:20 pm
![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png)
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
Importer functional again // next code update Monday
After the latest Slicehost failure (a jobserver went down), one of the tasks that runs imports didn't get restarted. Entry/comment imports have been stuck in the queue since that point (roughly 48 hours).
We're going to fix this so it doesn't happen again by setting our alerts so they fire when something is in the queue for more than 60 minutes. Right now, the warnings fire when the queue goes above 100 items: which, in this case, it hadn't. But they were getting pretty stale, which is a bad thing.
...
We will be doing a code push tomorrow. The scheduled time is slightly later than we're used to, to give me time to get home from the day job and make sure things are in order:
Monday, August 17th, 2009 @ 10PM (2200) PDT
Tuesday, August 18th, 2009 @ 5AM (0500) UTC
This will be a rather large push - lots of changes - so please expect the site to be bumpy while we get the code updated and everything restarted. As always, I will update Twitter and this journal when we get closer to the time.
We're going to fix this so it doesn't happen again by setting our alerts so they fire when something is in the queue for more than 60 minutes. Right now, the warnings fire when the queue goes above 100 items: which, in this case, it hadn't. But they were getting pretty stale, which is a bad thing.
...
We will be doing a code push tomorrow. The scheduled time is slightly later than we're used to, to give me time to get home from the day job and make sure things are in order:
Monday, August 17th, 2009 @ 10PM (2200) PDT
Tuesday, August 18th, 2009 @ 5AM (0500) UTC
This will be a rather large push - lots of changes - so please expect the site to be bumpy while we get the code updated and everything restarted. As always, I will update Twitter and this journal when we get closer to the time.
no subject
no subject
no subject
Stay tuned though, we have news on that front. :)
no subject
no subject
no subject
Also, thank you for putting the different timezones on the post.
no subject
no subject