On 1/30/2019 3:36 PM, Bharath Kumar wrote:
Thanks Erick. We cleanup the zookeeper state on every installation, so the
zookeeper states are gone. So what should we do in case of a new 7.6
installation where we want to manually create core.properties and use the
non-legacy cloud option? Is it in order to use non-legacy cloud, we should
use the collections api to create a collection first and then use the
manual core.properties for auto-discovery?
*ALL* creations and modifications to SolrCloud collections should be
done using the Collections API. Creating cores directly (either with
core.properties or the CoreAdmin API) is something that will almost
certainly bite you hard. Based on what Erick has said, I don't think
you can even do it at all when legacy mode is disabled. Even when you
can ... don't.
Because in the legacy cloud mode we were just creating the core.properties
manually and that would update the zookeeper state when the solr boots up.
Can you please help me with this?
Use the Collections API. This is the recommendation even for experts
who really know the code. Creating cores manually in ANY SolrCloud
install is a recipe for problems, even in legacy mode.
There is a very large warning box (red triangle with an exclamation
point) in this section of the documentation:
https://lucene.apache.org/solr/guide/7_6/coreadmin-api.html#coreadmin-create
One of the first things it says there in that warning box is that the
CoreAdmin API should not be used in SolrCloud. Manually creating
core.properties files and restarting Solr is effectively the same thing
as using the CoreAdmin API.
Thanks,
Shawn
