[jira] [Closed] (IGNITE-8993) Configuring sticky LoadBalancer for Ignite Service with Kubernetes

["Denis Magda (JIRA)" <ji...@apache.org>]

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

Denis Magda closed IGNITE-8993.
-------------------------------

> Configuring sticky LoadBalancer for Ignite Service with Kubernetes
> ------------------------------------------------------------------
>
>                 Key: IGNITE-8993
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8993
>             Project: Ignite
>          Issue Type: Task
>          Components: documentation
>            Reporter: Denis Magda
>            Assignee: Denis Magda
>            Priority: Major
>             Fix For: 2.7
>
>         Attachments: ignite-service.yaml
>
>
> Ignite service used for Ignite pods auto-discovery and access to the cluster from remote applications is deployed as LoadBalancer:
> https://apacheignite.readme.io/docs/ignite-service
> This might lead to problems when a stateful session is needed between an app and the cluster. For instance, Ignite JDBC driver preserves the state of an opened connection meaning that once LoadBalancer connects the driver to an Ignite pod, all the queries have to be redirected to that Ignite pod only (unless the pod is down).
> We need to show how to configure a sticky LoadBalancer that will assign a client connection to a specific pod and won't change it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)