Andy Vuong created SOLR-14134:
---------------------------------
Summary: Clear shared core's concurrency cache
Key: SOLR-14134
URL: https://issues.apache.org/jira/browse/SOLR-14134
Project: Solr
Issue Type: Sub-task
Components: SolrCloud
Reporter: Andy Vuong
In shared collections, each replica's core has an associated entry in a
metadata cache we call the shared core's concurrency cache (see
SharedCoreConcurrencyController) that is used to facilitate concurrent indexing
support of a single shard and associated optimizations.
Entries are currently created on demand - i.e. when request triggered
pulls/pushes are initiated but there's no way of clearing the cache unless the
node goes down and JVM restarts.
Eviction from this cache is needed to facilitate things such as collection name
reuse. Currently if you delete a collection and then recreate, you can create a
Replica containing the same core name as a previously active collection/replica
and have a pre-existing entry in the concurrency cache (barring restarts
between this point). The net effect is at least one indexing batch failure
before the cache returns to a correct state.
Eviction will also support scale - say 50k collections and thousands of entries
for cores located in memory is highly ineffective especially if a large number
of collections are accessed infrequently.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]