[
https://issues.apache.org/jira/browse/COUCHDB-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Shorin closed COUCHDB-1064.
-------------------------------------
Resolution: Cannot Reproduce
Closing this issue as outdated. Provided logs aren't available anymore to
figure out the reasons. Try to upgrade your CouchDB up to the latest release
and if this issue is still actual - reopen it.
> Couchdb view lost (generation started from scratch)
> ---------------------------------------------------
>
> Key: COUCHDB-1064
> URL: https://issues.apache.org/jira/browse/COUCHDB-1064
> Project: CouchDB
> Issue Type: Bug
> Affects Versions: 1.0.2
> Environment: Erlang R14B01 (erts-5.8.2) [source] [64-bit] [smp:8:8]
> [rq:8] [async-threads:0] [hipe] [kernel-poll:false]
> Linux buzz 2.6.26-2-amd64 #1 SMP Thu Sep 16 15:56:38 UTC 2010 x86_64 GNU/Linux
> Debian Lenny
> Reporter: Victor Jerlin
>
> Couch is currently doing view generation for 5 db's, with 3-4 views per db,
> with 30 million documents in each. Then I have another db with 120 million
> documents in.
> I've noticed that couch starts more couchjs processes after a while, like it
> forgets that it already has a couchjs process running for that view.
> After a while(hours), it ends up running more couchjs processes than I have
> views. This seems to be because of couch forgetting about the couchjs
> process, and
> launches another one when my crontabbed wget-script triggers view generation
> again.
> It has now happened (a few times) that it decides to rebuild the view from
> scratch.
> Logs from one of the times can be found at
> http://83.168.240.46/seq_reset_1.log.gz
> It is whois_queue _design/by_domain that resets at 09:40:01 (and the post
> requests before did not touch the design document)
> I have logs from other time when it happens to another view as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
