June 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3168) Use createClusteredCacheManager instead of createCacheManager for clustered caches

by Dan Berindei (JIRA)

Dan Berindei created ISPN-3168: ---------------------------------- Summary: Use createClusteredCacheManager instead of createCacheManager for clustered caches Key: ISPN-3168 URL: https://issues.jboss.org/browse/ISPN-3168 Project: Infinispan Issue Type: Bug Components: Test Suite Affects Versions: 5.3.0.CR1 Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 5.3.0.Final The overloads of {{TestCacheManagerFactory.createCacheManager(...)}} using the new configuration don't call {{amendTransport(...)}}, so the created cache managers will all use the same port range, and join the same cluster. Tests that need to create clustered cache managers should use {{TestCacheManagerFactory.createClusteredCacheManager(...)}} instead. -- 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3159) Implementing SERIALIZABLE isolation level based on GMU

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-3159?page=com.atlassian.jira.plugin.... ] Work on ISPN-3159 started by Pedro Ruivo. > Implementing SERIALIZABLE isolation level based on GMU > ------------------------------------------------------ > > Key: ISPN-3159 > URL: https://issues.jboss.org/browse/ISPN-3159 > Project: Infinispan > Issue Type: Feature Request > Components: Transactions > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 6.0.0.Alpha1, 6.0.0.Final > > > Implementation based in GMU, a Cloud-TM project research (www.cloudtm.eu). > GMU is a muti-version scheme that provides Update Serializability. It allows the read-only transaction to proceed without blocking, but they can observe an old value (but always a consistent value). > This scheme relies in Vector Clock to manage the snapshots to read and the transaction dependencies in each node in the cluster. > Also, it is a genuine scheme, i.e., only the nodes involved in the transaction (that contains data read or write) are involved in the transaction commit. > A paper describing GMU can be found here: http://ieeexplore.ieee.org/xpl/articleDetails.jsp?reload=true&arnumber=62... -- 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3159) Implementing SERIALIZABLE isolation level based on GMU

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-3159?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-3159: ------------------------------ Description: Implementation based in GMU, a Cloud-TM project research (www.cloudtm.eu). GMU is a muti-version scheme that provides Update Serializability. It allows the read-only transaction to proceed without blocking, but they can observe an old value (but always a consistent value). This scheme relies in Vector Clock to manage the snapshots to read and the transaction dependencies in each node in the cluster. Also, it is a genuine scheme, i.e., only the nodes involved in the transaction (that contains data read or write) are involved in the transaction commit. A paper describing GMU can be found here: http://ieeexplore.ieee.org/xpl/articleDetails.jsp?reload=true&arnumber=62... was: Implementation based in GMU, a Cloud-TM project research (www.cloudtm.eu). GMU is a muti-version scheme that provides Update Serializability. It allows the read-only transaction to proceed without blocking, but they can observe an old value (but always a consistent value). This scheme relies in Vector Clock to manage the snapshots to read and the transaction dependencies in each node in the cluster. Also, it is a genuine scheme, i.e., only the nodes involved in the transaction (that contains data read or write) are involved in the transaction commit. > Implementing SERIALIZABLE isolation level based on GMU > ------------------------------------------------------ > > Key: ISPN-3159 > URL: https://issues.jboss.org/browse/ISPN-3159 > Project: Infinispan > Issue Type: Feature Request > Components: Transactions > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 6.0.0.Alpha1, 6.0.0.Final > > > Implementation based in GMU, a Cloud-TM project research (www.cloudtm.eu). > GMU is a muti-version scheme that provides Update Serializability. It allows the read-only transaction to proceed without blocking, but they can observe an old value (but always a consistent value). > This scheme relies in Vector Clock to manage the snapshots to read and the transaction dependencies in each node in the cluster. > Also, it is a genuine scheme, i.e., only the nodes involved in the transaction (that contains data read or write) are involved in the transaction commit. > A paper describing GMU can be found here: http://ieeexplore.ieee.org/xpl/articleDetails.jsp?reload=true&arnumber=62... -- 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3058) HotRodTargetMigrator swallowing exceptions

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3058?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3058: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1863 > HotRodTargetMigrator swallowing exceptions > ------------------------------------------ > > Key: ISPN-3058 > URL: https://issues.jboss.org/browse/ISPN-3058 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.2.5.Final, 5.3.0.Alpha1 > Reporter: Galder Zamarreño > Assignee: Tristan Tarrant > Fix For: 5.3.0.Final > > > {code} > try { > cache.get(key); > int i = count.getAndIncrement(); > if (log.isDebugEnabled() && i % 100 == 0) > log.debugf(">> Moved %s keys\n", i); > } catch (Exception e) { > }{code} -- 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3167) Upgrade JTA to Narayana 4.17.4

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3167?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3167: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1862 > Upgrade JTA to Narayana 4.17.4 > ------------------------------ > > Key: ISPN-3167 > URL: https://issues.jboss.org/browse/ISPN-3167 > Project: Infinispan > Issue Type: Component Upgrade > Components: Transactions > Affects Versions: 5.3.0.CR1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Minor > Fix For: 5.3.0.Final > > > To align with other components (i.e. EAP) -- 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3167) Upgrade JTA to Narayana 4.17.4

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3167?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-3167: ------------------------------------- Assignee: Tristan Tarrant (was: Mircea Markus) > Upgrade JTA to Narayana 4.17.4 > ------------------------------ > > Key: ISPN-3167 > URL: https://issues.jboss.org/browse/ISPN-3167 > Project: Infinispan > Issue Type: Component Upgrade > Components: Transactions > Affects Versions: 5.3.0.CR1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Minor > Fix For: 5.3.0.Final > > > To align with other components (i.e. EAP) -- 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3167) Upgrade JTA to Narayana 4.17.4

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-3167: ------------------------------------- Summary: Upgrade JTA to Narayana 4.17.4 Key: ISPN-3167 URL: https://issues.jboss.org/browse/ISPN-3167 Project: Infinispan Issue Type: Component Upgrade Components: Transactions Affects Versions: 5.3.0.CR1 Reporter: Tristan Tarrant Assignee: Mircea Markus Priority: Minor Fix For: 5.3.0.Final To align with other components (i.e. EAP) -- 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

11 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2013