12:55 a.m.
collate keys in replication queue
----------------------------------
Key: ISPN-503
URL: https://jira.jboss.org/browse/ISPN-503
Project: Infinispan
Issue Type: Feature Request
Components: Core API
Affects Versions: 4.1.0.BETA2
Reporter: Mircea Markus
Assignee: Manik Surtani
At the moment the replication queue is replicating all the keys. What it can do is to
collate them, similar to the way cache stores are collating writes.
E.g.
1. put(k,v1)
2. put(k,v2).
This can be collated in put(k,v2), as put(k,v1) is redundant.
This would optimize async replication in a way that cannot be handled by jgroups.
--
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
10:36 p.m.
New subject: [JBoss JIRA] Commented: (ISPN-503) collate keys in replication queue
[
https://jira.jboss.org/browse/ISPN-503?page=com.atlassian.jira.plugin.sys...
]
Galder Zamarreno commented on ISPN-503:
---------------------------------------
Any collating at the replication queue should use generic code once ISPN-159 has been done
when coalesced logic would have been extracted for different modules to use it.
collate keys in replication queue
----------------------------------
Key: ISPN-503
URL: https://jira.jboss.org/browse/ISPN-503
Project: Infinispan
Issue Type: Feature Request
Components: Core API
Affects Versions: 4.1.0.BETA2
Reporter: Mircea Markus
Assignee: Manik Surtani
At the moment the replication queue is replicating all the keys. What it can do is to
collate them, similar to the way cache stores are collating writes.
E.g.
1. put(k,v1)
2. put(k,v2).
This can be collated in put(k,v2), as put(k,v1) is redundant.
This would optimize async replication in a way that cannot be handled by jgroups.
--
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
12:09 p.m.
New subject: [JBoss JIRA] Updated: (ISPN-503) Coalesce updates in the replication queue
[
https://jira.jboss.org/browse/ISPN-503?page=com.atlassian.jira.plugin.sys...
]
Manik Surtani updated ISPN-503:
-------------------------------
Summary: Coalesce updates in the replication queue (was: collate keys in
replication queue )
Fix Version/s: 5.0.0.BETA1
5.0.0.Final
Complexity: Medium
Coalesce updates in the replication queue
-----------------------------------------
Key: ISPN-503
URL: https://jira.jboss.org/browse/ISPN-503
Project: Infinispan
Issue Type: Feature Request
Components: Core API
Affects Versions: 4.1.0.BETA2
Reporter: Mircea Markus
Assignee: Manik Surtani
Fix For: 5.0.0.BETA1, 5.0.0.Final
At the moment the replication queue is replicating all the keys. What it can do is to
collate them, similar to the way cache stores are collating writes.
E.g.
1. put(k,v1)
2. put(k,v2).
This can be collated in put(k,v2), as put(k,v1) is redundant.
This would optimize async replication in a way that cannot be handled by jgroups.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:48 p.m.
New subject: [JBoss JIRA] Assigned: (ISPN-503) Coalesce updates in the replication queue
[
https://issues.jboss.org/browse/ISPN-503?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño reassigned ISPN-503:
-------------------------------------
Assignee: Galder Zamarreño (was: Manik Surtani)
Coalesce updates in the replication queue
-----------------------------------------
Key: ISPN-503
URL: https://issues.jboss.org/browse/ISPN-503
Project: Infinispan
Issue Type: Feature Request
Components: Core API
Affects Versions: 4.1.0.BETA2
Reporter: Mircea Markus
Assignee: Galder Zamarreño
Fix For: 5.0.0.ALPHA3, 5.0.0.Final
At the moment the replication queue is replicating all the keys. What it can do is to
collate them, similar to the way cache stores are collating writes.
E.g.
1. put(k,v1)
2. put(k,v2).
This can be collated in put(k,v2), as put(k,v1) is redundant.
This would optimize async replication in a way that cannot be handled by jgroups.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:48 p.m.
New subject: [JBoss JIRA] Updated: (ISPN-503) Coalesce updates in the replication queue
[
https://issues.jboss.org/browse/ISPN-503?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño updated ISPN-503:
----------------------------------
Fix Version/s: 5.0.0.ALPHA3
(was: 5.0.0.BETA1)
Coalesce updates in the replication queue
-----------------------------------------
Key: ISPN-503
URL: https://issues.jboss.org/browse/ISPN-503
Project: Infinispan
Issue Type: Feature Request
Components: Core API
Affects Versions: 4.1.0.BETA2
Reporter: Mircea Markus
Assignee: Galder Zamarreño
Fix For: 5.0.0.ALPHA3, 5.0.0.Final
At the moment the replication queue is replicating all the keys. What it can do is to
collate them, similar to the way cache stores are collating writes.
E.g.
1. put(k,v1)
2. put(k,v2).
This can be collated in put(k,v2), as put(k,v1) is redundant.
This would optimize async replication in a way that cannot be handled by jgroups.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:01 p.m.
New subject: [JBoss JIRA] Updated: (ISPN-503) Coalesce updates in the replication queue
[
https://issues.jboss.org/browse/ISPN-503?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño updated ISPN-503:
----------------------------------
Fix Version/s: 5.0.0.BETA1
(was: 5.0.0.ALPHA3)
Coalesce updates in the replication queue
-----------------------------------------
Key: ISPN-503
URL: https://issues.jboss.org/browse/ISPN-503
Project: Infinispan
Issue Type: Feature Request
Components: Core API
Affects Versions: 4.1.0.BETA2
Reporter: Mircea Markus
Assignee: Galder Zamarreño
Fix For: 5.0.0.BETA1, 5.0.0.Final
At the moment the replication queue is replicating all the keys. What it can do is to
collate them, similar to the way cache stores are collating writes.
E.g.
1. put(k,v1)
2. put(k,v2).
This can be collated in put(k,v2), as put(k,v1) is redundant.
This would optimize async replication in a way that cannot be handled by jgroups.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:13 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-503) Coalesce updates in the replication queue
[
https://issues.jboss.org/browse/ISPN-503?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño updated ISPN-503:
----------------------------------
Fix Version/s: 5.1.0.BETA1
5.1.0.Final
(was: 5.0.0.BETA1)
(was: 5.0.0.Final)
Coalesce updates in the replication queue
-----------------------------------------
Key: ISPN-503
URL: https://issues.jboss.org/browse/ISPN-503
Project: Infinispan
Issue Type: Feature Request
Components: Core API
Affects Versions: 4.1.0.BETA2
Reporter: Mircea Markus
Assignee: Galder Zamarreño
Fix For: 5.1.0.BETA1, 5.1.0.Final
At the moment the replication queue is replicating all the keys. What it can do is to
collate them, similar to the way cache stores are collating writes.
E.g.
1. put(k,v1)
2. put(k,v2).
This can be collated in put(k,v2), as put(k,v1) is redundant.
This would optimize async replication in a way that cannot be handled by jgroups.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:56 p.m.
New subject: [JBoss JIRA] Updated: (ISPN-503) Coalesce updates in the replication queue
[
https://issues.jboss.org/browse/ISPN-503?page=com.atlassian.jira.plugin.s...
]
Manik Surtani updated ISPN-503:
-------------------------------
Fix Version/s: 5.2.0.Final
(was: 5.1.0.BETA1)
(was: 5.1.0.Final)
Coalesce updates in the replication queue
-----------------------------------------
Key: ISPN-503
URL: https://issues.jboss.org/browse/ISPN-503
Project: Infinispan
Issue Type: Feature Request
Components: Core API
Affects Versions: 4.1.0.BETA2
Reporter: Mircea Markus
Assignee: Galder Zamarreño
Fix For: 5.2.0.Final
At the moment the replication queue is replicating all the keys. What it can do is to
collate them, similar to the way cache stores are collating writes.
E.g.
1. put(k,v1)
2. put(k,v2).
This can be collated in put(k,v2), as put(k,v1) is redundant.
This would optimize async replication in a way that cannot be handled by jgroups.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:27 a.m.
New subject: [JBoss JIRA] (ISPN-503) Coalesce updates in the replication queue
[
https://issues.jboss.org/browse/ISPN-503?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño updated ISPN-503:
----------------------------------
Fix Version/s: 6.0.0.Final
(was: 5.2.0.Final)
Coalesce updates in the replication queue
-----------------------------------------
Key: ISPN-503
URL: https://issues.jboss.org/browse/ISPN-503
Project: Infinispan
Issue Type: Feature Request
Components: Core API
Affects Versions: 4.1.0.BETA2
Reporter: Mircea Markus
Assignee: Galder Zamarreño
Fix For: 6.0.0.Final
At the moment the replication queue is replicating all the keys. What it can do is to
collate them, similar to the way cache stores are collating writes.
E.g.
1. put(k,v1)
2. put(k,v2).
This can be collated in put(k,v2), as put(k,v1) is redundant.
This would optimize async replication in a way that cannot be handled by jgroups.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4202
days inactive
5056
days old
infinispan-issues@lists.jboss.org
8 comments
4 participants
participants (4)
-
Galder Zamarreno (JIRA) -
Galder Zamarreño (JIRA)
-
Manik Surtani (JIRA)
-
Mircea Markus (JIRA)