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 the biggest hint. Regards, Alex. On Wed, 12 May 2021 at 14:00, Oakley, Craig (NIH/NLM/NCBI) [C] <craig.oak...@nih.gov.invalid> wrote: > > 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] <craig.oak...@nih.gov.INVALID> > Sent: Thursday, January 28, 2021 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 there any explanation? > > It may be relevant that we just recently started running this SolrCloud on > version 8.5.2, although the collection was created under Solr7.4. Also, this > collection seems to experience some heavy updates such that the non-Leader > replica has trouble keeping up. One of these renames occurred at 4:33am, so I > highly suspect that the rename (or drop and recreate) was done by some > internal Solr thread rather than by any of my coworkers. One other potential > clue is that I can see that /solr/admin/cores?action=REQUESTRECOVERY was > usually run on the new core a moment after it was created. > > Does anyone have any insights?
