[
https://issues.jboss.org/browse/BAM-77?page=com.atlassian.jira.plugin.sys...
]
Gary Brown commented on BAM-77:
-------------------------------
The other approach is to just deal with this as a startup situation, and use it to
bootstrap the local copy. This will depend upon the importance of the information, and
whether precise synchronization is required - but if not, then it may be a simple low cost
approach to get the new server up and running. However it also assumes that other servers
are already running. If this is a problem, then the only solution may be using a real
persistent store.
Backing store for active collections
------------------------------------
Key: BAM-77
URL:
https://issues.jboss.org/browse/BAM-77
Project: Business Activity Monitoring
Issue Type: Feature Request
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 1.0.0.M4
Although active collections generally represent a realtime transient snapshot of some
relevant information, on occasions it may be necessary that all instances of a collection
across a cluster are consistent, and complete (e.g. on a server startup situation).
In this situations, the active collection would require some shared state mechanism (e.g.
cache) to replicate their state. The issue is that each server in the cluster will attempt
to update their instance of the collection, so this needs to be handled (e.g. before
applying the change check that it is required - but this may require some
synchronization).
Due to the potential performance implications, this type of active collection should
ideally only be used where infrequent updates are applied.
--
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