[
https://issues.apache.org/jira/browse/SOLR-8027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761094#comment-17761094
]
Shawn Heisey commented on SOLR-8027:
------------------------------------
With more time to think about this, I don't know that we actually need the
ability to _convert_ an existing install. Unless we provide a fully automated
way to do it, I think the process is perhaps more complicated than we want to
try to document.
One thing we might want to do is provide instructions for *migrating* an index
to SolrCloud with these steps:
* Create cluster and a collection with one shard.
* Shut down all Solr servers in the cluster.
* Copy the index directory from the standalone install to one of the replica
shards.
* Delete any existing tlog directory on that replica.
* Start that replica.
* Delete the index and tlog directories on the other replicas.
* Start the remaining replicas one at a time.
That should include some notes:
* Reindexing from scratch is the *preferred* way to migrate.
* This will only work migrating to a collection with one shard.
> 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
> Priority: Major
>
> 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
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
