Re: Replicate managed-schema in Solr Master/Slave Configuration
https://issues.apache.org/jira/secure/Dashboard.jspa You have to create a login, but then you can raise a Solr JIRA. Please put in all the detail you can to help someone reproduce. One more thing to try: Rename your managed-schema to something like testschema.xml, and change your solrconfig as I mentioned. Then verify that changing the schema (and afterwards adding some docs to the index and committing) _does_ replicate the schema. Mostly just insuring that the only difference between successfully replicating the schema and not is the name and not something else. Best, Erick On Thu, May 31, 2018 at 7:07 PM, Kelly Rusk wrote: > 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 > Sent: Thursday, May 31, 2018 8:50 PM > To: solr-user > 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. > > > true > managed-schema > > > 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 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: >> schema.xml,managed-schema,stopwords.txt >> How can I replicate the managed-schema file if it has no file extension? >> Regards, >> Kelly >> >
RE: Replicate managed-schema in Solr Master/Slave Configuration
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 Sent: Thursday, May 31, 2018 8:50 PM To: solr-user 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. true managed-schema 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 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: > schema.xml,managed-schema,stopwords.txt > How can I replicate the managed-schema file if it has no file extension? > Regards, > Kelly >
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. true managed-schema 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 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: > schema.xml,managed-schema,stopwords.txt > How can I replicate the managed-schema file if it has no file extension? > Regards, > Kelly >
