#community-help

Cloning a Cluster and Progress on a GitHub Issue

TLDR Shaun asked about cloning an existing cluster and inquired about progress on a GitHub issue. Jason suggested exporting/importing data and provided a timeline for the issue resolution.

5mo

Join the chat

Apr 18, 2023 (5 months ago)

Photo of md5-9dd01dbbef7bac5e85a472a52dc35647

Shaun

07:21 AM

hey guys, is there a way to clone/copy an existing cluster to another? Our development cluster is up and would like to make a copy into a newly provisioned one for production data. Or is the only way to re-create each collection manually and then push the data from the production source DB?

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

07:22 AM

You could use the documents/export endpoint to export data from one collection and import it into another using the documents/import endpoint

07:22

Jason

07:22 AM

But in general, syncing from your primary data store would be the most ideal since that has the latest copy of the data

Shaun

07:23 AM

gotcha

07:23

Shaun

07:23 AM

and just create each schema manually in the new cluster ?

Jason

07:24 AM

Preferably programmatically via a script, so it’s version-controlled, etc

Shaun

07:24 AM

yeah makes sense

07:24

Shaun

07:24 AM

ok thanks

07:52

Shaun

07:52 AM

Diff question - hows progress on https://github.com/typesense/typesense/issues/229 going ? Would be a game changer when completed 😄

Jason

03:53 PM

We started work on it, but paused as other higher priority items came up. We’ll be resuming work on it in a month or so.

Apr 19, 2023 (5 months ago)

Shaun

01:57 AM

ok cool, thanks for the update

01:57

Shaun

01:57 AM

I think this will be one of the best features you can add in terms of power it will give to the entire system - eagerly awaiting 😄

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 2776 threads (79% resolved)

Join Our Community Manage subscription

Similar Threads

Cloning and Backups in Typesense Cloud

Muhamed asked about cloning and backups in Typesense Cloud. Jason clarified cloning methods and confirmed that backups were handled by Typesense Cloud.

10mo

Resolving Error in Node Restore

Nelson encountered error restoring node 2. Jason provided advice on correct node data handling. Nelson resolved the problem by deleting unnecessary data and re-running the node. Kishore Nallan affirmed this solution.

25mo

Discussing Features for Typesense Cloud Dashboard

Stephano expressed the need for a Typesense Cloud dashboard to manage collections. Jason confirmed its development, also including features like editing and deleting items. James and Mica added comments about API key management and self-hosted Typesense compatibility.

30mo

Addressing Cluster Issue due to Excessive Data

Andrew had trouble with cluster operations due to excessive data and collections. Jason advised flushing the data and stated that the upcoming update will remedy such issues. Both agreed to stick to v0.19 and not to fill the cluster excessively.

33mo

Setting up a Typesense Cluster without Data Loss

The needed help setting up a Typesense cluster without data loss. Jason provided a guide and confirmed it's possible to include a node with existing data into a cluster.

21mo