[
https://issues.apache.org/jira/browse/SOLR-10594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Khludnev updated SOLR-10594:
------------------------------------
Attachment: SOLR-10594.patch
[^SOLR-10594.patch] drops SolrConfigHandler.reloadLock, and reload triggering
on {{handleGET}} keeping all existing tests green. I suppose even concurrent
config updates (which we probably don't have a test for) will work on
[^SOLR-10594.patch] relying on Zk listening only.
[~noble.paul], are you fine to have it committed?
> Revise SolrConfigHandler.reloadLock after SolrCloudExampleTest fix
> ------------------------------------------------------------------
>
> Key: SOLR-10594
> URL: https://issues.apache.org/jira/browse/SOLR-10594
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Mikhail Khludnev
> Attachments: SOLR-10594 no reload on config GET.patch,
> SOLR-10594.patch
>
>
> SOLR-10588 fixed {{SolrCloudExampleTest}} by introducing ill dependency
> {{SolrCore --> SolrConfigHandler.reloadLock}} let's think how we can design
> it better. And it's also worth to think about overall flow: core reload is
> triggered by Zk listener and SolrConfigHandler see SOLR-10588
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
