Thanks Erick,

I have made changes on the Master/indexing that are replicated to the Slave and 
the managed-schema does not come over. Sounds like a JIRA entry may be in 
order. How do I go about doing that? I am not using ConfigSets as each Core has 
its own unique Schema.

Regards,

Kelly

-----Original Message-----
From: Erick Erickson <erickerick...@gmail.com> 
Sent: Thursday, May 31, 2018 8:50 PM
To: solr-user <solr-user@lucene.apache.org>
Subject: Re: Replicate managed-schema in Solr Master/Slave Configuration

On a quick glance at the code, I don't see anything requiring an xml extension 
for the managed schema. I suppose it's possible that the hyphen is messing 
things up.

You should see a message like:

"Adding config files to list: " ......  on replication if you turn on 
debug-level logging.

At worst, you could change the _name_ of your schema by changing solrconfig.xml 
like below.

<schemaFactory class="ManagedIndexSchemaFactory">
    <bool name="mutable">true</bool>
    <str name="managedSchemaResourceName">managed-schema</str>
  </schemaFactory>

But I'll emphasize that you should _not_ have to do this from a quick code 
inspection. Have you changed your index since changing the managed schema? 
Replication doesn't do anything unless the index on the master is changed 
relative to the slave.

And are you using configsets?

If the schema has changed _and_ you see a replication happens (i.e.
new docs appear on the slaves) _and_ the managed-schema still isn't replicated, 
that would merit a JIRA.

Best,
Erick

On Thu, May 31, 2018 at 3:35 PM, Kelly Rusk <kelly.r...@rackspace.com> wrote:
> Hello all,
> I need to replicate the managed-schema in my Solr 6.6.2 Master/Slave 
> environment and have added the necessary replication handlers. However, as 
> the managed-schema does not have a file extension it doesn't seem to get 
> picked up/replicated:
> <str name="confFiles">schema.xml,managed-schema,stopwords.txt</str>
> How can I replicate the managed-schema file if it has no file extension?
> Regards,
> Kelly
>

Reply via email to