John Marquiss created SOLR-10242:
------------------------------------
Summary: Cores created by Solr RESTORE end up with stale searches
after indexing
Key: SOLR-10242
URL: https://issues.apache.org/jira/browse/SOLR-10242
Project: Solr
Issue Type: Bug
Security Level: Public (Default Security Level. Issues are Public)
Components: Backup/Restore, search
Affects Versions: 6.3
Environment: Behavior observed on both Linux and Windows:
Linux version 3.10.0-327.36.3.el7.x86_64
([email protected]) (gcc version 4.8.5 20150623 (Red
Hat 4.8.5-4) (GCC) ) #1 SMP Thu Oct 20 04:56:07 EDT 2016
java version "1.8.0_77"
Java(TM) SE Runtime Environment (build 1.8.0_77-b03)
Java HotSpot(TM) 64-Bit Server VM (build 25.77-b03, mixed mode)
Windows 10 Enterprise Version 1607 Build 14393.693
java version "1.8.0_121"
Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)
Reporter: John Marquiss
Index files created by the Solr RESTORE feature are placed in a directory with
a name like "restore.20170307173236270" instead of the standard "index"
directory. This seems to break Solr's ability to detect index changes leading
to stale searchers on the restored cores.
Detailed information including steps to replicate can be found in this
solr-user mail thread. [http://markmail.org/message/wsm56jgbh53fx24u]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
