You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Mikhail Khludnev (JIRA)" <ji...@apache.org> on 2017/05/17 18:56:04 UTC
[jira] [Assigned] (SOLR-10594) Revise SolrConfigHandler.reloadLock
after SolrCloudExampleTest fix
[ https://issues.apache.org/jira/browse/SOLR-10594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Khludnev reassigned SOLR-10594:
---------------------------------------
Assignee: Mikhail Khludnev
> 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
> Assignee: 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org