[jboss-jira] [JBoss JIRA] (WFLY-12404) High Fail rate with MOD_JK and JDG remote-cache-container

[Tommasso Borgato (Jira)]

     [ https://issues.jboss.org/browse/WFLY-12404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tommasso Borgato updated WFLY-12404:
------------------------------------
    Description: 
Scenario: 2 nodes WildFly cluster where session data is offloaded to a remote 2 nodes JDG cluster (jboss-datagrid-7.3.0);
When using MOD_JK as load balancer we observe a higher fail rate (~9%) than when using MOD_CLUSTER or HAPROXY (~0.9%); fail rate is intended as inconsistencies in the data stored in cache and subsequently retrieved on another node of the cluster:

* [MOD_JK|https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-clustering-jdg-session-repl-shutdown-mod_jk/13/artifact/report/jm/html/index.html]
* [MOD_CLUSTER|https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-clustering-jdg-session-repl-shutdown-mod_cluster/72/artifact/report/jm/html/index.html]
* [HAPROXY|https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-clustering-jdg-session-repl-shutdown-haproxy/31/artifact/report/jm/html/index.html]

  was:
Scenario: 2 nodes EAP cluster where session data is offloaded to a remote 2 nodes JDG cluster (jboss-datagrid-7.3.0);
When using MOD_JK as load balancer we observe a higher fail rate (~9%) than when using MOD_CLUSTER or HAPROXY (~0.9%); fail rate is intended as inconsistencies in the data stored in cache and subsequently retrieved on another node of the cluster:

* [MOD_JK|https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-clustering-jdg-session-repl-shutdown-mod_jk/13/artifact/report/jm/html/index.html]
* [MOD_CLUSTER|https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-clustering-jdg-session-repl-shutdown-mod_cluster/72/artifact/report/jm/html/index.html]
* [HAPROXY|https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-clustering-jdg-session-repl-shutdown-haproxy/31/artifact/report/jm/html/index.html]



> High Fail rate with MOD_JK and JDG remote-cache-container
> ---------------------------------------------------------
>
>                 Key: WFLY-12404
>                 URL: https://issues.jboss.org/browse/WFLY-12404
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: 18.0.0.Beta1
>            Reporter: Tommasso Borgato
>            Assignee: Paul Ferraro
>            Priority: Major
>
> Scenario: 2 nodes WildFly cluster where session data is offloaded to a remote 2 nodes JDG cluster (jboss-datagrid-7.3.0);
> When using MOD_JK as load balancer we observe a higher fail rate (~9%) than when using MOD_CLUSTER or HAPROXY (~0.9%); fail rate is intended as inconsistencies in the data stored in cache and subsequently retrieved on another node of the cluster:
> * [MOD_JK|https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-clustering-jdg-session-repl-shutdown-mod_jk/13/artifact/report/jm/html/index.html]
> * [MOD_CLUSTER|https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-clustering-jdg-session-repl-shutdown-mod_cluster/72/artifact/report/jm/html/index.html]
> * [HAPROXY|https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-clustering-jdg-session-repl-shutdown-haproxy/31/artifact/report/jm/html/index.html]



--
This message was sent by Atlassian Jira
(v7.12.1#712002)