Being able to change the cluster name
a cluster has been in development for awhile .. but as new cluster are created within the project.. we'd like to change the cluster name ..
I'm Desmond, the DBA at LIVE17, a long-term partner of Mongo. From a cloud SaaS operations perspective, I strongly recommend enabling the 'Cluster Rename' feature. This recommendation goes beyond just the convenience of switching from -dev or - test to prod mode without the need to move a large amount of data.
We understand that changing the cluster name affects the Cluster endpoint. In situations where we want to quickly recover from a disaster, we opt to restore a new cluster (e.g., MongoDB-bak) from the most recent snapshot. If the Cluster Rename feature is available, we won't need to spend extra time modifying API endpoints or any DNS Route53 settings. We can utilize the Cluster Rename feature to switch the Cluster endpoint, minimizing downtime.
This function has been present in AWS RDS for quite some time, significantly reducing the complexities of cloud SaaS operations. We believe MongoDB's goal is also to address the frequent data migration challenges during development.
@Andrew Davidson - for what it's worth, I'd be happy to just be able to change the name displayed on the Atlas web dashboard. As a startup, we often run into situations where we realize having different database deployments makes more sense than having different collections. Being able to rename the cluster (or at least the displayed label) would provide a much more flexible experience.
We've gone back and forth on this one: One advantage of our cluster naming has been that the name shows up in the connection string (hostnames) of the cluster, which has convenience benefits. However this makes it more difficult to enable a naming change. If the name were purely a control plane metadata tag, then making the name change would make perfect sense. Still, we will explore options over time.
Can you shed some light on the value/use case of this for you? We know many customers start out with "-dev" or "-test" in cluster names and those may eventually become prod envs--that's a use case that's top of mind for us. Are there others?