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?
----------+
| xxx.xxx.0.17 | 1: xxxx(@n1) | xxxx | Client | Linux amd64
3.10.0-862.14.4.el7.x86_64 | 2 | xxxx | 1.00 % |
| xxx.xxxx.0.1 | |
| | | | xxxxxx |
|
| xxx.xxx.100.1 | |
| | | | xxxxxx |
|
| xxx.xxx.100.2 | |
| | | | xxxxxx |
|
| 127.0.0.1 | |
| | | | xxxxxx |
|
| xxx.xxx.xxx.68 | |
| | | | xxxxxx |
|
| xxx.xxx.0.1 | |
| | | |
| |
| xxx.xxx.xxx.129 | |
| | | |
| |
| xxx.xxx.100.3 | |
| | | |
| |
+--------------------+------------------+--------------------------------------+-----------+----------------------------------------+------+-------------------
On Mon, 8 Jun 2020 at 17:02, akorensh <[email protected]> wrote:
> 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:
>
> https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/spi/communication/tcp/TcpCommunicationSpi.html#setLocalAddress-java.lang.String-
>
> Doc for tcp communication spi:
> https://apacheignite.readme.io/docs/network-config#tcpcommunicationspi
>
>
>
> In your case, Discovery Communcation is using ZooKeeper to exchange
> messages, and therefore you would need to configure ZooKeeper if you would
> like address resolution.
>
> Ignite class ZookeperClient is a wrapper around the native ZooKeeper class
> which handles all communication.
>
> ZookeperClient wrapper class:
>
> https://github.com/apache/ignite/blob/master/modules/zookeeper/src/main/java/org/apache/ignite/spi/discovery/zk/internal/ZookeeperClient.java
>
>
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
