2009/5/26 Thomas G. Willis <[email protected]>:
>
> On May 24, 10:40 am, lasizoillo <[email protected]> wrote:
>> 2009/5/24 Jorge Vargas <[email protected]>:
>> > couchdb,
>>
>> I am porting a couchdb app to other storage. I am getting a lot of db
>> corruptions and I havn't tools to repair this. Couchdb is great for
>> read-only (or add-only) schema. Modifications and deletes are
>> painfull.
>>
>
>> Javi
>
> Just curious, Is there a bug filed for corruptions in couchdb? I was
> playing with it this weekend, and it seemed pretty useful and I didn't
> notice any issues. But it would be nice to know what to look out for
> if I develop an app that depends on it any further.  Briefly looking
> at the open issues for couch(and there are lots) I don't see anything
> related to data corruption.

Maybe is not a couchdb issue and is a erlang (BEAM), freebsd or
anything else issue.

Maybe my problem is like this:
http://www.erlang.org/pipermail/erlang-patches/2008-July/000258.html

I don't know why erlang crash with core dumped when write over a
corrupted register. The crash affects other connections for some
seconds raising errors. You can read the corrupt register, but not
modify or delete it. Compactations (read entire db and generates new
one with lesser size) don't solve the problem, but you gets a less
size corrupt db. With replication, you obtain a failure or a corrupt
replicated db.

The database have sensible information (I can't send it to developers
team). I don't know how to recreate the error. I can't create an issue
saying "somethings fails".


>
> Also, you need the trunk version of python-couchdb in order for views
> to work properly on the latest version of couch. In case anyone else
> reading this is having those issues.
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to