You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Adam Kocoloski (JIRA)" <ji...@apache.org> on 2010/08/08 03:04:17 UTC
[jira] Resolved: (COUCHDB-844) Documents missing after CouchDB
restart
[ https://issues.apache.org/jira/browse/COUCHDB-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam Kocoloski resolved COUCHDB-844.
------------------------------------
Fix Version/s: 1.0.1
Resolution: Fixed
Randall Leeds wrote a test case and a patch, which I've committed to both trunk and the 1.0.x branch.
> Documents missing after CouchDB restart
> ---------------------------------------
>
> Key: COUCHDB-844
> URL: https://issues.apache.org/jira/browse/COUCHDB-844
> Project: CouchDB
> Issue Type: Bug
> Components: Database Core
> Affects Versions: 1.0
> Environment: Debian Version 5.0.5, Linux *** 2.6.29-xs5.5.0.17 #1 SMP Mon Aug 3 17:37:37 UTC 2009 i686 GNU/Linux, XenServer Guest
> Reporter: Sascha Reuter
> Priority: Critical
> Fix For: 1.0.1
>
>
> After a CouchDB restart, recently added/changed documents+designdocuments (min. 2 weeks timeline!) are missing and cant be accessed trough REST Calls / Futon.
> All documents that are still available trought REST/Futon only exist in old revisions.
> All documents/revisions can be found doing a manual search (less/egrep/...) in the datafile (/var/lib/couchdb/<database>.couch)
> Example:
> strings dtap.couch | grep -i "226b2e6c-24b7-4336-92c7-257abf923b11"
> $226b2e6c-24b7-4336-92c7-257abf923b11h
> $226b2e6c-24b7-4336-92c7-257abf923b11l
> $226b2e6c-24b7-4336-92c7-257abf923b11l
> $226b2e6c-24b7-4336-92c7-257abf923b11l
> $226b2e6c-24b7-4336-92c7-257abf923b11l
> $226b2e6c-24b7-4336-92c7-257abf923b11l
> $226b2e6c-24b7-4336-92c7-257abf923b11l
> $226b2e6c-24b7-4336-92c7-257abf923b11l
> $226b2e6c-24b7-4336-92c7-257abf923b11l
> $226b2e6c-24b7-4336-92c7-257abf923b11h
> $226b2e6c-24b7-4336-92c7-257abf923b11h
> curl http://localhost:5984/dtap/226b2e6c-24b7-4336-92c7-257abf923b11
> {"error":"not_found","reason":"missing"}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.