[
https://issues.jboss.org/browse/ISPN-2038?page=com.atlassian.jira.plugin....
]
Manik Surtani commented on ISPN-2038:
-------------------------------------
It will work for async repl as well. You just need to query the messages received for a
transaction boundary event (commit or rollback) and you can be guaranteed that previous
messages pertaining to the tx would have been delivered.
Single thread doing all distribution related to a transaction - to
get ORDERING
-------------------------------------------------------------------------------
Key: ISPN-2038
URL:
https://issues.jboss.org/browse/ISPN-2038
Project: Infinispan
Issue Type: Enhancement
Reporter: Sudheer Krishna
Assignee: Manik Surtani
Priority: Minor
If we have this feature were in - a single thread does all replication related tasks
related to a transaction(may be by JTA transaction id) , we will get ordering of the
messages by default.
This will be quite useful in lots of use cases where ordering of messages is necessary -
which is now achieved with SYNC replication , can also be done using ASYNC replication(IF
we can guarantee ORDERING in ASYNC with the above feature).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira