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

• Type: Improvement
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.8
• Fix Version/s: 2.9
• Component/s: networking
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Ivan Bessonov
• Reporter: Denis A. Magda
• Created: 15/May/20 05:01
• Updated: 01/Sep/20 14:09
• Resolved: 14/Aug/20 13:04

Description

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

Issue Links

• is part of: IGNITE-12438 Extend communication protocol to establish client-server connection
• links to: GitHub Pull Request #8074
• links to: GitHub Pull Request #8199