[
https://issues.jboss.org/browse/TEIIDSB-64?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIIDSB-64:
---------------------------------------
On sticky routes. According to the docs they are sticky by default. The only issue is if
there is another load-balancer in front of the router in which the source ip is the same
for all requests and all traffic is routed to a single pod. The only way around that
limitation is to use a different strategy and cookies - which could be done for odata, but
not pg/jdbc.
Research HA
-----------
Key: TEIIDSB-64
URL:
https://issues.jboss.org/browse/TEIIDSB-64
Project: Teiid Spring Boot
Issue Type: Quality Risk
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Major
Teiid's pg, and jdbc assume session affinity. Also OData pagination works best with
session affinity.
For HA, and horizontal scaling, it would be good to have more than 1 pod alive and
receiving traffic. It appears that there is a sessionAffinity setting at a service level
https://kubernetes.io/docs/concepts/services-networking/service/ and some work that can be
done to customize routes
https://docs.openshift.com/container-platform/3.9/architecture/networking...
- but that doesn't appear to work for just tcp traffic.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)