October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-249) sessionAffinity doesn't cause a requests from a same IP to be served by single endpont

by Petr Kremensky (Jira)

[ https://issues.jboss.org/browse/WFWIP-249?page=com.atlassian.jira.plugin.... ] Petr Kremensky commented on WFWIP-249: -------------------------------------- More info from discussion: Martin Choma 9:35 AM @Jean-Frederic Mesnil Just note regarding cookies. I doubt JSESSIONID cookie is relevant for OpenShift as it is platform for different languages. So what seems to me as relevant for openshift is 8695ba418ddbdc20694cde13495bd90c=78c87044937651274b32fab52794c559 from your example. I assume that is how OpenShift decide where to send the traffic by default. But then what is sessionAffinity: ClientIP useful for? {noformat} If you want to make sure that connections from a particular client are passed to the same Pod each time, you can select the session affinity based the on client’s IP addresses by setting service.spec.sessionAffinity to “ClientIP” {noformat} Based on this documentation I would expect when sessionAffinity: ClientIP is set only one pod will serve my requests. > sessionAffinity doesn't cause a requests from a same IP to be served by single endpont > -------------------------------------------------------------------------------------- > > Key: WFWIP-249 > URL: https://issues.jboss.org/browse/WFWIP-249 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Petr Kremensky > Assignee: Jeff Mesnil > Priority: Critical > Labels: operator > > It is expected, that if the {{sessionAffinity=true}}, the requests from a client with a same IP should be served by the same endpoint, using the latest upstream operator with the quickstart example: > *sessionAffinity=false* > {noformat} > $ oc patch wildflyserver quickstart -p '\[{"op":"replace", "path":"/spec/sessionAffinity", "value":false}\]' --type json > $ oc describe service/quickstart-loadbalancer | grep Session > Session Affinity: None > $ for i in {1..4} ; do echo `curl -s quickstart-route-wildfly.apps-crc.testing` ; done > {"ip":"10.128.0.98"} > {"ip":"10.128.0.99"} > {"ip":"10.128.0.98"} > {"ip":"10.128.0.99"} > {noformat} > *sessionAffinity=true* > {noformat} > $ oc patch wildflyserver quickstart -p '[{"op":"replace", "path":"/spec/sessionAffinity", "value":true}]' --type json > $ oc describe service/quickstart-loadbalancer | grep Session > Session Affinity: ClientIP > $ for i in {1..4} ; do echo `curl -s quickstart-route-wildfly.apps-crc.testing` ; done > {"ip":"10.128.0.98"} > {"ip":"10.128.0.99"} > {"ip":"10.128.0.98"} > {"ip":"10.128.0.99"} > {noformat} > {{sessionAffinity=true}} should make all responses to be served by the same endpoint -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-249) sessionAffinity doesn't cause a requests from a same IP to be served by single endpont

by Petr Kremensky (Jira)

Petr Kremensky created WFWIP-249: ------------------------------------ Summary: sessionAffinity doesn't cause a requests from a same IP to be served by single endpont Key: WFWIP-249 URL: https://issues.jboss.org/browse/WFWIP-249 Project: WildFly WIP Issue Type: Bug Components: OpenShift Reporter: Petr Kremensky Assignee: Jeff Mesnil It is expected, that if the {{sessionAffinity=true}}, the requests from a client with a same IP should be served by the same endpoint, using the latest upstream operator with the quickstart example: *sessionAffinity=false* {noformat} $ oc patch wildflyserver quickstart -p '\[{"op":"replace", "path":"/spec/sessionAffinity", "value":false}\]' --type json $ oc describe service/quickstart-loadbalancer | grep Session Session Affinity: None $ for i in {1..4} ; do echo `curl -s quickstart-route-wildfly.apps-crc.testing` ; done {"ip":"10.128.0.98"} {"ip":"10.128.0.99"} {"ip":"10.128.0.98"} {"ip":"10.128.0.99"} {noformat} *sessionAffinity=true* {noformat} $ oc patch wildflyserver quickstart -p '[{"op":"replace", "path":"/spec/sessionAffinity", "value":true}]' --type json $ oc describe service/quickstart-loadbalancer | grep Session Session Affinity: ClientIP $ for i in {1..4} ; do echo `curl -s quickstart-route-wildfly.apps-crc.testing` ; done {"ip":"10.128.0.98"} {"ip":"10.128.0.99"} {"ip":"10.128.0.98"} {"ip":"10.128.0.99"} {noformat} {{sessionAffinity=true}} should make all responses to be served by the same endpoint -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4610) Update HACEP docs & config for openshift 4.x

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4610?page=com.atlassian.jira.plugi... ] Massimiliano Dessi updated DROOLS-4610: --------------------------------------- Tester: Jiri Petrlik > Update HACEP docs & config for openshift 4.x > -------------------------------------------- > > Key: DROOLS-4610 > URL: https://issues.jboss.org/browse/DROOLS-4610 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4709) Upgrade Undertow to 2.0.27.Final

by Ivo Studensky (Jira)

[ https://issues.jboss.org/browse/WFCORE-4709?page=com.atlassian.jira.plugi... ] Ivo Studensky updated WFCORE-4709: ---------------------------------- Labels: downstream_dependency (was: ) > Upgrade Undertow to 2.0.27.Final > -------------------------------- > > Key: WFCORE-4709 > URL: https://issues.jboss.org/browse/WFCORE-4709 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Ivo Studensky > Assignee: Flavia Rainone > Priority: Major > Labels: downstream_dependency > > Upgrade Undertow to 2.0.27.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4610) Update HACEP docs & config for openshift 4.x

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4610?page=com.atlassian.jira.plugi... ] Massimiliano Dessi updated DROOLS-4610: --------------------------------------- Summary: Update HACEP docs & config for openshift 4.x (was: Update HACEP docs for openshift 4.x) > Update HACEP docs & config for openshift 4.x > -------------------------------------------- > > Key: DROOLS-4610 > URL: https://issues.jboss.org/browse/DROOLS-4610 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4643) Make configurable Kafka's consumers poll time

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4643?page=com.atlassian.jira.plugi... ] Massimiliano Dessi updated DROOLS-4643: --------------------------------------- Sprint: 2019 Week 41-43 (from Okt 7) > Make configurable Kafka's consumers poll time > ---------------------------------------------- > > Key: DROOLS-4643 > URL: https://issues.jboss.org/browse/DROOLS-4643 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4610) Update HACEP docs for openshift 4.x

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4610?page=com.atlassian.jira.plugi... ] Massimiliano Dessi updated DROOLS-4610: --------------------------------------- Sprint: 2019 Week 41-43 (from Okt 7) > Update HACEP docs for openshift 4.x > ----------------------------------- > > Key: DROOLS-4610 > URL: https://issues.jboss.org/browse/DROOLS-4610 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4709) Upgrade Undertow to 2.0.27.Final

by Ivo Studensky (Jira)

Ivo Studensky created WFCORE-4709: ------------------------------------- Summary: Upgrade Undertow to 2.0.27.Final Key: WFCORE-4709 URL: https://issues.jboss.org/browse/WFCORE-4709 Project: WildFly Core Issue Type: Component Upgrade Reporter: Ivo Studensky Assignee: Flavia Rainone Fix For: 10.0.0.Beta6, 10.0.0.Final Upgrade Undertow to 2.0.26.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4709) Upgrade Undertow to 2.0.27.Final

by Ivo Studensky (Jira)

[ https://issues.jboss.org/browse/WFCORE-4709?page=com.atlassian.jira.plugi... ] Ivo Studensky updated WFCORE-4709: ---------------------------------- Fix Version/s: (was: 10.0.0.Beta6) (was: 10.0.0.Final) > Upgrade Undertow to 2.0.27.Final > -------------------------------- > > Key: WFCORE-4709 > URL: https://issues.jboss.org/browse/WFCORE-4709 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Ivo Studensky > Assignee: Flavia Rainone > Priority: Major > > Upgrade Undertow to 2.0.26.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4709) Upgrade Undertow to 2.0.27.Final

by Ivo Studensky (Jira)

[ https://issues.jboss.org/browse/WFCORE-4709?page=com.atlassian.jira.plugi... ] Ivo Studensky updated WFCORE-4709: ---------------------------------- Description: Upgrade Undertow to 2.0.27.Final (was: Upgrade Undertow to 2.0.26.Final) > Upgrade Undertow to 2.0.27.Final > -------------------------------- > > Key: WFCORE-4709 > URL: https://issues.jboss.org/browse/WFCORE-4709 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Ivo Studensky > Assignee: Flavia Rainone > Priority: Major > > Upgrade Undertow to 2.0.27.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2019