Mark Smith (
mark) wrote in
dw_maintenance2012-04-28 05:22 pm
Site slowness expected shortly
Hi all,
Summary: some unexpected but required maintenance is going to cause the site to slow down by some amount for the next hour or two.
Some details: We have run into an issue with one of our larger communities that requires us to make a change to the way we store comments in memcache. This means that our caches are all going to invalidate here in a few minutes when I roll the code out, so the databases are going to get very busy until we repopulate the caches.
Those of you who have been on LJ for a few years might remember when ONTD ran into an issue when they hit 16,777,215 comments and LJ had to do the same thing. I helped LJ with the code to fix the problem, but for some reason, never committed it on Dreamwidth. Now we have hit the same issue and I feel silly for having not done that, but here we are, and hence this maintenance.
Please let me know if you see any major problems, and again, sorry for the inconvenience. This really isn't a great time to be doing site maintenance.
Update: Congratulations to
sixwordstories for being the first community or journal to hit the 16.7 million comment limit in the database. :)
At any rate, currently the community is being migrated to a database where I fixed up the column widths so they won't have this limit anymore. It will take some time to move that much data, though. In the meantime the community will be in read-only mode.
I'm sorry that we hit this -- I really thought we had made this fix on Dreamwidth after LJ ran into it. It turns out we didn't, though, hence this situation. Alas.
Summary: some unexpected but required maintenance is going to cause the site to slow down by some amount for the next hour or two.
Some details: We have run into an issue with one of our larger communities that requires us to make a change to the way we store comments in memcache. This means that our caches are all going to invalidate here in a few minutes when I roll the code out, so the databases are going to get very busy until we repopulate the caches.
Those of you who have been on LJ for a few years might remember when ONTD ran into an issue when they hit 16,777,215 comments and LJ had to do the same thing. I helped LJ with the code to fix the problem, but for some reason, never committed it on Dreamwidth. Now we have hit the same issue and I feel silly for having not done that, but here we are, and hence this maintenance.
Please let me know if you see any major problems, and again, sorry for the inconvenience. This really isn't a great time to be doing site maintenance.
Update: Congratulations to
At any rate, currently the community is being migrated to a database where I fixed up the column widths so they won't have this limit anymore. It will take some time to move that much data, though. In the meantime the community will be in read-only mode.
I'm sorry that we hit this -- I really thought we had made this fix on Dreamwidth after LJ ran into it. It turns out we didn't, though, hence this situation. Alas.

no subject
no subject
no subject
Good luck with this! :)
no subject
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
no subject
no subject
[edit: Of course, DW isn't so little now anyway. But still...]
no subject
(no subject)
no subject
no subject
no subject
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
no subject
no subject
Uh, sorry Mark, couldn't resist; but I *am* curious if your earlier statement about 2^24 comments in that comm and the numerical figure that tied up LJ are the same - again?
no subject
♥
It's so nice just being allowed some looks behind-the-scenes of what you're doing; it really helps the site feel friendly and accessible. I'm so glad I and so many others migrated here!
no subject
I love this place! :D
(no subject)
no subject
no subject
no subject
no subject
no subject
A lot of the comment counts look pretty high, but that's the only one I checked before popping back in here to say something, because it was the first one I opened (one of my characters periodically played with the OP of that thread and I couldn't remember if that post was one of the times she did... it wasn't).
no subject
(And to be clear, when the dupes are removed the profile page will drop back to the number it's supposed to have. The count will be accurate, it's just that the database will have empty spots that it can never re-use.)
(no subject)
no subject
and compared to the current problems with lj - i think i'll cope! :)
no subject
no subject
no subject
no subject
(no subject)
(no subject)
no subject
no subject
no subject
:|
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
no subject
I'm using Chrome. If I clean my cache and try to open or 'reply to' a
This is what pops up on the page for me:
Error 503 Service Unavailable
Service Unavailable
Guru Meditation:
XID: 2017400525
Varnish cache server
Any news on when that will stop?
no subject
We'll get it fixed as soon as we can!
(no subject)
Me again
Re: Me again
Re: Me again