Streams marked orphan and deleted when converting standalone to cluster #7831
Replies: 2 comments 10 replies
-
|
Standalone single-server is different from clustered deployments and can't be migrated in place like that. You'll likely need to take a backup of your streams and then restore them in the clustered setup. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @MauriceVanVeen, I’d like to propose adopting orphan streams specially for R1 streams on orphans check while running in cluster mode. Ideally, a stream created in standalone mode should behave similarly to a backup/restore in a clustered setup. At the very least, the server should attempt to bring up any resources that are still valid. I’ve put together a small PR for this change and tested it locally. It seems to be working. Would you be open to reviewing the PR? Since this discussion already was open, I didn’t open a new issue. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello Team,
I'm currently running NATS JetStream in standalone mode across multiple datacenters and need to migrate these deployments to cluster mode for high availability.
I had expected that updating the configuration to cluster mode would allow me to:
However, when I restart NATS with the cluster configuration, the existing streams are immediately marked as orphaned and automatically deleted before I have any opportunity to update their replica counts. This results in complete data loss.
Questions:
I'm looking for a solution that doesn't require manual backup and restore operations, as we have deployments across multiple datacenters where this approach would be operationally challenging.
Any guidance on how to achieve this migration while preserving existing data would be greatly appreciated.
Beta Was this translation helpful? Give feedback.
All reactions