lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cassandra Targett (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SOLR-4669) conf file replication can cause new index to be loaded before new core (with new configs) is loaded.
Date Wed, 10 Jan 2018 20:42:00 GMT

     [ https://issues.apache.org/jira/browse/SOLR-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Cassandra Targett updated SOLR-4669:
------------------------------------
    Component/s: replication (java)

> 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
>          Components: replication (java)
>            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 was sent by Atlassian JIRA
(v6.4.14#64029)

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


Mime
View raw message