Glad to hear it. Now, if you want to be really bold (and I haven’t verified it,
but it _should_ work).
Rather than copy the index, try this:
1> spin up a one-replica empty collection
2> use the REPLICATION API to copy the index from the re-indexed source.
3> ADDREPLICAs as before.
<2> looks
Thanks so much - your approaches worked a treat!
Best,
Kevin.
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Hi all,
I'm sure I've done this before but this seems to be falling down a bit and I
was wondering if anyone had any helpful ideas.
I have a large index (51GB) that exists in a 4 node Solr Cloud instance. The
reprocessing for this takes a long time and so we normally reindex on a
secondary
On 4/8/2019 10:06 AM, Shawn Heisey wrote:
* Make sure you have a copy of the source index directory.
* Do not copy the tlog directory from the source.
* Create the collection in the target cloud.
* Shut down the target cloud completely.
* Delete all the index directories in the cloud.
* Copy the
On 4/8/2019 8:59 AM, kevinc wrote:
I have reindexed to a single Solr 6.6.0 index and spun up a new 3 node Solr
cluster with 1 shard and replication factor of 3.
I want to copy over the index and have it replicate to the rest of the
cluster. I have taken a copy of the data directory from the
Here’s what I’d do:
1> Just spin up a _one_ node cluster and copy the index from your offline
process and start Solr. I’l probably do this with Solr down.
2> Use the ADDREPLICA command to build out that cluster. The index copy
associated with ADDREPLICA is robust. I’d wait until each replica
Hi all,
I'm sure I've done this before but this seems to be falling down a bit and I
was wondering if anyone had any helpful ideas.
I have a large index (51GB) that exists in a 4 node Solr Cloud instance. The
reprocessing for this takes a long time and so we normally reindex on a
secondary
