If at all possible you shouldn't run with legacyCloud=true. I was just
mentioning that in order to see if that was the place to start
looking, I could have been clearer.
Let's back up a bit though. I just tried this creating a collection
with 6.6.0, changing to 7.1.0 and I can add replicas just
Thanks Erick, I've looked over the documentation.
Quick follow-up question:
What are the consequences of running with legacyCloud=true?
Would I need to point a new Solr cluster at a new Zookeeper instance to
avoid this?
Many thanks!
-Dave
On Mon, Oct 30, 2017 at 1:36 PM, Erick Erickson
empty clusterstate.json node. OK, you're on state format 2 (the modern
one) so that's good. No need to MIGRATESTATE
The admin UI>>cloud>>tree view should have a cluster.properties (IIRC
the name correctly, it'll be fairly obvious). If you have no
non-default values it'll be totally missing. It's
> You may have to set legacyCloud=true in your cluster properties
> Check your cluster properties (top level znode in ZooKeeper).
How would I check this? Would it appear in the Solr Cloud interface, or do
I have to query Zookeeper?
> Or, try the MIGRATESTATEFORMAT collection API on your 6x
You may have to set legacyCloud=true in your cluster properties. In
the Solr reference guide (7.0) there's a section "Changes to Default
Behaviors" that'll tell you a bit about that. Check your cluster
properties (top level znode in ZooKeeper).
Or, try the MIGRATESTATEFORMAT collection API on
I have a Solr collection with 1 shard and around 40 replicas hosted on Solr
6.6.0
I added a Solr 7.1 server to the cluster and then tried to add a replica
(ADDREPLICA) onto the new server but got this message:
> Error CREATEing SolrCore 'content_collection_20171013_shard1_replica37':
non legacy
