Remove duplicate storage cluster with LCM
When you configure a separate storage cluster for metrics, the OpsCenter keyspace is recreated on the storage cluster. Because the OpsCenter UUID changes, you will see duplicate clusters in LCM. To remove the duplicate cluster in Lifecycle Manager (LCM), resync the OpsCenter cluster UUID.
In OpsCenter 6.8.1 and later, LCM finds the OpsCenter cluster by its UUID first and then the intersecting seed list. This improvement prevents LCM from listing a duplicate cluster. |
-
Create a unique keyspace to use for each DSE cluster monitored by OpsCenter. If you are storing data for multiple clusters, DataStax recommends adding the cluster name as a suffix to the default keyspace name of
OpsCenter
. For example, set the keyspace name toOpsCenter_Cluster1Storage
for the storage cluster to differentiate it from the OpsCenter keyspace for the monitored cluster. -
Get the unique_cluster_id for the OpsCenter storage cluster.
curl http://127.0.0.1:8888/cluster_name/cluster/unique_cluster_id
"unique_cluster_id"
-
Get a list of LCM clusters to get the unique
opsc-cluster-id
andhref_URL
for the LCM cluster:curl http://127.0.0.1:8888/api/v2/lcm/clusters/
{ "next": null, "previous": null, "last": 1, "count": 1, "per-page": 50, "current": 1, "results": [ { "opsc-cluster-id": "opsc_cluster_id", "name": "cluster_name", "id": "id", "href": "href_URL", ... } ] }
-
If
opsc-cluster-id
andunique_cluster_id
don’t match, replace theopsc-cluster-id
value with theunique_cluster_id
using the LCM cluster’shref_URL
:curl -X PUT href_URL -H "Content-Type: application/json" -d '{"opsc-cluster-id": "unique_cluster_id"}'
If the OpsCenter and LCM cluster UUIDs match and you have duplicate clusters, contact DataStax Support.
-
Refresh the LCM web-interface.
The duplicate cluster should no longer be visible.
-
Remove the duplication from the
db_monitoring
cluster:-
Get the
unique_cluster_id
fromdb_monitoring
cluster.curl http://127.0.0.1:8888/db_monitoring/cluster/unique_cluster_id
"6885d453-a816-4c9e-b06f-7050d28c50b5"
-
Get the unique
opsc-cluster-id
andhref_URL
for thedb_monitoring
LCM cluster.curl http://127.0.0.1:8888/api/v2/lcm/clusters/
{ "next": null, "previous": null, "last": 1, "count": 1, "per-page": 50, "current": 1, "results": [ { "opsc-cluster-id": "f1da1420-7846-4c84-bf7d-399d48e6a51e", "name": "db_monitoring", "id": "cd658793-e763-4e5a-9960-b19fe935f0db", "href": "http://127.0.0.1:8888/api/v2/lcm/clusters/cd658793-e763-4e5a-9960-b19fe935f0db", ... } ] }
-
Replace the
opsc-cluster-id
value with theunique_cluster_id
:curl -X PUT href_url -H "Content-Type: application/json" -d '{"opsc-cluster-id": "unique_cluster_id"}'
Verify that the
opsc-cluster-id
is now set to the value of theunique_cluster_id
in the response:{ "opsc-cluster-id": "6885d453-a816-4c9e-b06f-7050d28c50b5", "name": "db_monitoring", "id": "cd658793-e763-4e5a-9960-b19fe935f0db", "href": "http://127.0.0.1:8888/api/v2/lcm/clusters/cd658793-e763-4e5a-9960-b19fe935f0db", ... }
-