[jira] [Updated] (IGNITE-13013) Thick client must not open server sockets when used by serverless functions

["Aleksey Plekhanov (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-13013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksey Plekhanov updated IGNITE-13013:
---------------------------------------
    Fix Version/s:     (was: 2.9)
                   2.10

> Thick client must not open server sockets when used by serverless functions
> ---------------------------------------------------------------------------
>
>                 Key: IGNITE-13013
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13013
>             Project: Ignite
>          Issue Type: Improvement
>          Components: networking
>    Affects Versions: 2.8
>            Reporter: Denis A. Magda
>            Assignee: Ivan Bessonov
>            Priority: Critical
>             Fix For: 2.10
>
>
> A thick client fails to start if being used inside of a serverless function such as AWS Lamda or Azure Functions. Cloud providers prohibit opening network ports to accept connections on the function's end. In short, the function can only connect to a remote address.
> To reproduce, you can follow this tutorial and swap the thin client (used in the tutorial) with the thick one: https://www.gridgain.com/docs/tutorials/serverless/azure_functions_tutorial
> The thick client needs to support a mode when the communication SPI doesn't create a server socket if the client is used for serverless computing. This improvement looks like an extra task of this initiative: https://issues.apache.org/jira/browse/IGNITE-12438



--
This message was sent by Atlassian Jira
(v8.3.4#803005)