Phew :)
Mike
On Thu, Sep 10, 2009 at 8:14 PM, Jason Rutherglen
wrote:
> Indexing locking was off, there was a bug higher up clobbering the
> index. Sorry and thanks!
>
> On Thu, Sep 10, 2009 at 4:49 PM, Michael McCandless
> wrote:
>> That's an odd exception. It means IndexWriter thinks 468 do
Indexing locking was off, there was a bug higher up clobbering the
index. Sorry and thanks!
On Thu, Sep 10, 2009 at 4:49 PM, Michael McCandless
wrote:
> That's an odd exception. It means IndexWriter thinks 468 docs have
> been written to the stored fields file, which should mean the fdx file
>
That's an odd exception. It means IndexWriter thinks 468 docs have
been written to the stored fields file, which should mean the fdx file
size is 3748 (= 4 + 468*8), yet the file size is far larger than that
(298404).
How repeatable is it? Can you turn on infoStream, get the exception
to happen,
I'm seeing a strange exception when indexing using the latest Solr rev on EC2.
org.apache.solr.client.solrj.SolrServerException:
org.apache.solr.client.solrj.SolrServerException:
java.lang.RuntimeException: after flush: fdx size mismatch: 468 docs
vs 298404 length in bytes of _0.fdx
at
or
