[infinispan-issues] [JBoss JIRA] Commented: (ISPN-557) support for same transaction touching multiple nodes (multiple VMs)

[Manik Surtani (JIRA)]

    [ https://jira.jboss.org/browse/ISPN-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12542440#action_12542440 ] 

Manik Surtani commented on ISPN-557:
------------------------------------

This is for different VMs.  E.g., consider 2 JBossAS instances with embedded Infinispan instances, running a transactional WebApp and NOT using session affinity.  Correct that this still is a niche though (and I'm downgrading prio accordingly), but it may become a valid concern once we look at cloud/PaaS deployments where container volatility is more common.

> support for same transaction touching multiple nodes (multiple VMs) 
> --------------------------------------------------------------------
>
>                 Key: ISPN-557
>                 URL: https://jira.jboss.org/browse/ISPN-557
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Transactions
>    Affects Versions: 4.1.0.Final
>            Reporter: Mircea Markus
>            Assignee: Manik Surtani
>             Fix For: 5.1.0.BETA1, 5.1.0.Final
>
>
> E.g. if a distributed transaction managers touches two embedded Infinispan nodes within the same transaction.
> Could be implemented using the Hot Rod client approach - but in an embedded fashion!
> EmbeddedClient <-- implements logic above
> Except comms are in-VM for local entries
> And via RpcDispatcher for remote entries
> RemoteClient extends EmbeddedClient
> Adds proper HotRod layer for comms 
> Including failover, smart routing, etc.

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