There’s also the Collections API MOVEREPLICA command that does this all as a
single command.
> On Nov 19, 2019, at 5:21 AM, Sripra deep wrote:
>
> Got it, Thanks for helping me Emir.
>
> On Tue, Nov 19, 2019 at 12:36 PM Emir Arnautović <
> emir.arnauto...@sematext.com> wrote:
>
>> Hi,
>> Copy
Got it, Thanks for helping me Emir.
On Tue, Nov 19, 2019 at 12:36 PM Emir Arnautović <
emir.arnauto...@sematext.com> wrote:
> Hi,
> Copying indices will work and it is a fine approach. An alternative would
> be to join new node to a cluster, use add replica to copy cores to this new
> node and th
Hi,
Copying indices will work and it is a fine approach. An alternative would be to
join new node to a cluster, use add replica to copy cores to this new node and
then remove replicas from old nodes, if you want to move cores.
Regards,
Emir
--
Monitoring - Log Management - Alerting - Anomaly Det
Hi Emir,
Thank you so much. Now I got it cleared with the TLOG purpose.
I am trying to copy an index of one solr cluster to use it to build
other solr cluster. I am able to make that work but Is this design okay? or
any other approach I can try to get a new cluster spin up with the same
data
Hi Sripradeep,
Simplified: TLog files are used to replay index updates from the last
successful hard commit in case of some Solr crashes. It is used on the next
Solr startup. It does not contain all updates, otherwise, it would duplicate
the index size.
If you start from these premises, you will
Hi Guys,
I observed a scenario with the tlog creation and usage and couldn't find
any usage for the tlog.
Solr version: 7.1.0
Number of shards = 3
Number of replica = 1
I indexed the about 10k docs into the collection.
Scenario 1:
Using add replica collection API, I created one more replica
