On 12/3/2012 8:44 PM, Yonik Seeley wrote:
On Mon, Dec 3, 2012 at 9:59 PM, Shawn Heisey <s...@elyograg.org> wrote:
As you can see, _nd is missing the fnm and nrm files and _ne is missing lots
of files. When the next autocommit happened, _nf and _ng were created, and
both of the segments listed above were completed.
Ah, I think you're just seeing side-effects from soft commits (AKA
NRT-reopens) in conjunction with NRTCachingDirectory?
A soft commit simply flushes a segment to disk (but doesn't write a
new segments file to reference those files and hence can avoid
fsyncing those files), and then opens a new reader. the
NRTCachingDirectory is a write-back cache that caches small files in
memory (and that's prob why you don't see all of the files on disk).
My main concern in bringing this up wasn't the missing files, it was the
fact that every autocommit generates two segments instead of one, which
makes merges happen more frequently. Is that expected behavior?
It was my understanding that autocommit always did a hard commit. Is
that still the case, and I am just seeing something *like* a soft commit
courtesy of NRTCachingDirectory, or do I need a different config to
ensure they are hard commits?Here's my full updateHandler config:
<updateHandler class="solr.DirectUpdateHandler2">
<autoCommit>
<maxDocs>65536</maxDocs>
<maxTime>300000</maxTime>
</autoCommit>
<updateLog />
</updateHandler>
Thanks,
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
