[
https://issues.apache.org/jira/browse/SOLR-10742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson updated SOLR-10742:
----------------------------------
Description:
SolrCores.getNamesForCore iterates through all the cores to find all the
aliases to this core. It does this in a synchronized block which blocks other
core operations.
For installations with many cores this can be a performance issue. I'm not sure
it makes sense to do it this way anyway, perhaps SolrCore should have a list of
its current aliases and we can be more efficient about this? Or otherwise get
this information in a less heavy-weight fashion?
I'm assigning this to myself to keep track of it, but anyone who wants to grab
it please feel free.
was:
SolrCores.getCoreNames iterates through all the cores to find all the aliases
to this core. It does this in a synchronized block which blocks other core
operations.
For installations with many cores this can be a performance issue. I'm not sure
it makes sense to do it this way anyway, perhaps SolrCore should have a list of
its current aliases and we can be more efficient about this? Or otherwise get
this information in a less heavy-weight fashion?
I'm assigning this to myself to keep track of it, but anyone who wants to grab
it please feel free.
> SolrCores.getNamesForCore is quite inefficient and blocks other core
> operations
> -------------------------------------------------------------------------------
>
> Key: SOLR-10742
> URL: https://issues.apache.org/jira/browse/SOLR-10742
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Erick Erickson
> Assignee: Erick Erickson
>
> SolrCores.getNamesForCore iterates through all the cores to find all the
> aliases to this core. It does this in a synchronized block which blocks other
> core operations.
> For installations with many cores this can be a performance issue. I'm not
> sure it makes sense to do it this way anyway, perhaps SolrCore should have a
> list of its current aliases and we can be more efficient about this? Or
> otherwise get this information in a less heavy-weight fashion?
> I'm assigning this to myself to keep track of it, but anyone who wants to
> grab it please feel free.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
