Identifying All CLDB Nodes
Explains how you can identify all the CLDB nodes in an HPE Ezmeral Data Fabric.
Some procedures in this guide require you to find all the container location database (CLDB) nodes in your fabric.
CLDB Nodes in Cloud-Based Fabrics
In AWS, Azure, and GCP deployments of the Data Fabric, ALL nodes are CLDB nodes because fabric creation configures every node as a CLDB node.
CLDB Nodes in On-Premises Fabrics
In an on-premises deployment, not all nodes are necessarily CLDB nodes. To identify if a node is a CLDB node, ssh into the node asroot
or the Data Fabric
admin
user, and issue the following
command:maprcli node list -columns svc,ip
A node is a CLDB node if the
service list includes cldb
as one of the
services:maprcli node list -columns hostname,csvc
hostname ip configuredservice
mynode67213.mycompany.net 10.163.167.293 keycloak,s3server,cldb,ezotelcol,nfs4,collectd,hoststats,data-access-gateway,fileserver,mastgateway,opentsdb,gateway,apiserver
mynode67214.mycompany.net 10.163.167.294 keycloak,s3server,cldb,ezotelcol,nfs4,collectd,hoststats,data-access-gateway,fileserver,mastgateway,opentsdb,gateway,apiserver
mynode67215.mycompany.net 10.163.167.295 keycloak,s3server,cldb,ezotelcol,nfs4,collectd,hoststats,fileserver,mastgateway,opentsdb
To
find the primary CLDB:
maprcli node cldbprimary
cldbprimary
ServerID: 5525564767900681920 HostName: mynode167215.mycompany.net