I do restart Solr after changing schema using "solr zk upconfig". I am yet to confirm but I do have a daily cron that does "delta" import. Does that process have any bearing on some cores losing the field?
On Thu, Aug 29, 2019 at 11:32 AM Shawn Heisey <apa...@elyograg.org> wrote: > On 8/29/2019 11:26 AM, Antony A wrote: > > Hi, > > > > I am running on Solr cloud 7.2.1. I have 4 core collection. The fields > are > > available in the schema.xml in solr admin UI. This tells me zookeeper has > > the correct schema. But unfortunately only the leader core has the > correct > > response to the query with the field while other cores are throwing the > > below error stack. Restarting the core returns the correct results but > > trying to avoid that situation. > > > > o.a.s.h.RequestHandlerBase org.apache.solr.common.SolrException: > undefined > > field xxx > > This sounds like the schema got updated to add the referenced field, but > some or all of the cores were never reloaded. So when you do the core > reload (or restart Solr), it's good on that core, but not on a core that > didn't get reloaded. > > Whenever you make changes to the config files in ZooKeeper, you should > reload the collection. This will reload all the individual cores on > whatever servers they happen to reside on, which will cause them to > re-read the config files. > > https://lucene.apache.org/solr/guide/7_2/collections-api.html#reload > > Thanks, > Shawn >
