Hmmm, if there is a bug, odds are it's due to multicore stuff  -
probably nothing else has touched core stuff like that recently.
Can you reproduce (or rather help others to reproduce) with the
solr/example setup?

-Yonik

On Wed, Apr 30, 2008 at 5:39 PM, Matthew Runo <[EMAIL PROTECTED]> wrote:
> Hello!
>
>  In using the SVN head version of Solr, I've found that recently we started
> getting multiple open SegmentReaders, all registered... etc..
>
>  Any ideas why this would happen? They don't go away unless the server is
> restarted, and don't go away with commits, etc. In fact, commits seem to
> cause the issue. They're causing issues since it causes really stale
> searchers to be around...
>
>  For example, right now...
>  org.apache.solr.search.SolrIndexSearcher
>  caching : true
>  numDocs : 153312
>  maxDoc : 153324
>  readerImpl : SegmentReader
>  readerDir : org.apache.lucene.store.FSDirectory@/opt/solr/data/index
>  indexVersion : 1205944085143
>  openedAt : Wed Apr 30 14:04:15 PDT 2008
>  registeredAt : Wed Apr 30 14:04:15 PDT 2008
>
>  (and right below that one...)
>  org.apache.solr.search.SolrIndexSearcher
>  caching : true
>  numDocs : 153312
>  maxDoc : 153324
>  readerImpl : SegmentReader
>  readerDir : org.apache.lucene.store.FSDirectory@/opt/solr/data/index
>  indexVersion : 1205944085143
>  openedAt : Wed Apr 30 14:30:02 PDT 2008
>  registeredAt : Wed Apr 30 14:30:02 PDT 2008
>
>  Thanks!
>
>  Matthew Runo
>  Software Developer
>  Zappos.com
>  702.943.7833
>
>

Reply via email to