[
https://issues.apache.org/jira/browse/IGNITE-12438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17108388#comment-17108388
]
Denis A. Magda commented on IGNITE-12438:
-----------------------------------------
Ivan, thank you!
As this task's description suggests, a server will try to connect to a client
anyway through communication SPI before requesting the client (via a discovery
message) to establish a connection with the server instead. It means that the
client should create a server socket even for EnvironmentType.VIRTUALIZED. At
least that was my understanding. The issue described in
[IGNITE-13013|https://issues.apache.org/jira/browse/IGNITE-13013] is about the
cases when the server must not even try to connect to the client and the client
must not open the server socket. Actually, that's the case for this bullet item
of this ticket_ (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_
I'll leave it up to you, you can close IGNITE-13013 and fix the issue as part
of this task. Or you can IGNITE-13013 as a sub-task and track those cases
separately.
> 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
> Assignee: Ivan Bessonov
> Priority: Major
> Fix For: 2.9
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> 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)
