[jboss-jira] [JBoss JIRA] (WFLY-12718) Clustering: replicated-cache sampling errors

[Tommasso Borgato (Jira)]

    [ https://issues.jboss.org/browse/WFLY-12718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13806818#comment-13806818 ] 

Tommasso Borgato commented on WFLY-12718:
-----------------------------------------

[~rhusar] I added re-sync with this logic "if JMeter client receives N from server when it was expecting M, it logs the error and next time expects N+1 from server instead of M+1"

I re-run [eap-7.x-clustering-http-session-shutdown-repl-haproxy with jboss-eap-7.3.0.CD18-CR1.zip|https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP7-Clustering/view/EAP7-Clustering-HTTP-Session/job/eap-7.x-clustering-http-session-shutdown-repl-haproxy/20/artifact/report/jm/jmeter.log/*view*/] and now you can see the complete samples sequences up tothe sampling error, e.g.:

{noformat}
2019-10-31 14:59:00,930 ERROR o.j.e.c.j.ClusteringHTTPRequestSampler: Invalid serial: Expected 13, received 2 (previous: JSessionId{sessionId='UqdyYsC9ppIcJ-FwVcK_IG6SfEr67M3HREOGVcMC', jvmRoutes=[wildfly1]} current: JSessionId{sessionId='UqdyYsC9ppIcJ-FwVcK_IG6SfEr67M3HREOGVcMC', jvmRoutes=[wildfly1]}) 
samples sequence:
serial 0 JSessionId{sessionId='UqdyYsC9ppIcJ-FwVcK_IG6SfEr67M3HREOGVcMC', jvmRoutes=[wildfly1]}
serial 1 JSessionId{sessionId='UqdyYsC9ppIcJ-FwVcK_IG6SfEr67M3HREOGVcMC', jvmRoutes=[wildfly1]}
serial 2 JSessionId{sessionId='UqdyYsC9ppIcJ-FwVcK_IG6SfEr67M3HREOGVcMC', jvmRoutes=[wildfly1]}
serial 3 JSessionId{sessionId='UqdyYsC9ppIcJ-FwVcK_IG6SfEr67M3HREOGVcMC', jvmRoutes=[wildfly1]}
serial 4 JSessionId{sessionId='UqdyYsC9ppIcJ-FwVcK_IG6SfEr67M3HREOGVcMC', jvmRoutes=[wildfly1]}
serial 5 JSessionId{sessionId='UqdyYsC9ppIcJ-FwVcK_IG6SfEr67M3HREOGVcMC', jvmRoutes=[wildfly1]}
serial 6 JSessionId{sessionId='UqdyYsC9ppIcJ-FwVcK_IG6SfEr67M3HREOGVcMC', jvmRoutes=[wildfly1]}
serial 7 JSessionId{sessionId='UqdyYsC9ppIcJ-FwVcK_IG6SfEr67M3HREOGVcMC', jvmRoutes=[wildfly1]}
serial 8 JSessionId{sessionId='UqdyYsC9ppIcJ-FwVcK_IG6SfEr67M3HREOGVcMC', jvmRoutes=[wildfly1]}
serial 9 JSessionId{sessionId='UqdyYsC9ppIcJ-FwVcK_IG6SfEr67M3HREOGVcMC', jvmRoutes=[wildfly1]}
serial 10 JSessionId{sessionId='UqdyYsC9ppIcJ-FwVcK_IG6SfEr67M3HREOGVcMC', jvmRoutes=[wildfly1]}
serial 11 JSessionId{sessionId='UqdyYsC9ppIcJ-FwVcK_IG6SfEr67M3HREOGVcMC', jvmRoutes=[wildfly1]}
serial 12 JSessionId{sessionId='UqdyYsC9ppIcJ-FwVcK_IG6SfEr67M3HREOGVcMC', jvmRoutes=[wildfly1]}
{noformat}


> Clustering: replicated-cache sampling errors
> --------------------------------------------
>
>                 Key: WFLY-12718
>                 URL: https://issues.jboss.org/browse/WFLY-12718
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: 18.0.0.Final
>            Reporter: Tommasso Borgato
>            Assignee: Paul Ferraro
>            Priority: Blocker
>
> The issue is about replicated-cache in fail-over tests.
> WildFly is started in clustered mode using a replicated cache for replicating HTTP session data across cluster nodes; all 4 nodes in the cluster are initialized with the following cli script:
> {noformat}
> embed-server --server-config=standalone-ha.xml
> /subsystem=jgroups/channel=ee:write-attribute(name=stack,value=tcp)
> /subsystem=infinispan/cache-container=web/replicated-cache=testRepl:add()
> /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/component=locking:write-attribute(name=isolation, value=REPEATABLE_READ)
> /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/component=transaction:write-attribute(name=mode, value=BATCH)
> /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/store=file:add()
> /subsystem=infinispan/cache-container=web:write-attribute(name=default-cache, value=testRepl)
> {noformat}
> The test is run with wildfly-18.​0.0.Final.zip;
> The same tests run with version wildfly-17.​0.1.Final.zip do not have any problem;
> hence this looks like a regression;
> As usual, we test that the serial value stored in the replicated cache is incremented at every call: when this is not true, we say we have a sampling error;
> Here are the runs that exhibit this issue: 
> - **22.82% Fail Rate with WildFly-18 ** [eap-7.x-clustering-http-session-shutdown-repl#23|https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP7-Clustering/view/EAP7-Clustering-HTTP-Session/job/eap-7.x-clustering-http-session-shutdown-repl/23/artifact/report/jm/html/index.html]
> - **0% Fail Rate with WildFly-17 ** [eap-7.x-clustering-http-session-shutdown-repl#24|https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP7-Clustering/view/EAP7-Clustering-HTTP-Session/job/eap-7.x-clustering-http-session-shutdown-repl/24/artifact/report/jm/html/index.html]
> We also repeated the tests to make sure it can be reproduced:
> - **22.75% Fail rate with WildFly-18 ** [eap-7.x-clustering-http-session-shutdown-repl#26|https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP7-Clustering/view/EAP7-Clustering-HTTP-Session/job/eap-7.x-clustering-http-session-shutdown-repl/26/artifact/report/jm/html/index.html] 
> - **0% Fail Rate with WildFly-17 ** [eap-7.x-clustering-http-session-shutdown-repl#25|https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP7-Clustering/view/EAP7-Clustering-HTTP-Session/job/eap-7.x-clustering-http-session-shutdown-repl/25/artifact/report/jm/html/index.html]



--
This message was sent by Atlassian Jira
(v7.13.8#713008)