CLOSED – I resolved the issue by using cbbackup to store my bucket data, then I uninstalled and re-installed couchbase on a new server with a unique DNS name and re-loaded the data.
Hi, I recently created a couchbase cluster out of two nodes. Before this I was able to start and stop my original node server without any issues even though it was a VM and the IP address would change everytime it was restarted. I recently had to restart both nodes and now couchbase won’t start on either of them. Is there anyway I can fix this without losing all my data? It’s a dev server so technically I don’t lose anything important, but a lot of people in my company use it and if I can save the data it would be nice. E.g. if I can remove the new node from the cluster without couchbase server being started so that my original node can start up normally like it did before.
I saw the documentation for couchbase in the cloud (after having this problem and searching it up, it would be really great for future users if you mentioned this issue in the install instructions so that people would know about it when configuring their servers) that mentions using DNS names instead of IP addresses. I’m using Azure and a load balancer, so both my nodes are behind the same DNS name. I can specify a port number per node, but that’s it. Is there any other way to solve this issue without having to have individual DNS names per node?