CA 10 Container set up

[Deactivated User]

We have started working with the containerized versions of the API Gateway. We are working through one issue after another, our latest issue seems straightforward enough errors with intra node communication: The error is below, apparently the nodes are expecting port 8777 to be open between nodes. Because this is containerized we have to map this port from the container to the OS, we can do this in the configuration,
api-gateway4_1  | 2021-06-15T14:23:34.905+0000 WARNING 126    com.hazelcast.internal.cluster.impl.ClusterHeartbeatManager: [172.19.0.2]:8777 [gateway] [3.12.5] This node does not have a connection to Member [172.22.0.2]:8777 - 4a979ed6-caea-4b3a-b4c5-2fc36152aefc
h

[Deactivated User]

Looks like this is most likely related to many docker container in the cluster_info database that are orphaned

in you mysql run the following command
1. use ssg;
2. select * from cluster_master;
3. select * cluster_info;
4. select * from cluster_info where nodeid in (select nodeid from cluster_master);

Most likely your node started is not matching with the cluster master (specially if this is just a single container that keep starting). You may want to  comapare the node id with the master node id



Finally in your when you start your docker-compose just use the 

docker-compose -f dc_gw.yaml -p <project name> up -d -- to ensure you gateway cluster are created in the same stack when you join and other command


Hope this help..

------------------------------
Pre-Sales Consultant
CA Southern Africa
------------------------------