[
http://jira.jboss.com/jira/browse/JBMESSAGING-406?page=comments#action_12... ]
Tim Fox commented on JBMESSAGING-406:
-------------------------------------
We need to support automatic failover for the case where no shared file systems is
present.
In which case we need to replicate state to a buddy.
This should be configurable on a per queue level.
We can supply different levels of reliability:
1) Once and only once - with this mode we would need two streams one for replication
messages and one for replication acks
We would also need to store last sequence received in the storage to avoid having to use
XA
2) At most once - replication sent async. Chance of message loss.
3) No replication
Persistence refactoring
-----------------------
Key: JBMESSAGING-406
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-406
Project: JBoss Messaging
Issue Type: Task
Reporter: Tim Fox
Assigned To: Tim Fox
Priority: Critical
Fix For: 2.0.0 Alpha
Need to refactor persistence so each node has its own storage.
We should provide at least three local persistence manager configs:
1) JDBC local pm that works out of the box with HSQL - not recommended for production.
2) BDB based pm that customers need to download - recommended for best performance.
Should optimise for the SAN use case.
Need to consider whether we need to support replication for failover too.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira