From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Invalid meta data error in OklahomaMixer
Date: Tue, 14 Jun 2011 03:30:58 +0000 [thread overview]
Message-ID: <1308022018-sup-5391@masanjin.net> (raw)
In-Reply-To: <BANLkTikqVo2WLyOJ7jTdRgyBm9d3=DbRMw@mail.gmail.com>
Reformatted excerpts from Horacio Sanson's message of 2011-06-14:
> Not even close... my store.tch is 76MB only. This metadata corruption
> in Tokyo Cabinet seems to be a common occurrence and what is scary
> about this is that there seems to be no way to recover from it (as far
> as google can tell). The only option I see is delete my store/index
> and restart sync again.
Can you point me to some links about this type of corruption?
I'm far from wedded to Oklahoma Mixer / Tokyo Cabinet. It was just the
easiest thing to get started with. Any kind of mutable persistent
key-value store will do. Other alternatives to consider: another
TokyoCabinet gem besides OH, KyotoCabinet, BDB... I kinda don't want to
move to separate processes like Redis though. If only there were a
libredis (well there is, but it's not what you want.)
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2011-06-14 3:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-11 15:30 Horacio Sanson
2011-06-14 2:14 ` William Morgan
2011-06-14 2:14 ` William Morgan
2011-06-14 2:37 ` Horacio Sanson
2011-06-14 3:30 ` William Morgan [this message]
2011-06-14 4:21 ` Horacio Sanson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1308022018-sup-5391@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--cc=sup-devel@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox