I'm assuming you're using classic schema factory?
Do this error show up in the log correlated to your use of the
config API to configure CDCR? If so, please do three things:
1> raise a JIRA
2> paste the command you use to configure CDCR
3> paste in any more info from the ERROR in the log, especially
if there's a stack trace.
It is certainly possible that CDCR is piggy-backing on some of the
configuration code. I don't know of any CDCR tests that specifically
mix classic schema with CDCR config commands. If you'd like to
take a stab at a test case illustrating this that would be way cool.
I can easily imagine these two things not being tested together
though.
Erick
On Fri, Jan 6, 2017 at 7:15 AM, Webster Homer <webster.ho...@sial.com> wrote:
> I occasionally see this error in our logs:
> 2017-01-05 20:48:46.664 ERROR (SolrConfigHandler-refreshconf)
> [c:sial-catalog-material s:shard2 r:core_node2
> x:sial-catalog-material_shard2_replica1] o.a.s.s.IndexSchema This
> IndexSchema is not mutable.
>
> None of our indexes are mutable, nor are we trying to use the managed
> schema features.
>
> It doesn't seem to cause a problem, but I want to understand where this
> ERROR is coming from.
>
> It may be related to the use of the Config API which we use to dynamically
> set properties and to configure the CDCR Request handlers. I don't see
> anything in the Config API docs that limits its use to collections with
> managed schemas, moreover the API seems to work fine.
>
> I don't see SolrConfigHandler defined in the solrconfig.xml file
>
> We have been using the same basic schema file since Solr 3.* upgrading the
> schema and config as needed. I've only seen this error since migrating to
> Solr 6.2
>
> --
>
>
> This message and any attachment are confidential and may be privileged or
> otherwise protected from disclosure. If you are not the intended recipient,
> you must not copy this message or attachment or disclose the contents to
> any other person. If you have received this transmission in error, please
> notify the sender immediately and delete the message and any attachment
> from your system. Merck KGaA, Darmstadt, Germany and any of its
> subsidiaries do not accept liability for any omissions or errors in this
> message which may arise as a result of E-Mail-transmission or for damages
> resulting from any unauthorized changes of the content of this message and
> any attachment thereto. Merck KGaA, Darmstadt, Germany and any of its
> subsidiaries do not guarantee that this message is free of viruses and does
> not accept liability for any damages caused by any virus transmitted
> therewith.
>
> Click http://www.emdgroup.com/disclaimer to access the German, French,
> Spanish and Portuguese versions of this disclaimer.
