Validating a Mashery Local Cluster

  1. Run the following command to check if the correct number of containers have been created. If the number of NoSQL containers is greater than 1, then one will be created as seed node and remaining as nonseed. 
    docker service ls
    Sample output:

  2. You can also get the placement of containers node wise by running the following command. 
    docker node ps $(docker node ls -q) --filter desired-state=Running | uniq
    Sample output:

  3. To examine the current state of the cluster, go the CM container. Make note of the node where the Cluster Manager is deployed. You can open another terminal and configure Docker client to talk to that node. If tml-cm container is deployed on node-1, then open a new terminal and run below commands in sequence. 
    1. eval "$(docker-machine env node-1)"
    2. docker ps
    3. docker exec -it <cm container id> /bin/bash
    4. You will see the list of commands you can execute within the container. Here is a common set of commands you may want to use: 
1. [root@51ffa1197313 builder]# alias cm=clustermanager
 
2. [root@51ffa1197313 builder]# cm ls clusters
Cluster ID                            Cluster Name       
------------------------------------- --------------------
b353e255-4ea6-4403-af2d-2c5e72ccc2f4  Tibco Mashery Loc...
 
3. [root@51ffa1197313 builder]# cm use cluster b353e255-4ea6-4403-af2d-2c5e72ccc2f4
Using cluster [Tibco Mashery Local Reference Cluster]
 
4. [root@51ffa1197313 builder]# cm ls zones
Using cluster [Tibco Mashery Local Reference Cluster]
Zone ID                               Zone Name          
------------------------------------- --------------------
c70f8e9f-d65d-44b7-8569-2523fd66998d  local              
 
 
5. [root@51ffa1197313 builder]# cm use zone c70f8e9f-d65d-44b7-8569-2523fd66998d
Using cluster [Tibco Mashery Local Reference Cluster]
Using Zone [local]
 
 
 
6. [root@51ffa1197313 builder]# cm ls components
Using cluster [Tibco Mashery Local Reference Cluster]
Using Zone [local]
Component ID                          Component Type       Component Name       Component Status     Component Host       Component Agent Port   Component Service Port(s) 
------------------------------------- -------------------- -------------------- -------------------- -------------------- ---------------------- ---------------------------
adbd4a21-fc67-4b6d-ad5b-b2123fffa2b5  cache                cache                ACTIVE               x.x.4.17            9080                   11212,11211,11213,11214,11215,11216
2c93a8cf-b117-463a-8ea7-4cac8cf3ce00  configmanager        cm                   ACTIVE               x.x.4.11            9080                   8080                      
4dc48599-2033-4b9d-a73c-e900c4a93d92  logservice           log                  ACTIVE               x.x.4.13            9080                   24224                     
349d9f08-a336-47c0-b3eb-21809b15a26a  nosql                nosql                ACTIVE               x.x.4.7             9080                   9042                      
dbe59546-ad38-410f-8fd9-44e8ea91328f  nosql                nosql                ACTIVE               x.x.4.5             9080                   9042                      
60f4e5a8-8daf-4cc7-9fa3-49d1d5337d44  platformapi          api                  ACTIVE               x.x.4.9             9080                   8080                      
4c02d916-6342-4e52-9d29-58f1f47e6530  sql                  sql                  ACTIVE               x.x.4.15            9080                   3306                      
8e93db9d-d701-45f3-aebc-64a33233117b  trafficmanager       tm                   ACTIVE               x.x.4.19            9080                   8080