BTW, my purpose in suggesting you remove managed schema is just to insure that
you’re really using classic. Solr will blow up because it’s unable to find
managed-schema if, for some strange reason, you’re really using managed.
The two can exist perfectly well together, one should be used and one
Thanks Erick.
I have removed the managed-schema for now. This setup was running perfectly
for couple of years. I implemented basic auth around the collection a year
back. But nothing really changed on my process to update the schema. Let me
see if removing managed-schema has any impact and will up
Then something sounds wrong with your setup. The configs are stored in ZK, and
read from ZooKeeper every time Solr starts. So how the replica “does not have
the correct schema” is a complete mystery.
You say you have ClassicIndexSchemaFactory set up. Take a look at your configs
_through the Adm
Hi,
I also observed that whenever the JVM crashes, the replicas does not have
the correct schema. Anyone seen similar behavior.
Thanks,
AA
On Wed, Sep 4, 2019 at 9:58 PM Antony A wrote:
> Hi,
>
> I have confirmed that ZK ensemble is external. Even though both
> managed-schema and schema.xml ar
Hi,
I have confirmed that ZK ensemble is external. Even though both
managed-schema and schema.xml are on the admin ui, I see the below class
defined in solrconfig.
The workaround is till to run "solr zk upconfig" followed by restarting the
cores of the collection. Anything else I should be looki
This almost always means that you really _didn’t_ update the schema and reload
the collection, you just thought you did ;).
One common reason is to fire up Solr with an internal ZooKeeper but have the
rest of your collection be using an external ensemble.
Another is to be modifying schema.xml w
Hi,
I ran the collection reload after a new "leader" core was selected for the
collection due to heap failure on the previous core. But I still have stack
trace with common.SolrException: undefined field.
On Thu, Aug 29, 2019 at 1:36 PM Antony A wrote:
> Yes. I do restart the cores on all the d
Yes. I do restart the cores on all the different servers. I will look at
implementing reloading the collection. Thank you for your suggestion.
Cheers,
Antony
On Thu, Aug 29, 2019 at 1:34 PM Shawn Heisey wrote:
> On 8/29/2019 1:22 PM, Antony A wrote:
> > I do restart Solr after changing schema u
On 8/29/2019 1:22 PM, Antony A wrote:
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?
Did you restart all the Solr servers? If the colle
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 wrote:
> On 8/29/2019 11:26 AM, Antony A wro
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 th
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 th
12 matches
Mail list logo
