[jira] [Created] (SOLR-15830) Concurrent core reload messes up commits when using Schema API

["Bence Szabó (Jira)" <ji...@apache.org>]

Bence Szabó created SOLR-15830:
----------------------------------

             Summary: Concurrent core reload messes up commits when using Schema API
                 Key: SOLR-15830
                 URL: https://issues.apache.org/jira/browse/SOLR-15830
             Project: Solr
          Issue Type: Bug
      Security Level: Public (Default Security Level. Issues are Public)
            Reporter: Bence Szabó


When using Schema API SchemaManager class triggers a core reload here: [https://github.com/apache/solr/blob/cfc953b6b906ef742bba57024d327fbde5d564c2/solr/core/src/java/org/apache/solr/schema/SchemaManager.java#L132]

As I understand this was introduced in SOLR-9832 and is useful to avoid accidentally reloading to an older version of the config. The problem is that in the solr core a listener is implemented to initiate a reload whenever a config change happens in ZK, this can be found here: [https://github.com/apache/solr/blob/cfc953b6b906ef742bba57024d327fbde5d564c2/solr/core/src/java/org/apache/solr/core/SolrCore.java#L3140]

When updating the schema using the Schema API both of these reloads get triggered and this can result a strange bug, where not all the indexed documents are visible if the indexing is started just after the schema API returned.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org