[
https://issues.apache.org/jira/browse/SOLR-15964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17488299#comment-17488299
]
ASF subversion and git services commented on SOLR-15964:
--------------------------------------------------------
Commit f6d60c375cdabfbd6d5e17b4050db362eb4dbff4 in solr's branch
refs/heads/main from David Smiley
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=f6d60c3 ]
SOLR-15964: move javadoc to correct method
> Transient cores should not be unloaded/evicted while it's being used
> --------------------------------------------------------------------
>
> Key: SOLR-15964
> URL: https://issues.apache.org/jira/browse/SOLR-15964
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Major
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> When using "transient cores" (transient=true on the core and configure
> transientCacheSize in solr.xml), Solr will evict/unload a core that appears
> to be getting little use when there is pressure on this cache. However, this
> mechanism doesn't truly check that the core isn't being used when making this
> decision. It could happen that a core is undergoing a long running operation
> (huge indexing batch?) but otherwise nothing else, and assuming some cache
> pressure on many others cores during this time, Solr will then "evict" this
> core. Solr will then consider this core unloaded even though it exists in
> memory and is open for this long-running operation for some time. If by bad
> luck a request comes in to use this core, Solr will attempt to load a new
> SolrCore for it which will fail due to the write lock file. At this point,
> the core is unusable until the node is restarted.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
