[
https://issues.jboss.org/browse/ISPN-2632?page=com.atlassian.jira.plugin....
]
Dan Berindei updated ISPN-2632:
-------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request:
https://github.com/infinispan/infinispan/pull/1576,
https://github.com/infinispan/infinispan/pull/1587 (was:
https://github.com/infinispan/infinispan/pull/1576)
Send the cache topology id to the client instead of the JGroups view id.
After a rebalance, the cache topology id is incremented, so this ensures
that the client's topology information is updated as well.
To work properly with replicated caches, this change required always incrementing the
cache topology id after a leave, even if without a rebalance
(
https://issues.jboss.org/browse/ISPN-2420).
Uneven request balancing after node crash
-----------------------------------------
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: Dan Berindei
Priority: Blocker
Fix For: 5.2.0.CR2, 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-REPOR...
--
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