[
https://issues.apache.org/jira/browse/IGNITE-13013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17170667#comment-17170667
]
Semyon Danilov commented on IGNITE-13013:
-----------------------------------------
I was able to validate that changes indeed fix the problem for Azure, however
it is worth mentioning that working in serverless mode with Azure or AWS
requires additional configuration.
# IGNITE_HOME must be configured to use temporary dir
# Address resolver must be configured for server node (node local address ->
node public address)
# Default timeouts of functions are really small, thick client won't be able
to start so fast
> 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
>
> Attachments: image-2020-07-30-18-42-01-266.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)
