unov
Sent: Friday, February 9, 2018 3:54 AM
To: dev@ignite.apache.org
Subject: TcpCommunicationSpi in dockerized environment
Hello Ignite community,
When testing Ignite in dockerized environment I faced the following issue
with current TcpComminicationSpi implementation.
I had several physical
Hello Ignite community,
When testing Ignite in dockerized environment I faced the following issue
with current TcpComminicationSpi implementation.
I had several physical machines and each Ignite node running inside Docker
container had at least two InetAddresses associated with it: one IP address
