[
https://issues.jboss.org/browse/ISPN-977?page=com.atlassian.jira.plugin.s...
]
Mircea Markus edited comment on ISPN-977 at 5/11/11 8:02 AM:
-------------------------------------------------------------
Here is the problem:
- KAS registers itself as a view change listener
- on a view change event the key buffer is flushed and new keys are generated
- the new CH is only installed at a further point (i.e. after @ViewChange is processed).
In this time window, keys are being generated using the old CH => stale keys
was (Author: mircea.markus):
Here is the problem:
- KAS registers itself as a view change listener
- on a change of view, KAS cleans the key buffer and regenerates other keys
- the new CH is only installed at a further point in time so keys are being generated on
the old CH => stale keys
KeyAffinityService has stale keys when topology changes
-------------------------------------------------------
Key: ISPN-977
URL:
https://issues.jboss.org/browse/ISPN-977
Project: Infinispan
Issue Type: Bug
Affects Versions: 4.2.1.CR4
Reporter: Mircea Markus
Assignee: Mircea Markus
Fix For: 5.0.0.FINAL
When the KAS is registered for single not cluster, when the cluster increases size, the
old keys from KAS are not purged, resulting in an inconsistent key set.
Usable UT on the forums:
http://community.jboss.org/message/592275#592275
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira