Bringing together the Apache Cassandra experts from the community and DataStax.
Want to learn? Have a question? Want to share your expertise? You are in the right place!
Not sure where to begin? Getting Started
opscenter creates duplicate cluster profiles when opscenter is restarted
example if the cluster name is POC_1 after restart it becomes POC_11
due to this change opscenter cannot pull out the POC_1 cluster details resulting in error like cluster is not configured .
Please provide a solution for this problem
This sounds like OPSC-15888, which can result in duplicate OpsCenter clusters being created when install jobs are run. This is fixed in our internal builds and should be publicly released in a 6.7.x patch within a few days.
You can workaround this by running configure jobs instead of install jobs, which is viable if you're modifying configs on an existing DSE cluster without adding nodes.
If you DO need to add new nodes, you'll have to run install jobs and delete the duplicate clusters afterward. The recommended procedure for deletion is:
Ensure that OpsCenter is not in the middle of any long-running operations you don’t want to interrupt, like an almost finished repair or backup.
Stop Opscenter: sudo service opscenterd stop
Delete the extra cluster config files from /etc/opscenter/clusters or the relevant location. For example, if you files named “my_cluster.conf” “my_cluster1.conf” “my_cluster2.conf”, you'll want to delete the copies that have numbers in their filename.
When you refresh the UI opscenter and lcm should only show the single cluster again.
2 People are following this question.
