[infinispan-issues] [JBoss JIRA] (ISPN-2632) Uneven request balancing after node restore

[Galder Zamarreño (JIRA)]

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

Galder Zamarreño commented on ISPN-2632:
----------------------------------------

@Michal, Ok. What do you have in terms of logs? If this can be replicated in small scale, client and server TRACE logs on org.infinispan would be the easiest. 

How are these caches configured? Replication or distribution? I suppose it's the latter since it's the area that's changed the most for 5.2. If you need to scala log down, I'd suggest org.infinispan.client on the client side, and org.infinispan.server and org.infinispan.distribution on the server side.
                
> Uneven request balancing after node restore 
> --------------------------------------------
>
>                 Key: ISPN-2632
>                 URL: https://issues.jboss.org/browse/ISPN-2632
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Remote protocols
>    Affects Versions: 5.2.0.CR1
>            Reporter: Michal Linhard
>            Assignee: Galder Zamarreño
>             Fix For: 5.2.0.Final
>
>
> This is a new manifestation of ISPN-1995, but in this case this happens after killing only one node: the hot rod requests aren't very well balanced.
> these runs still manifest also ISPN-2550 and it may be cause of this bug.
> The uneven balancing of requests can be seen here:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EDG6/view/EDG-REPORTS-RESILIENCE/job/edg-60-resilience-dist-4-3/59/artifact/report/stats-throughput.png

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira