[
https://issues.jboss.org/browse/ISPN-2394?page=com.atlassian.jira.plugin....
]
Adrian Nistor commented on ISPN-2394:
-------------------------------------
Actually it seems DataRehashedEvent already exists and is not used yet in 5.2 due to NBST
changes. So rather than introducing a new event we should use this to signal end of state
transfer. But we should also update the TopologyChangedEvent as noted before.
Introduce an event to signal end of state transfer
--------------------------------------------------
Key: ISPN-2394
URL:
https://issues.jboss.org/browse/ISPN-2394
Project: Infinispan
Issue Type: Task
Components: State transfer
Affects Versions: 5.2.0.ALPHA1
Reporter: Adrian Nistor
Assignee: Adrian Nistor
Fix For: 5.2.0.Beta3
Since NBST was introduced the actual completion of state transfer happens later than the
TopologyChangedEvent. In unit tests there is currently no simple way to find out when this
actually happens so we resorted to some ugly polling (see
TestingUtil.waitForRehashToComplete()). Also some other core components could benefit from
such an event (eg. StaleTransactionCleanupService, see ISPN-2383).
The event should contain the CacheTopology that is being confirmed as stable.
--
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