lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <j...@apache.org>
Subject [jira] [Created] (SOLR-4669) conf file replication can cause new index to be loaded before new core (with new configs) is loaded.
Date Wed, 03 Apr 2013 23:09:15 GMT
Hoss Man created SOLR-4669:
------------------------------

             Summary: conf file replication can cause new index to be loaded before new core
(with new configs) is loaded.
                 Key: SOLR-4669
                 URL: https://issues.apache.org/jira/browse/SOLR-4669
             Project: Solr
          Issue Type: Bug
            Reporter: Hoss Man


Unless i'm smoking crack, some behavior i noticed working on SOLR-4629 indicates that when
solr replication detects both a changed index, and changed config files, the index is copied
over and put into use by the current solr core, then the conig files are copied over, and
then the solr core is reloaded with the modified configs.

which means there is a window of time in which the "new" index is being searched using the
old configs -- which could have bizare consequences.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message