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 som
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 clus
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 repr
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 sho
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 cluste
opy operation wasn't successful.
> BestMoritz
>
>
>
> _
> From: Michael Kuhlmann
> Sent: Donnerstag, Juni 22, 2017 2:50 PM
> Subject: Re: Error after moving index
> To:
>
>
> Hi Moritz,
>
> did you stop your local Sol
essful.
> BestMoritz
>
>
>
> _
> From: Michael Kuhlmann
> Sent: Donnerstag, Juni 22, 2017 2:50 PM
> Subject: Re: Error after moving index
> To:
>
>
> Hi Moritz,
>
> did you stop your local Solr sever before? Copying dat
cessful.
BestMoritz
_
From: Michael Kuhlmann
Sent: Donnerstag, Juni 22, 2017 2:50 PM
Subject: Re: Error after moving index
To:
Hi Moritz,
did you stop your local Solr sever before? Copying data from a running
instance may cause headaches.
BestMoritz
_
From: Michael Kuhlmann
Sent: Donnerstag, Juni 22, 2017 2:50 PM
Subject: Re: Error after moving index
To:
Hi Moritz,
did you stop your local Solr sever before? Copying data from a running
instance may cause headaches.
If
Hi Moritz,
did you stop your local Solr sever before? Copying data from a running
instance may cause headaches.
If yes, what happens if you copy everything again? It seems that your
copy operations wasn't successful.
Best,
Michael
Am 22.06.2017 um 14:37 schrieb Moritz Munte:
> Hello,
>
>
>
>
Hello,
I created an index on my local machine (Windows 10) and it works fine there.
After uploading the index to the production server (Linux), the server shows
an error:
java.util.concurrent.ExecutionException:
org.apache.solr.common.SolrException: Unable to create core
[contentselect_v3]
On 9/27/07, Jae Joo <[EMAIL PROTECTED]> wrote:
> I do need to move the index files, but have a concerns any potential problem
> including performance?
> Do I have to keep the original document for querying?
I assume you posted XML documents in Solr XML format (like ...)?
If so, that is just an exa
Hi,
I do need to move the index files, but have a concerns any potential problem
including performance?
Do I have to keep the original document for querying?
Thanks,
Jae Joo
15 matches
Mail list logo
