You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Nilesh Singh (Jira)" <ji...@apache.org> on 2019/09/24 15:47:00 UTC
[jira] [Updated] (SOLR-13789) Solr core reload with config change
upstream put solr instance in bad state
[ https://issues.apache.org/jira/browse/SOLR-13789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nilesh Singh updated SOLR-13789:
--------------------------------
Description:
In a master/slave setup if the schema.xml is changed on master, during replication on slave solr instance, solr tries to reload the core with the new config.
During the reload operation solr creates a new searcher but it is not checking the status of the searcher and make this new core active.
Problem arises when the custom caches attached to the searcher has not been warmed up. In some scenarios custom caches might take some times to warm up in the background.
This issue becomes critical during the schema changes in live solr instances, that makes solr to return bad responses until the searcher caches are fully ready.
was:
In a master/slave setup if the schema.xml is changed on master, during replication on slave solr instance, solr tries to reload the core with the new config.
During the reload operation solr creates a new searcher but it is not checking the status of the searcher and make this new core active.
Problem arises when the custom caches attached to the searcher has not been warmed up. In some scenarios custom caches might take some times to warm up in the background.
> Solr core reload with config change upstream put solr instance in bad state
> ---------------------------------------------------------------------------
>
> Key: SOLR-13789
> URL: https://issues.apache.org/jira/browse/SOLR-13789
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: replication (java)
> Affects Versions: 6.6.5, 8.1.1
> Reporter: Nilesh Singh
> Priority: Critical
> Labels: patch
>
> In a master/slave setup if the schema.xml is changed on master, during replication on slave solr instance, solr tries to reload the core with the new config.
> During the reload operation solr creates a new searcher but it is not checking the status of the searcher and make this new core active.
> Problem arises when the custom caches attached to the searcher has not been warmed up. In some scenarios custom caches might take some times to warm up in the background.
>
> This issue becomes critical during the schema changes in live solr instances, that makes solr to return bad responses until the searcher caches are fully ready.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org