Update - 3/15/2010
5 views
Skip to first unread message
Scott Alden
Mar 15, 2010, 8:21:55 PM3/15/10
to bgg_down
If you saw the notice today - you'll see that we switched over the
recently viewed database to use MongoDB (a NOSQL document store
database). This worked fine when we tested it, but it suffers several
crashes under load. It crashed about 15 times today.
recently viewed database to use MongoDB (a NOSQL document store
database). This worked fine when we tested it, but it suffers several
crashes under load. It crashed about 15 times today.
I'm reverting back to our MySQL version of storing recently viewed.
Sorry for the inconvenience - I was hoping that Mongo would work out,
because the reads and writes from the database were lightning fast
which would improve performance for everyone.
I don't have a good estimate on the downtime, but I'll guesstimate it
will take about 2 hours.
--
Scott
MahatmaManic
Mar 15, 2010, 8:30:02 PM3/15/10
to BGG Down
Good luck with the work and thanks for the update. I'm glad it's not
me who has to do all this systems work. Ugh.
me who has to do all this systems work. Ugh.
snoozef...@gmail.com
Mar 15, 2010, 8:30:42 PM3/15/10
to BGG Down
2 HOURS?!
Actually, just checking what time this was posted....
milandoug
Mar 15, 2010, 8:34:45 PM3/15/10
to BGG Down
sigmazero13
Mar 15, 2010, 11:11:12 PM3/15/10
to BGG Down
I like the idea of a faster DB - is the crashing something that can be
resolved, or is it a permanent flaw-under-stress of that new DB type?
resolved, or is it a permanent flaw-under-stress of that new DB type?
Reply all
Reply to author
Forward
0 new messages