[infinispan-issues] [JBoss JIRA] (ISPN-1995) Uneven request balancing after node restore
[
https://issues.jboss.org/browse/ISPN-1995?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on ISPN-1995:
-----------------------------------------------
Michal Linhard <mlinhard(a)redhat.com> made a comment on [bug
809631|https://bugzilla.redhat.com/show_bug.cgi?id=809631]
@Galder, just in case you don't already know: I'm looking at the trace logs as
well and on node01 I'm seeing this:
HotRodServer.viewId is set to 2 when both events - adding of node02 and adding of node03:
14:34:14,429 TRACE [org.infinispan.server.hotrod.HotRodServer] (undefined) Address cache
had CACHE_ENTRY_CREATED for key node03/default. View id is now 2
14:34:14,468 TRACE [org.infinispan.server.hotrod.HotRodServer] (undefined) Address cache
had CACHE_ENTRY_CREATED for key node02/default. View id is now 2
since viewId didn't change the HotRodServer doesn't think it needs to send info
about node02 to the client.
Uneven request balancing after node restore
-------------------------------------------
Key: ISPN-1995
URL: https://issues.jboss.org/browse/ISPN-1995
Project: Infinispan
Issue Type: Bug
Components: Cache Server
Affects Versions: 5.1.4.CR1
Reporter: Tristan Tarrant
Assignee: Galder Zamarreño
Fix For: 5.1.5.CR1, 5.2.0.ALPHA1, 5.2.0.FINAL
After a node crashes and rejoins the cluster, it does not receive client load at the same
level as the other nodes.
This issue does not affect data integrity and distribution in the cluster.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira