Re: S3 discovery and bridge networks

Hello! Can you have a virtual network containing all of your nodes, so that their internal addresses will work? I have to admit I'm not a devops so I don't know any more specifics. Regards, -- Ilya Kasnacheev 2018-08-07 17:07 GMT+03:00 Dave Harvey : > My understanding: S3 discovery works

Re: S3 discovery and bridge networks

My understanding: S3 discovery works because the container publishes its IP/port in an S3 bucket, and other nodes can read this to determine which nodes might be in the cluster. When running in a container using a bridge network, the container does not know the external IP address that can be

Re: S3 discovery and bridge networks

Hello! Have you tried to specify localAddress for communication and discovery SPIs? If not, can you please elaborate with ifconfig information and stuff? Regards, -- Ilya Kasnacheev 2018-08-03 16:53 GMT+03:00 Dave Harvey : > I've been successfully running 2.5 on AWS ECS with host or AWSVPC >

S3 discovery and bridge networks

I've been successfully running 2.5 on AWS ECS with host or AWSVPC networking for the Ignite containers. Is there any way around the fact that with bridge networking, the Ignite node registers it's unmapped address on S3? Disclaimer The information contained in this communication from the