Re: Cores renamed

2023-03-15 Thread Shawn Heisey
On 3/15/23 12:30, Oakley, Craig (NIH/NLM/NCBI) [C] wrote: Once again, Solr has taken upon itself to rename the core. Does anyone yet have any input on the idea of using the Leader's collection name in Leader/Follower replication? If you are in Cloud mode, let SolrCloud handle replication. Do

RE: Cores renamed

2023-03-15 Thread Oakley, Craig (NIH/NLM/NCBI) [C]
users@solr.apache.org Subject: RE: Cores renamed This has happened yet again. Does anyone yet have any input on the idea of using the Leader's collection name in Leader/Follower replication (or pre-Solr8.7 Master/Slave replication), rather than the core name? -Original Message- Fr

Re: Cores renamed

2023-02-27 Thread Shawn Heisey
On 2/27/23 09:03, Oakley, Craig (NIH/NLM/NCBI) [C] wrote: This has happened yet again. Does anyone yet have any input on the idea of using the Leader's collection name in Leader/Follower replication (or pre-Solr8.7 Master/Slave replication), rather than the core name? If you're in cloud mode

RE: Cores renamed

2023-02-27 Thread Oakley, Craig (NIH/NLM/NCBI) [C]
rsday, June 3, 2021 10:30 AM To: users@solr.apache.org Subject: RE: Cores renamed As a potential solution, I was wondering about implementing Master/Slave replication using the collection name of the Master rather than the core name. My initial experiment with this in a test environment seemed to

RE: Cores renamed

2021-06-03 Thread Oakley, Craig (NIH/NLM/NCBI) [C]
ction name in Master/Slave replication, rather than the core name? -Original Message- From: Oakley, Craig (NIH/NLM/NCBI) [C] Sent: Wednesday, June 02, 2021 5:46 PM To: users@solr.apache.org Subject: RE: Cores renamed It happened again this morning. Attached is an excerpt from solr.log

RE: Cores renamed

2021-06-02 Thread Oakley, Craig (NIH/NLM/NCBI) [C]
t;state":"active", "type":"NRT", "force_set_state":"false", "router":{"name":"compositeId"}, "maxShardsPerNode":"1", "autoAd

RE: Cores renamed

2021-05-17 Thread Oakley, Craig (NIH/NLM/NCBI) [C]
"type":"NRT", "force_set_state":"false", "leader":"true", "router":{"name":"compositeId"}, "maxShardsPerNode":"1",

Re: Cores renamed

2021-05-17 Thread matthew sporleder
og for the most recent problem (with IP > addresses and port numbers redacted) > > Please not that Master/Slave replication breaks when a core is renamed, so > this can be a major problem > > > Any ideas? > > -Original Message- > From: Alexandre Rafalovitch > Sen

RE: Cores renamed

2021-05-17 Thread Oakley, Craig (NIH/NLM/NCBI) [C]
day, May 12, 2021 2:10 PM To: users@solr.apache.org Subject: Re: Cores renamed This is truly a shot in the dark, but is it possible you have something in core.properties file (which is where the core name is for non-Cloud setup)? What does the core renames itself to, that would probably be

Re: Cores renamed

2021-05-12 Thread Alexandre Rafalovitch
21 10:57 AM > To: solr-u...@lucene.apache.org > Subject: Cores renamed > > We recently have had a few occasions when cores for one specific collection > were renamed (or more likely dropped and recreated, and thus ended up with a > different core name). > > Is this a known phenomenon? Is th

RE: Cores renamed

2021-05-12 Thread Oakley, Craig (NIH/NLM/NCBI) [C]
This phenomenon has happened again (this time without any REQUESTRECOVERY) Does anyone yet have any explanation of this? -Original Message- From: Oakley, Craig (NIH/NLM/NCBI) [C] Sent: Thursday, January 28, 2021 10:57 AM To: solr-u...@lucene.apache.org Subject: Cores renamed We