Just thinking loud, but Mapping is a OS feature.
For example , if a recovery is happening ( and it involves less than 100
docs of difference), the Tlog will be read to reproduce the data.
This will cause the Tlog to be accessed and ideally memory mapped.
Am I correct ?
Cheers
On 28 October 2015 a
yep. Although I won't guarantee that the tlog won't be MMapped
even if this is turned off.
On Tue, Oct 27, 2015 at 4:21 PM, Rallavagu wrote:
> Is it related to this config?
>
>
>
Is it related to this config?
Hmm, the tlog. AFAIK, that's because of
"real time get" (Yonik/Mark/Whoever, please
correct if wrong).
This is a feature where when fetching a document as
the result of a search it insures that you get the most
recent version whether it's been committed or not.
The tlog isn't relevant for sea
On 10/27/15 8:43 AM, Erick Erickson wrote:
bq: So, the updated file(s) on the disk automatically read into memory
as they are Memory mapped?
Yes.
Not quite sure why you care, curiosity or is there something you're
trying to accomplish?
This is out of curiosity. So, I can get better understan
bq: So, the updated file(s) on the disk automatically read into memory
as they are Memory mapped?
Not quite sure why you care, curiosity or is there something you're
trying to accomplish?
The contents of the index's segment files are read into virtual memory
by MMapDirectory as needed to satisfy
Erick, Thanks for clarification. I was under impression that
MMapDirectory is being used for both read/write operations. Now, I see
how it is being used. Essentially, it only reads from MMapDirectory and
writes directly to disk. So, the updated file(s) on the disk
automatically read into memory
You're really looking at this backwards. The MMapDirectory stuff is
for Solr (Lucene, really) _reading_ data from closed segment files.
When indexing, there are internal memory structures that are flushed
to disk on commit, but these have nothing to do with MMapDirectory.
So the question is reall
