Alexey Goncharuk created IGNITE-12438:
-----------------------------------------
Summary: Extend communication protocol to establish client-server connection
Key: IGNITE-12438
URL:
https://issues.apache.org/jira/browse/IGNITE-12438 Project: Ignite
Issue Type: Improvement
Reporter: Alexey Goncharuk
Recently there was quite a lot of questions related to thick clients connectivity issues when the clients are deployed in a k8s pod [1]. The general issue here is clients reporting network address which are not reachable from server nodes. At the same time, the clients can connect to server nodes.
An idea of how to fix this is as follows:
* Make sure that think clients discovery SPI always maintains a connection to a server node (this should be already implemented)
* (Optionally) detect when a client has only one-way connectivity with the server nodes. This part should be investigated. We need this to avoid server nodes attempt to connect to a client and send communication request to the client node faster
* When a server attempts to establish a connection with a client, check if client is unreachable or the previous connection attempt failed. If so, send a discovery message to the client to force a client-server connection. In this case, server will be able to send the original message via the newly established connection.
[1]
https://stackoverflow.com/questions/59192075/ignite-communicationspi-questions-in-paas-environment/59232504--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Locked
