[ https://issues.jboss.org/browse/ISPN-2394?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-2394: -------------------------------- Description: 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. was: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). -- 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

[ https://issues.jboss.org/browse/ISPN-2394?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-2394: ------------------------------------ I think the existing {{TopologyChanged}} event is fine, we just need to modify it to contain the initial and final {{CacheTopology}}. That way a listener can check if the pending CH is {{null}} in the final topology and conclude that state transfer has finished. -- 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

[ 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. -- 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

[ https://issues.jboss.org/browse/ISPN-2394?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2394: -------------------------------- Fix Version/s: 5.2.0.CR1 (was: 5.2.0.Beta3) -- 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

[ https://issues.jboss.org/browse/ISPN-2394?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2394: -------------------------------- Fix Version/s: 6.0.0.Final (was: 5.2.0.Final) -- 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