Well, it is not only with a huge index.
It is only if ReplicationHandler is in use on a master.
If ReplicationHandler is configured to replicateAfter startup it first
sends a commit via IndexWriter to have a "stable" index. The left over
of this operation is the write.lock.
So removing replicateA
Hi Mike,
thanks for the infos.
As far as I know a write.lock is created from an IndexWriter.
So I have to dig into it why an IndexWriter is created just
on starting solr with an optimized index.
The problem, this is only with a huge index.
And also old parts of the index are not cleaned up.
May
On Mon, May 2, 2011 at 9:17 AM, Bernd Fehling
wrote:
> Dear list,
>
> some questions about the index.
> (questions go to the lucene list because it is more about the index itself)
>
> First my results from CheckIndex:
>
> Segments file=segments_l6 numSegments=1 version=FORMAT_3_1 [Lucene 3.1]
> Ch
