kristina

7 ms·

1.
by kristina 15y ago
For 2.0, there is some major work on locking being done (concurrency will be an ongoing theme in 2011) and online compaction has been implemented (although you have to kick it off, it's not yet automatic).
2.
by kristina 15y ago
Ah, sorry, I assumed people would understand that from the post. I added (preview, not production-ready), is that better?
3.
How to set up a Redis cluster (preview, not production-ready)(antirez.com)
45 points by kristina 15y ago|15 comments
4.
by kristina 16y ago
I'm reluctant to put such technical info on the documentation homepage, but I've updated it to very clearly point people to Production Notes. How does it look now?
5.
by kristina 16y ago
Actually, it's more like saying, "we HIGHLY recommend having a backup parachute" (as, I'd imagine, most skydiving instructors would). Also, I think I've always mention it in my talks. I'm not sure how VoltDB escaped your wrath, it's an in-m
6.
by kristina 16y ago
Writing to disk and transaction logs are nice, but they aren't magic bullets. What if a data center catches fire? More mundanely, I've heard ~6% of hard drive fail/year. Only replication can help you there. I'd argue that durability is a
7.
by kristina 16y ago
Response (awaiting moderation, I think it's the links?): ------- > haha, that’s funny. i regularly use non-CouchDB databases and I get along great with > all the people from other databases at conferences. Oh, I tend to bite people
8.
by kristina 16y ago
We really, really want people to know they should run on multiple servers. Do you have any suggestions on making it clearer? Where did you look for information about running it in production (so I can add stuff about multiple servers to t
9.
by kristina 16y ago
> Having said that, I must ask. Do the "unchecked" writes, > configurable fsyncs and multi-node writes exist in the > currently stable version of MongoDB or are these features > still in alpha or beta? They're all availab
10.
by kristina 16y ago
I've tried to post this as a comment on the blog, but it's not showing up (moderated?): ----------- Full disclosure: I work for 10gen. You strategically posted this when my air conditioning was broken, so here are a few thoughts before I go
11.
by kristina 16y ago
...which is why you have a slave. Master corrupt? Promote the slave to master, get it its own slave. Repairing a corrupted database, even a relational database, often takes too long for a production app.
12.
by kristina 16y ago
They go into it in the actual paper, if you're interested. They wanted a document store because their data is flexible (all different sizes and shapes), complex, and they needed secondary indexes. They didn't need transactions and MongoDB