Re: Zookeeper discovery in mix environments.

We know that host mode works, that's too easy... And I said that already works no problem. So the client is running in Dokcer on bridge mode. It binds to some internal docker I.P 172.18.xxx.xxx That can also be easily seen with Visor. So in bridge mode it means we need to map some external I.P +

Re: Zookeeper discovery in mix environments.

Limit your env to two nodes. Try using --net=host for docker containers. If that works, limiting to use setLocalHost for TcpCommunicationSPI, and configure ZooKeeper to use address translation/or bind to a specific address. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Zookeeper discovery in mix environments.

I think the problem might also, be the client is running inside DC/OS with docker containers. When I check the network topology all connected aplication are reporting multiple addresses... Here is an example of a single client... Is it possible to tell it only bind to one or only use one?

Re: Zookeeper discovery in mix environments.

In terms of TcpCommunicationSPI it might help: https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/spi/communication/tcp/TcpCommunicationSpi.html#setLocalAddress-java.lang.String- Also look into setting the localaddress:

Re: Zookeeper discovery in mix environments.

Would address resolver work here with Zookeeper discovery? I think most of my communications erros are due to my clients binding to multiple addresses?

Re: Zookeeper discovery in mix environments.

It is possible. All discovery communication is through ZooKeeper, but yes private docker IPs (172.. ) might be leaked over. Would need to see the full logs(Ignite and Zookeper) which contain the IPs of the node and the particular one used for a given communication. Try running docker w/--net=host

Re: Zookeeper discovery in mix environments.

So, I'm guessing that the client node reports multiple I.Ps to the zookeeper so then when another node tries to connect to the client node to create the full mesh maybe it connecting to the wrong I.P? On Mon, 1 Jun 2020 at 11:26, akorensh wrote: > Hi, >ZookeperDiscoverySpi > < >

Re: Zookeeper discovery in mix environments.

Hi, ZookeperDiscoverySpi uses ZooKeeper to transmit discovery messages. You can specify a comma separated host:port pairs, each corresponding to a zooKeeper server here:

Re: Zookeeper discovery in mix environments.

Maybe you would ask the question on VM/container related mailing list? Regards On Mon, Jun 1, 2020 at 9:32 PM John Smith wrote: > Any news on this? Thanks > > > On Thu., May 28, 2020, 1:10 p.m. John Smith, > wrote: > >> Hi, I'm running an ignite cluster on VMs running on Openstack and using

Re: Zookeeper discovery in mix environments.

Any news on this? Thanks On Thu., May 28, 2020, 1:10 p.m. John Smith, wrote: > Hi, I'm running an ignite cluster on VMs running on Openstack and using > regular network stack nothing special here. > > My CLIENT (client=true) applications are running in DC/OS using docker > container in bridged

Zookeeper discovery in mix environments.

Hi, I'm running an ignite cluster on VMs running on Openstack and using regular network stack nothing special here. My CLIENT (client=true) applications are running in DC/OS using docker container in bridged network mode. When using TCP discovery everything works nice and dandy. But I recently