Shots fired at MIT - report of an active shooter near Bldg. 32 (Stata)

Re:Shots fired at MIT - report of an active shooter near Bld... by trobertson on Friday April 19, 2013 @05:30AM (#5575679)

Certain threads generate enormous amounts of activity, and the reddit infrastructure will automatically place those threads into a temporary 'Read Only Mode'. This effectively ends the thread when it revolves around rapid updates, so redditors normally start 'Incident Thread 2', then 3, and so on.

During the Boston Marathon bombing, there were, if I remember correctly, over a dozen threads that continued the original conversation, simply because each of the previous threads kept getting hammered by people posting comments.

[ Parent | on HN ]

Re:Shots fired at MIT - report of an active shooter near Bld... by buro9 on Friday April 19, 2013 @05:53AM (#5575748)

I guess I'm just curious on the technical side, about why they go into a temporary read-only mode. What issues forced that to be implemented?

I am mostly wondering whether it's the threaded nature of a thread on Reddit that makes this a difficult problem, or whether this is reflective of some limitation in the underlying datastore or something.

[ Parent | on HN ]

Re:Shots fired at MIT - report of an active shooter near Bld... by fyi80 on Friday April 19, 2013 @10:52AM (#5576936)

It's because a the database isn't completely agnosticly load-balanced, and a single story is stored/processed with more co-locality than a random sample of, say, 10000 randomly chosen comments.

It's easier to cache and serve a fixed piece of content than to constantly insert and re-compress it (which kills cached versions too)

[ Parent | on HN ]