Corrupted Databases Are Fun 60
Notice how all these stories are disappearing? Is it because
I'm a censorship oriented Nazi? According to my inbox, thats
the only rational explanation. The truth is that we've been
having database problems for several days. Stories are
randomly disappearing. Its making me really cranky. I
haven't been eating or sleeping much. But I'm working on
it. I'm really sorry about all this crap. Believe me, its
pissing me off more than you.
Try this... (Score:1)
:-) keep smiling.
I especially like how icons from two days ago
are showing up in the title bar now.
censorship oriented Nazi... (Score:1)
8)
(ah, sarcasm is so relaxing)
Slashdot servers are compromised? (Score:1)
Considering your database corruption and the root compromise of the Slashdot server last year, isn't it a strange coincidence that the story about the vulnerabilities in the WuFTPd and ProFTPd software should be the one to disappear?
Rob et al, have you checked your servers in detail to see if they have been compromised again and re-installed from scratch?
First! (Score:2)
At least Slashdot is still going... (Score:2)
Open source? (Score:1)
MySQL is hardly Open Source(tm), I didn't know there was any pretense that is was...
Not just articles (Score:1)
Weird things are happening lately indeed.
I wonder what tcx (the mysql guys) has to say about that, did you buy support?
Jumping to conclusions is MORE fun! (Score:1)
Rob the Party Pooper. Shooting down all the wonderful conspiracy theories. Well, this semi-downtime gives everybody a chance to rest up their flamethrowers. Right?
BURP!!
(with apologies to... M**PT!!)
--
YATYR (Score:1)
Erk! (Score:1)
I, for one, -don't- think you're any kind of censorship nazi and a pox on anybody who does think that. You do extremely valuable work, put in an enormous amount of time & effort, and I certainly appreciate the results!
Hang in there, Rob.... (Score:1)
Slashdot servers are compromised? (Score:1)
A good one.
Messages disappearing too (Score:1)
Anyways, thanks for fixing.
<tim><
hit reload (Score:1)
<tim><
Great job (Score:1)
Maybe we should organize a stroke-a-thon -- have slashdotters clap if they like Rob...
Free the source to Slashdot and sleep easy (Score:1)
We are all in this together. (Score:1)
Cheers,
smithdog
A reasonable variation: (Score:1)
periodically creating static HTML files from a dynamic database.
A fully-dynamic system has to read the DB and spew crap out for every user (could be many requests per second!) The theory is that this system is the most "live" (i.e. changes are visible to everyone immediately). The reality is that the hardware requirements of this system are very high for a moderate to high traffic site (Slashdot surely qualifies).
A periodically updated system has to read the DB and spew data (this time to files, not users) only once every 30 seconds, 1 minute, 5 minutes, or whatever seems like a reasonable interval. Compared to running many times per second, this starts to look pretty nice. And you'd be surprised how large you can make the intervals while still maintaining a good user experience. An interval of 2 minutes would be almost indistinguishable from a truly live, dynamic system to most users, and 5 minutes is still completly within the realm of acceptability. The final optimization is to update the bare minimum files that need to be updated on each cycle. That's the real trick, but done right, it can be very efficient (thus allowing you to decrease the update interval even more). Think about it :-)
Oh, and as for corrupted DBs, what DB server are you using?
One word: (Score:1)
isamchk [mysql.com]
Read all about it...
(Sorry if this is a duplicate)
It's not all roses (Score:1)
Whether it is a good idea or not depends on whether the disadvantages of complexity and lack of transparency outweigh the advantages of clean access API and high flexibility. The answer does not always favour RDBMSs because high flexibility can be irrelevant in many cases, especially in an informal web environment. A combination of DBM files and directory-based structuring can often provide both rapid access and a lot of flexibility while keeping complexity very low and transparency very high. Furthermore, this can interface trivially with standard file distribution mechanisms to scale the whole thing up to thousands of servers if you feel the urge, and without introducing single points of failure that are almost inevitable with commit-based solutions.
It is a mistake to head blindly down the RDBMS route without seriously considering that there are strings attached. Use them where it is *necessary*, not where the tempting illusion of a simple SQL API makes it appear merely convenient.
Slashdot (Score:1)
Great service you have here,for the people!
Keep up the good work! Thanks!
where's the bazaar (Score:1)
again, where's the code? where's the remote cvs?
Sabotage! (Score:1)
How 'bout a Reader's Digest Condensed version?
Squishdot?
Just thought I'd say... (Score:1)
A reasonable variation: (Score:1)
Good Work, Rob (Score:2)
Everyone seems to forget that Slashdot has been growing by leaps and bounds lately. Don't be suprised that there are a few problems. Be suprised that it hasn't crashed and burned long ago.
Why? I'd guess that it probably has something to do with the fact that Rob et al have been busting their butts to keep it running so all the Slashdot Longhairs can make them feel appreciated by telling them how much Slashdot sucks.
I know I'm kicking a dead horse, but it seems that most forget that this is a free site, run by volunteers who care deeply about it. I'm not saying constructive criticism is bad, but there's a reason they call it constructive.
Rob, thanks for running the best site on the Web. Keep up the awesome work. (And don't OD on those caffienated penguins!)
Chris
A mySQL suggestion (Score:2)
I hope you've paid the $ 200 for support and asked the mySQL folks about this. I run a much lower volume web site with mySQL, and I've never had any problems. But in case my sites become higher volume, I'd sleep a lot better at night if I saw a resolution of some sort to these problems.
D
Enough is enough! Switch databases! Do something! (Score:1)
Calm down everyone! (Score:1)
Enough is enough! Switch databases! Do something! (Score:1)
Hi, Hello, howdy, We are with you (Score:1)
Keep up the Good work, Metaphor
We're with you, Chaos
Don't let it get you down, Reality
We feel your pain, Master Switch
I am possessed by daemons.
-Master INIT
You? A Net-Nazi? (Score:1)
Keep up the good work, and you might consider a vacation, if you want to train a lackey. No, I'm not volunteering; I'm a greeeeen Linux newbie!
Penguins make me piss like a race horse. (Score:1)
Y2K..? (Score:1)
You don't suppose these database problems could be a symptom of a Y2K compatibility problem..?
Just a thought..
everyone needs to chill (Score:2)
In the end-thanks Rob, you're doing a great job, and good luck getting everything back to normal
Hope this article doesn't Dissapear (Score:1)
Remove fingers from kbd and pat yourself on back! (Score:1)
-Signed Me
great job, but switch the database (Score:1)
You are indeed doing a great job with Slashdot, but it definitely seems like it's time change the database. You shouldn't use a product just because it's Open Source.. if it doesn't work, dump it. We all criticize Microsoft and other companies for writing buggy software that breaks. We should be just as demanding of the Open Source projects.
Good luck with everything...