couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Newson <>
Subject Re: silent view index file corruption
Date Wed, 07 Apr 2010 18:05:02 GMT
Being able to start a consistency checking task (that shows up in
_active_tasks, etc) would be useful. I don't think it's something that
ought to happen automatically, though. Possibly in the case where
corruption is actually detected?

I'd like;

a) checksums on *everything* (don't care for crc32 vs fnv1a vs md5 vs
sha1 debate, anything is massively better than nothing).
b) ability to launch end-to-end verification of all checksums (with
progress if possible).
c) ability to store/retrieve verification checkpoints.

Further to c), it would be useful to have API access to replication
checkpoints. Specifically so that we can interrogate one couchdb
instance and get some idea for how up to date it is with respect to
its replicas (which may be unreachable or offline).


On Wed, Apr 7, 2010 at 6:30 PM, Randall Leeds <> wrote:
> fnv1a looks interesting. I hadn't heard of this hash but I see how
> it'd be extremely fast and also easy to implement.
> I hadn't really thought through the merkle thing, I just kinda spat
> out words. I'll try not to do that in the future :-P
> As far as how paranoid to be... we obviously don't want to do a full
> table scan on writes, but could we afford a full table scan at startup
> to verify that the view index hasn't been corrupted since couch was
> last run?
> -Randall

View raw message