couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Newson <>
Subject Re: couchdb-lucene reindexes when restarted
Date Wed, 14 Apr 2010 12:19:16 GMT
Ok, I think I understand this now.

When you start couchdb-lucene on a database for the first time (and
after a restart), it looks at the update_seq of all the Lucene indexes
it has on disk and takes the lowest number of these. It then uses that
in a call to _changes?since=N.

My suspicion is you have an index that is no longer reachable (because
you've changed your index function at some point). This index won't be
updated, so it's stuck at 27200.

I've pushed an update that will log (at DEBUG level, so change
log4j.xml temporarily) how the 'since' value is calculated. It would
be very helpful if you could verify my hypothesis.

You can fix this, if I'm right, by running _cleanup (check the README
for the syntax) which will delete the unreachable index. I need to
make a real fix, though; namely, the update_seq calculation should
ignore unreachable indexes.


On Wed, Apr 14, 2010 at 1:07 PM, Manokaran K <> wrote:
> On Wed, Apr 14, 2010 at 5:34 PM, Manokaran K <> wrote:
>> Again. This time I restarted couchdb leaving c-l running:
>> 2010-04-14 17:32:32,193 INFO [spulz] View[digest=acv33jkyzefc7wb8djdc0cyw5]
>> now at update_seq 202639
>> 2010-04-14 17:32:32,323 INFO [spulz] View[digest=5krdzy83b9nlrsl5pnru6eh3s]
>> now at update_seq 202639
>> 2010-04-14 17:32:32,338 INFO [spulz] View[digest=bafqygi7kb41yj0wq5swblbx5]
>> now at update_seq 202639
>> 2010-04-14 17:33:35,971 INFO [spulz] Indexing from update_seq 27200
> I do make one change to the db between the restarts, a new 'session' doc is
> added to the db. But its not indexed for fti or views. I hope that's not a
> problem.
> thanks,
> mano

View raw message