[JBoss JIRA] (ISPN-2038) Single thread doing all distribution related to a transaction - to get ORDERING
2:31 p.m.
Sudheer Krishna created ISPN-2038:
-------------------------------------
Summary: 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
3:57 p.m.
[
https://issues.jboss.org/browse/ISPN-2038?page=com.atlassian.jira.plugin....
]
Manik Surtani commented on ISPN-2038:
-------------------------------------
Not true. Even if a single thread performs all of the RPC for a given transaction (and
this is what happens even now!) if your listener is async (and you have an async listener
thread pool of > 1 thread) it is possible that the events are handled out of order.
What you need, specifically, is the ability to register an async listener but to pass in
to that listener a mechanism of ordering the events it receives. This is what is commonly
known as "unit of order", where, in your case, the transaction id becomes the
unit of order when handling messages on the receiver.
Some JMS implementations support this, it is worthwhile checking whether HornetQ currently
supports this - it has been on their roadmap for a while now.
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
4:11 p.m.
[
https://issues.jboss.org/browse/ISPN-2038?page=com.atlassian.jira.plugin....
]
Sudheer Krishna commented on ISPN-2038:
---------------------------------------
Great. I was not aware that single thread performs all of the RPC for a given
transaction.
Does this mean that even though I have async replication, with sync listeners I will get
all changes within a transaction in order ?
Just by my curisity,
If any JMS implementation does support the above functionality for async listeners, How
would it know that all messages related to a transaction have already been received ?
(Since replication mode is async and listener is async)
Or is this functionality only applicable for sync replication and async notification ?
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
4:29 p.m.
[
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
4:49 p.m.
[
https://issues.jboss.org/browse/ISPN-2038?page=com.atlassian.jira.plugin....
]
Sudheer Krishna commented on ISPN-2038:
---------------------------------------
Thanks for confirming the same. Should be closing this issue ?
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
5:49 p.m.
[
https://issues.jboss.org/browse/ISPN-2038?page=com.atlassian.jira.plugin....
]
Manik Surtani commented on ISPN-2038:
-------------------------------------
Yes please. :)
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
6:08 p.m.
[
https://issues.jboss.org/browse/ISPN-2038?page=com.atlassian.jira.plugin....
]
Sudheer Krishna closed ISPN-2038.
---------------------------------
Resolution: Done
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
4364
days inactive
4370
days old
infinispan-issues@lists.jboss.org
6 comments
2 participants
participants (2)
-
Manik Surtani (JIRA) -
Sudheer Krishna (JIRA)