Slashdot Posting Bug Infuriates Haggard Admins 262
Last night we crossed over 16,777,216 comments in the database. The wise amongst you might note that this number is 2^24, or in MySQLese an unsigned mediumint. Unfortunately, like 5 years ago we changed our primary keys in the comment table to unsigned int (32 bits, or 4.1 billion) but neglected to change the index that handles parents. We're awesome! Fixing is a simple ALTER TABLE statement... but on a table that is 16 million rows long, our system will take 3+ hours to do it, during which time there can be no posting. So today, we're disabling threading and will enable it again later tonight. Sorry for the inconvenience. We shall flog ourselves appropriately. Update: 11/10 12:52 GMT by J : It's fixed.
Sorry, could not resist. (Score:2, Insightful)
Please do.
D'oh. (Score:5, Insightful)
And let this be a reminder to the kids - RTFM, twice!
So who's the killer? (Score:5, Insightful)
Dupe! (Score:0, Insightful)
GSM phones to monitor traffic problems, anyone ?
My Reply to the Funny Comment Above This (Score:5, Insightful)
You claim that the 16,777,216th comment would have broke it but I contest that actually the 16,777,217th comment poster would be the culprit. Since it should be able to handle that many comments if it is zero referenced, and it would actually be the one after that one that would break it. You laugh but these kinds of problems plague a lot of coders?
If you don't agree with me, please respond below and reference my comment ID.
Should have used PostgreSQL instead.. (Score:2, Insightful)
Let the flamewars begin...
Slashed Eyeballs (Score:4, Insightful)
Open source - it's not just a buzzword, it's a way of life.
24 bit? (Score:5, Insightful)
Re: Access to the database (Score:3, Insightful)
Not just grad students; as a DBA by profession, I'd love a crack at the DB. If nothing else, it would give me a great place to play around with MySQL. Not to mention the ability to maybe extract some interesting user-level statistics.
Of course, the odds of this happening are pretty damn low - there'd have to be an awful lot of work and review done to scrub the DB of information that is entrusted to
Just the email addresses would be a huge deal - can you imagine the market value of such a targeted list of addresses?
In short, it would be fantastically cool for them to release the DB, but it would be a lot of work on their part for no particular return. Not to mention that if they released it once, they'd no doubt be pestered to keep releasing periodic updates...then there's the bandwidth issues...and, even, the potential copyright issues (/. doesn't own the copyright on posted comments, the poster does)...then the copyright issues for stuff they do own; releasing the DB would make it trivial for a bad actor to post a mirrored slash. A little bit of domain typosquatting and some ad deals, and you could be talking about real money.
If I were them, there's no way in hell I'd even think about doing it.
But it would be cool.
Parent [slashdot.org]
+10 (Score:5, Insightful)
At least they didn’t try to make bullshit excuses. I respect them for being up front about the real nature of the issue.
Mysql long running alter command (Score:1, Insightful)
I too run multi-master replication -- but only one server is primary at any one point in time.
To get around this problem, I made the change on one of the standby servers, failed over the web application to that server and then implemented the change on the previously live server.
So why was this 24-bit to begin with? (Score:4, Insightful)
Re:Congrats taco (Score:1, Insightful)
To get back on topic, my heart say's perl, but my head says