Denise (
denise) wrote in
dw_maintenance2009-04-18 06:19 pm
![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png)
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
Import issues
There are three commonly-reported issues we're seeing with importing your journal right now:
* Some icons are not transfering over -- the message will say that they're successful, but only the keywords/comments will come over, not the userpic itself.
* Entries will appear to have no comments, until you click through to the entry itself, at which point the comments will be visible.
* Tags will appear not to import, until you wait for a little while.
We're aware of all three problems, and are working on diagnosing and fixing them. There's no need to open a support request about these problems.
The other issues described in this news post still apply.
The geeky bits, for those who care:
The first problem is happening because the userpics are in the database, but not in MogileFS, our image-storage filesystem. We know what's happening, but haven't figured out what's causing it yet. Once we do, we'll fix it from happening again, and we'll likely be able to fix it automatically for every affected account (although we can't say that for sure until we locate the root cause).
We think that the second and third problems are happening because of memcached, the function we use to store commonly-accessed information in memory to drastically increase site performance. It may turn out to be something else entirely, of course, but our leading theory right now is that the information is making its way to our database, the database is just not telling memcached that the information's been updated. We're looking into the best ways to solve it. In the meantime, viewing the comment page and then returning to your journal will cause the comment counts to display properly, and some people have reported that viewing the Manage Tags page and then returning to your tags list will cause your tags to show up.
EDIT, 2300 EDT 18 April: We believe we've figured out what was causing these problems. Future imports (anything scheduled after now) should no longer display these symptoms, and we're working out the best way to fix accounts that were affected. We'll make a new
dw_maintenance post with the postmortem once we've deployed the fix.
* Some icons are not transfering over -- the message will say that they're successful, but only the keywords/comments will come over, not the userpic itself.
* Entries will appear to have no comments, until you click through to the entry itself, at which point the comments will be visible.
* Tags will appear not to import, until you wait for a little while.
We're aware of all three problems, and are working on diagnosing and fixing them. There's no need to open a support request about these problems.
The other issues described in this news post still apply.
The geeky bits, for those who care:
The first problem is happening because the userpics are in the database, but not in MogileFS, our image-storage filesystem. We know what's happening, but haven't figured out what's causing it yet. Once we do, we'll fix it from happening again, and we'll likely be able to fix it automatically for every affected account (although we can't say that for sure until we locate the root cause).
We think that the second and third problems are happening because of memcached, the function we use to store commonly-accessed information in memory to drastically increase site performance. It may turn out to be something else entirely, of course, but our leading theory right now is that the information is making its way to our database, the database is just not telling memcached that the information's been updated. We're looking into the best ways to solve it. In the meantime, viewing the comment page and then returning to your journal will cause the comment counts to display properly, and some people have reported that viewing the Manage Tags page and then returning to your tags list will cause your tags to show up.
EDIT, 2300 EDT 18 April: We believe we've figured out what was causing these problems. Future imports (anything scheduled after now) should no longer display these symptoms, and we're working out the best way to fix accounts that were affected. We'll make a new
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
no subject
Since you last tried importing 10 days ago, and since we have made changes to the importer since then, go ahead and try running your import again. If the comments don't come over in about 24h, open a support request.
no subject