[
http://jira.jboss.com/jira/browse/JBMESSAGING-911?page=comments#action_12... ]
Tim Fox commented on JBMESSAGING-911:
-------------------------------------
Actually we should make it so a particular node *doesn't* share it's tx log - we
can do this by adding a node id column to the transaction table, and a node will only
recover its own txs.
This makes life a lot easier.
Clustered recovery cleanup
--------------------------
Key: JBMESSAGING-911
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-911
Project: JBoss Messaging
Issue Type: Task
Reporter: Tim Fox
Assigned To: Tim Fox
Priority: Critical
Fix For: 1.4.0.CR1
For a clustered config we assume we can get our xaresource for recovery from any node of
the cluster and do recovery on that, this means that transactions can be recovered on
different nodes to where they originally where - i.e. we have a shared transaction log.
This means other nodes will also load them up into their in memory maps too.
Therefore on successful resolution we need to broadcst this across the cluster so they
can be removed from other nodes in transaction repositories 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