[
https://issues.apache.org/jira/browse/SOLR-8027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739595#comment-14739595
]
Shawn Heisey commented on SOLR-8027:
------------------------------------
bq. Of course, all this assuming you couldn't just re-index fresh ;)
That would definitely be the preferred way, and the first thing I hope the docs
mention.
I guess we'd need to decide whether the goal would be to get the conversion
done first, or to set up a fully fault-tolerant cloud first ... the former
would very likely be a lot easier, but I'd argue that the latter is much more
useful for a production install.
Thanks for looking!
> Reference guide instructions for converting an existing install to SolrCloud
> ----------------------------------------------------------------------------
>
> Key: SOLR-8027
> URL: https://issues.apache.org/jira/browse/SOLR-8027
> Project: Solr
> Issue Type: Improvement
> Components: documentation
> Reporter: Shawn Heisey
>
> I have absolutely no idea where to begin with this, but it's a definite hole
> in our documentation. I'd like to have some instructions that will help
> somebody convert a non-cloud install to SolrCloud. Ideally they would start
> with a typical directory structure with one or more cores and end with cores
> named foo_shardN_replicaM.
> As far as I know, Solr doesn't actually let non-cloud cores coexist with
> cloud cores. I once tried to create a non-cloud core on a cloud install, and
> couldn't do it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
