Terrific! Thank you. I realize y'all get a lot of flak for the
comparisons on the wiki, but this is a good differentiator re:
MongoDB.
Mongo is a very nice product, but if you want to start a project small
on a single server and grow if it makes it, you're exposed on the data
corruption side until
Hi Jason/Sean,
I'll chime in on this one. Embedded Inno uses exactly the same
transactional logging as it does under MySQL so it should recover in the
same way without needing any user intervention. The tools Sean
mentioned can be used in dire circumstances (e.g. log files got overrun
or do
Yes, you can use low-level commands to recover lost data from the binlogs.
It's embedded InnoDB, not MySQL's driver, so not everything is exactly the
same, but the technique is similar.
Sean Cribbs
Developer Advocate
Basho Technologies, Inc.
http://basho.com/
On May 26, 2010, at 11:42 PM, Jas
That's terrific. We're very familiar with InnoDBs buffer pool and
that's exactly the kind of control we're looking for. With the
InnoStore backend is the crash recovery/durability similar to InnoDB
under MySQL?
-J
On Wed, May 26, 2010 at 8:13 PM, Sean Cribbs wrote:
> Riak's usage of memory prima
Riak's usage of memory primarily depends on the backend you choose. Innostore,
for example, has a configurable buffer pool (cache) which can help you limit
the memory footprint. Bitcask, our most recently released backend, keeps only
a hash mapping keys to file/offset in memory (with the value
