On Wed, Apr 14, 2010 at 5:03 PM, Manokaran K <[email protected]> wrote:
> > On Wed, Apr 14, 2010 at 4:56 PM, Robert Newson <[email protected]>wrote: > >> One thought. There is a delay between indexing and commit the index to >> disk. updates within that period (currently 60s seconds) will indeed >> be redone if you restart couchdb-lucene. I'll make the setting >> configurable but it will always be at least a few seconds, as this >> makes for much more efficient i/o. You can see search results before >> the data is committed to disk, so perhaps this explains what you're >> seeing? >> >> > Its not just a few documents that gets indexed. I suspect all the docs in > the db get read for reindexing - I would not have noticed it otherwise :-) > > My connection is crawling... maven is still downloading things needed for > the latest from github. Will update later on what happened. > > Its happening in the latest build also! Following is the c-l output just before and after restart: 2010-04-14 17:25:11,189 INFO [spulz] View[digest=acv33jkyzefc7wb8djdc0cyw5] now at update_seq 202639 2010-04-14 17:25:11,247 INFO [spulz] View[digest=5krdzy83b9nlrsl5pnru6eh3s] now at update_seq 202639 2010-04-14 17:25:11,257 INFO [spulz] View[digest=bafqygi7kb41yj0wq5swblbx5] now at update_seq 202639 ^cm...@acer:~/couchdb-lucene$ ./bin/run 2010-04-14 17:26:18,886 INFO [Main] Index output goes to: /home/mano/couchdb-lucene-0.5-SNAPSHOT-latest/indexes 2010-04-14 17:26:18,910 INFO [Main] Accepting connections with selectchannelconnec...@localhost:5985 2010-04-14 17:26:29,547 INFO [spulz] Indexing from update_seq 27200 I'm curious that its indexing from update_seq 27200 even though before restart it was already at 202639!! thanks, mano
