comments in line...
On 3/17/16 2:16 PM, Erick Erickson wrote:
First, I want to make sure when you say "TTL", you're talking about
documents being evicted from the documentCache and not the "Time To Live"
option whereby documents are removed completely from the index.
May be TTL was not the right word to use here. I wanted learn the
criteria for an entry to be ejected.
The time varies with the number of new documents fetched. This is an LRU
cache whose size is configured in solrconfig.xml. It's pretty much
unpredictable. If for some odd reason every request gets the same document
it'll never be aged out. If no two queries return the same document, when
"cache size" docs are fetched by subsequent requests.
The entire thing is thrown out whenever a new searcher is opened (i.e.
softCommit or hardCommit with openSearcher=true)
But maybe this is an XY problem. Why do you care? Is there something you're
seeing that you're trying to understand or is this just a general interest
question?
I have following configuration,
<autoCommit><maxTime>${solr.autoCommit.maxTime:15000}</maxTime><openSearcher>false</openSearcher></autoCommit>
<autoSoftCommit><maxTime>${solr.autoSoftCommit.maxTime:120000}</maxTime></autoSoftCommit>
As you can see, openSearcher is set to "false". What I am seeing is
(from heap dump due to OutOfMemory error) that the LRUCache pertaining
"Document Cache" occupies around 85% of available heap and that is
causing OOM errors. So, trying to understand the behavior to address the
OOM issues.
Thanks
Best,
Erick
On Thu, Mar 17, 2016 at 1:40 PM, Rallavagu <rallav...@gmail.com> wrote:
Solr 5.4 embedded Jetty
Is it the right assumption that whenever a document that is returned as a
response to a query is cached in "Document Cache"?
Essentially, if I request for any entry like /select?q=id:<Document ID>
will it be cached in "Document Cache"? If yes, what is the TTL?
Thanks in advance
