December 2012 - infinispan-issues

[JBoss JIRA] (ISPN-2635) Support for Total Order Multicast Transactions

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2635?page=com.atlassian.jira.plugin.... ] Mircea Markus edited comment on ISPN-2635 at 12/14/12 7:06 AM: --------------------------------------------------------------- Implemented within the CloudTM project, based on https://issues.jboss.org/browse/JGRP-1442 was (Author: mircea.markus): Implemented by CloudTM project, based on https://issues.jboss.org/browse/JGRP-1442 > Support for Total Order Multicast Transactions > ---------------------------------------------- > > Key: ISPN-2635 > URL: https://issues.jboss.org/browse/ISPN-2635 > Project: Infinispan > Issue Type: Feature Request > Components: Transactions > Reporter: Mircea Markus > Assignee: Mircea Markus > Fix For: 5.3.0.Final > > > Based on CloudTM's implementation. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2636) Support for Total Order Broadcast(TOB) Transactions

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2636?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2636: -------------------------------- Fix Version/s: 5.3.0.Final > Support for Total Order Broadcast(TOB) Transactions > --------------------------------------------------- > > Key: ISPN-2636 > URL: https://issues.jboss.org/browse/ISPN-2636 > Project: Infinispan > Issue Type: Feature Request > Components: Transactions > Reporter: Mircea Markus > Assignee: Mircea Markus > Fix For: 5.3.0.Final > > -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2636) Support for Total Order Broadcast(TOB) Transactions

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2636?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2636: -------------------------------- Affects Version/s: (was: 5.3.0.Final) > Support for Total Order Broadcast(TOB) Transactions > --------------------------------------------------- > > Key: ISPN-2636 > URL: https://issues.jboss.org/browse/ISPN-2636 > Project: Infinispan > Issue Type: Feature Request > Components: Transactions > Reporter: Mircea Markus > Assignee: Mircea Markus > -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2636) Support for Total Order Broadcast(TOB) Transactions

by Mircea Markus (JIRA)

Mircea Markus created ISPN-2636: ----------------------------------- Summary: Support for Total Order Broadcast(TOB) Transactions Key: ISPN-2636 URL: https://issues.jboss.org/browse/ISPN-2636 Project: Infinispan Issue Type: Feature Request Components: Transactions Affects Versions: 5.3.0.Final Reporter: Mircea Markus Assignee: Mircea Markus -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2635) Support for Total Order Multicast Transaction

by Mircea Markus (JIRA)

Mircea Markus created ISPN-2635: ----------------------------------- Summary: Support for Total Order Multicast Transaction Key: ISPN-2635 URL: https://issues.jboss.org/browse/ISPN-2635 Project: Infinispan Issue Type: Feature Request Components: Transactions Reporter: Mircea Markus Assignee: Mircea Markus Fix For: 5.3.0.Final Based on CloudTM's implementation. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2631) HotRod server attempts to cast to CacheImpl

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-2631?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-2631: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Integrated. Thanks! > HotRod server attempts to cast to CacheImpl > ------------------------------------------- > > Key: ISPN-2631 > URL: https://issues.jboss.org/browse/ISPN-2631 > Project: Infinispan > Issue Type: Enhancement > Components: Remote protocols > Affects Versions: 5.2.0.Beta5 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Blocker > Fix For: 5.2.0.Beta6 > > > The HotRod server attempts to cast an AdvancedCache to CacheImpl directly which is wrong (and incidentally breaks JDG) > The getCacheEntry() method should be exposed on the AdvancedCache interface -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2635) Support for Total Order Multicast Transactions

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2635?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2635: -------------------------------- Summary: Support for Total Order Multicast Transactions (was: Support for Total Order Multicast Transaction) > Support for Total Order Multicast Transactions > ---------------------------------------------- > > Key: ISPN-2635 > URL: https://issues.jboss.org/browse/ISPN-2635 > Project: Infinispan > Issue Type: Feature Request > Components: Transactions > Reporter: Mircea Markus > Assignee: Mircea Markus > Fix For: 5.3.0.Final > > > Based on CloudTM's implementation. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2634) Implement cross-site replication based on I-RAC (Reliably Asynchronous Clustering)

by Mircea Markus (JIRA)

Mircea Markus created ISPN-2634: ----------------------------------- Summary: Implement cross-site replication based on I-RAC (Reliably Asynchronous Clustering) Key: ISPN-2634 URL: https://issues.jboss.org/browse/ISPN-2634 Project: Infinispan Issue Type: Feature Request Components: Cross-Site Replication Reporter: Mircea Markus Assignee: Mircea Markus Fix For: 5.3.0.Final As described here: https://community.jboss.org/wiki/RAC -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2342) The x-site implementation needs an inter-site state transfer mechanism

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2342?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2342: -------------------------------- Fix Version/s: 5.3.0.Final > The x-site implementation needs an inter-site state transfer mechanism > ---------------------------------------------------------------------- > > Key: ISPN-2342 > URL: https://issues.jboss.org/browse/ISPN-2342 > Project: Infinispan > Issue Type: Feature Request > Components: Cross-Site Replication > Affects Versions: 5.2.0.Alpha4 > Reporter: Erik Salter > Assignee: Mircea Markus > Fix For: 5.3.0.Final > > > To bring up a new site or recover a failed site, I need an inter-site state transfer mechanism for synchronizing keys. > Note that initially, this should a manual process that is invoked on one site to one of its configured backups. > This should be based on the non-blocking state transfer mechanism for consistency. > The pseudo-design may look similar to the following: > - Manually invokable, background thread > - Since the bridge end is open, there are writes happening to keys. Keep track of the puts/removes on the main data owner. > - Iterate through the key set. > - If the key has already been modified since the process started, discard. > - Else synchronously write the key value in a TX context -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-604) Re-design CacheStore transactions

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-604?page=com.atlassian.jira.plugin.s... ] Mircea Markus updated ISPN-604: ------------------------------- Fix Version/s: 5.3.0.Final (was: 6.0.0.Final) > Re-design CacheStore transactions > ---------------------------------- > > Key: ISPN-604 > URL: https://issues.jboss.org/browse/ISPN-604 > Project: Infinispan > Issue Type: Feature Request > Components: Loaders and Stores, Transactions > Affects Versions: 4.0.0.Final, 4.1.0.CR2 > Reporter: Mircea Markus > Assignee: Mircea Markus > Labels: as7-ignored, modshape > Fix For: 5.3.0.Final > > > Current(4.1.x) transaction implementation in CacheStores is brocken in several ways: > 1st problem. > - AbstractCacheStore.prepare: > public void prepare(List<? extends Modification> mods, GlobalTransaction tx, boolean isOnePhase) throws CacheLoaderException { > if (isOnePhase) { > applyModifications(mods); > } else { > transactions.put(tx, mods); > } > } > If this is 1PC we apply the modifications in the prepare phase - we should do it in the commit phase (as JTA does it). > 2nd problem. > This currently exhibits during commit/rollback with JdbcXyzCacheStore, but it is rather a more general cache store issue. > When using a TransactionManager, during TM.commit AbstractCacheStore.commit is being called internally which tries to apply all the modifications that happened during that transaction. > Within the scope of AbstractCacheStore.commit, JdbcStore obtains a connection from a DataSource and tries to write the modifications on that connection. > Now if the DataSource is managed (e.g. by an A.S.) on the DS.getConnection call the A.S. would try to enlist the connection with the ongoing transaction by calling Transaction.enlistResource(XAResource xaRes) [1] > This method fails with an IllegalStateException, because the transaction's status is preparing (see javax.transaction.Transaction.enlistResource). > Suggested fix: > - the modifications should be registered to the transaction as they happen(vs. during prepare/commit as it happens now) > - this requires API changes in CacheStore, e.g. > void store(InternalCacheEntry entry) > should become > void store(InternalCacheEntry entry, GlobalTransaction gtx) > (gtx would be null if this is not a transactional call). > [1] This behavior is specified by the JDBC 2.0 Standard Extension API, chapter 7 - distributed transaction -- 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

12 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2012