Hello!
I can imagine circumstances where clients will open connections to other
clients, such as starting caches on clients or deploying services on
clients.
Regards,
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Wanted to close the loop on this, I am running in Kubernetes and the root
cause of this was a network policy blocking communications.
It seems as if in Ignite 2.6, with paired connections, I need to have an
open communication path on 47100 between all the servers, between the
servers and the
Hello!
As far as my understanding goes, ZookeeperClusterNode is not a Zookeeper
daemon but a cluster node (i.e. Apache Ignite) which is managed by
Zookeeper discovery. So it's natural that a connection will be initiated to
such node.
Modern TCP firewalls usually null route connection attempts to
The logs do not indicate any connectivity problem, unless I am missing it,
in which case please point it out to me.
The messages seem to be getting through fine, but the server thinks there
is a connection which does not exist, so it rejects it. This seems to
happen because the communication SPI
Hello!
This might happen when there's connectivity problems, i.e. when node A can
connect to node B but not vice versa.
You can also try increasing socketWriteTimeout on communicationSpi if
communication connections die mid-flight.
Regards,
--
Ilya Kasnacheev
2018-07-25 0:16 GMT+03:00
