[jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1340) Session replication

[Tim Fox (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBMESSAGING-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Fox closed JBMESSAGING-1340.
--------------------------------

    Resolution: Done


> Session replication
> -------------------
>
>                 Key: JBMESSAGING-1340
>                 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1340
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>            Assignee: Tim Fox
>            Priority: Critical
>             Fix For: 2.0.0 Beta
>
>
> Implement replication of sessions between live and backup.
> It will be possible to replicate sessions to a backup node. Each node will be twinned with a backup. The nodes backup will be configured in the live nodes jbm-configuration.xml. When a node is started it will not become active until its backup is started.
> If a node fails, failover will occur on to the backup. It will then be possible to promote the back to a live node, and bring up another backup without downtime.
> The replication needs to happen in memory synchronously.
> Write to journal on both nodes can be lazy (asynchronous) since on failover we can be sure it is in memory on backup so no single point of failover.
> But can persist to disk asynchronously?? I think we can persist to disk asynchrnously on the master node, but needs to be synchronous on the backup node, in case we get a failure of the backup too shortly after failure of the master.
> If we can tolerate duplicate messages (or messages thought sent but not store) in a double failure then can do asynchronous storage on both master and slave.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira