May 2011 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-1132) Locking optimization: reorder lock acquisition to avoid deadlocks

by Mircea Markus (JIRA)

Locking optimization: reorder lock acquisition to avoid deadlocks ------------------------------------------------------------------- Key: ISPN-1132 URL: https://issues.jboss.org/browse/ISPN-1132 Project: Infinispan Issue Type: Feature Request Components: Transactions Reporter: Mircea Markus Assignee: Manik Surtani Fix For: 5.1.0.Final Detailed here, as the 3rd improvement: http://community.jboss.org/wiki/PossibleLockingImprovements -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

4
12
0 / 0

[JBoss JIRA] Created: (ISPN-1137) Locking optimization: for dist lock only main data owner

by Mircea Markus (JIRA)

Locking optimization: for dist lock only main data owner --------------------------------------------------------- Key: ISPN-1137 URL: https://issues.jboss.org/browse/ISPN-1137 Project: Infinispan Issue Type: Feature Request Components: Transactions Affects Versions: 4.2.1.FINAL Reporter: Mircea Markus Assignee: Manik Surtani Detailed here, as the 4th improvement: http://community.jboss.org/wiki/PossibleLockingImprovements As without ISPN-1131 locks are being acquired as the transaction progresses this optimization makes more sense after having ISPN-1131 in place. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

5
18
0 / 0

[JBoss JIRA] Created: (ISPN-1115) Fine-grained AtomicMaps

by Manik Surtani (JIRA)

Fine-grained AtomicMaps ----------------------- Key: ISPN-1115 URL: https://issues.jboss.org/browse/ISPN-1115 Project: Infinispan Issue Type: Feature Request Components: Core API Affects Versions: 5.0.0.FINAL Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.1.0.BETA1, 5.1.0.Final Atomic Maps are locked by acquiring a single lock on the entire map and this causes concurrency issues for certain use cases. This JIRA is to allow for concurrent modifications of keys within the AtomicMap, provided the keys do not overlap. The design is as follows: * {{AtomicMapLookup}} gets a WL on the {{AtomicMap}}'s key (AMK) when creating and removing a new AtomicMap * Modifications to the AtomicMap (which go through the {{AtomicMapProxy}}) do _not_ acquire a WL on AMK. Instead, * {{AdvancedCache}} exposes a new API, {{applyDelta(K deltaAwareValueKey, Delta delta, Object... locksToAcquire)}} * {{AtomicMapProxy}} makes changes by calling {{applyDelta}} and passing in the key within the map that is being modified, along with the delta to apply. * The implementation could offer lock pooling to prevent a large number of locks being created for AtomicMaps with a large number of entries This can then be used by other {{Delta}}/{{DeltaAware}} types in future as well, perhaps JSON documents, etc. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

12
22
0 / 0

[JBoss JIRA] Created: (ISPN-439) Define and implement configuration file backward and forward compatibility policy

by Vladimir Blagojevic (JIRA)

Define and implement configuration file backward and forward compatibility policy --------------------------------------------------------------------------------- Key: ISPN-439 URL: https://jira.jboss.org/jira/browse/ISPN-439 Project: Infinispan Issue Type: Task Affects Versions: 4.1.0.BETA1 Reporter: Vladimir Blagojevic Assignee: Manik Surtani Fix For: 4.1.0.CR1 Backward compatibility: Process any previous version configuration file from the same minor version. For example, Infinispan release 4.2 should process configuration file produced for version 4.1 without any configuration file changes or any other adjustments. For configuration options present in 4.2, but not in 4.1 assume default values. However, Infinispan version 5.0 is not required to process configuration files from previous major versions, i.e 4.0...4.x. Forward compatibility. Do not process any forward version configuration file. For example, Infinispan release 4.1, give configuration file input from any succeeding versions (i.e 4.2...4.x, 5.x) would simply fail outright with proper error message. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

7
26
0 / 0

[JBoss JIRA] Created: (ISPN-658) DistributionManager not considerate of cache state changes

by Paul Ferraro (JIRA)

DistributionManager not considerate of cache state changes ---------------------------------------------------------- Key: ISPN-658 URL: https://jira.jboss.org/browse/ISPN-658 Project: Infinispan Issue Type: Bug Components: Distributed Cache Affects Versions: 4.2.0.ALPHA2 Reporter: Paul Ferraro Assignee: Manik Surtani Considering a cache manager with 2 caches in DIST mode (C1 and C2) deployed on 2 nodes (N1 and N2). Currently, the DistributionManager does not properly handle the following scenarios: 1. Stop C1 on N1. This ought to trigger a rehash for the C1 cache. Currently, rehashing is only triggered via view change. Failure to rehash on stopping of a cache can inadvertently cause data loss, if all backups of a given cache entry have stopped. 2. A new DIST mode cache, C3, is started on N2. If N1 is the coordinator, the join request sent to N1 will get stuck in an infinite loop, since the cache manager on N1 does not contain a C3 cache. 3. Less critically, a new node, N3 is started. It does not yet have a C1 or C2 cache, though it's cache manager is started. This prematurely triggers a rehash of C1 and C2, even though there are no new caches instances to consider. -- 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

13 years, 2 months

11
24
0 / 0

[JBoss JIRA] Created: (ISPN-1136) Locking optimization: for dist lock only main data owner

by Mircea Markus (JIRA)

Locking optimization: for dist lock only main data owner --------------------------------------------------------- Key: ISPN-1136 URL: https://issues.jboss.org/browse/ISPN-1136 Project: Infinispan Issue Type: Feature Request Components: Transactions Affects Versions: 4.2.1.FINAL Reporter: Mircea Markus Assignee: Manik Surtani Detailed here, as the 4th improvement: http://community.jboss.org/wiki/PossibleLockingImprovements As without ISPN-1131 locks are being acquired as the transaction progresses this optimization makes more sense after having ISPN-1131 in place. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (ISPN-1131) Locking optimization: acquire (write) locks at prepare time

by Mircea Markus (JIRA)

Locking optimization: acquire (write) locks at prepare time ----------------------------------------------------------- Key: ISPN-1131 URL: https://issues.jboss.org/browse/ISPN-1131 Project: Infinispan Issue Type: Feature Request Reporter: Mircea Markus Assignee: Manik Surtani Fix For: 5.1.0.Final Detailed here, as the 1st improvement: http://community.jboss.org/wiki/PossibleLockingImprovements -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

4
18
0 / 0

[JBoss JIRA] Created: (ISPN-434) Creating a new distributed cache on a non-coordinator node causes rehashing to hang

by Manik Surtani (JIRA)

Creating a new distributed cache on a non-coordinator node causes rehashing to hang ----------------------------------------------------------------------------------- Key: ISPN-434 URL: https://jira.jboss.org/jira/browse/ISPN-434 Project: Infinispan Issue Type: Bug Components: Distributed Cache Affects Versions: 4.1.0.ALPHA3 Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 4.1.0.CR1, 4.1.0.Final If a cluster is already formed (perhaps due to another cache instance being started, such as a replicated one) and subsequently a distributed cache is created and started, first on a non-coordinator node, the startup sequence will hang until the cache is also started on the coordinator. E.g., 1. C1 (coord) starts replicated cache 2. C2 starts replicated cache 3. C2 starts distributed cache 4. C1 starts distributed cache Step 3 will hang until step 4 completes. So unless these happen in different threads - on different servers - this rehash will hang. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (ISPN-1104) Upgrade to Scala 2.9.0.final

by Trustin Lee (JIRA)

Upgrade to Scala 2.9.0.final ---------------------------- Key: ISPN-1104 URL: https://issues.jboss.org/browse/ISPN-1104 Project: Infinispan Issue Type: Task Reporter: Trustin Lee Assignee: Trustin Lee Priority: Trivial Fix For: 5.0.0.FINAL, 5.0.0.CR3 Scala 2.9.0.final has been released with various bug fixes and improvements. It's backward compatible as long as the code is recompiled, so I assume it's safe to upgrade and we should upgrade because people will be using Scala 2.9 when 5.0.0.Final is out. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
8
0 / 0

[JBoss JIRA] Created: (ISPN-448) Consider all topology cache updates to be done by coordinator in Hot Rod

by Galder Zamarreno (JIRA)

Consider all topology cache updates to be done by coordinator in Hot Rod ------------------------------------------------------------------------ Key: ISPN-448 URL: https://jira.jboss.org/browse/ISPN-448 Project: Infinispan Issue Type: Task Components: Cache Server Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 5.0.0.BETA1 Based on the discussion below, consider all topology cache updates to be done by coordinator to avoid concurrency issues when updating it. > Looks good. > What is causing this unsuccessful add? If it is caused by timeouts due > to multiple caches operating on the same key an alternative would be > to only perform the operation on the coordinator and rest of the > members to have node added listeners ... Currently, each node when it starts, it's responsible of adding itself to the view and when it stops, it's responsible from removing itself. Apart from this, there's a crashed member listener running only in coordinator that detects whether any member left without updating the topology view. Your suggestion to have the coordinator control it all seems like could work and get around potential timeouts. I'll create a JIRA to investigate this but won't do it for CR1 since I'm expect this to be a major issue. Metadata size is small and it's not constantly uddated. -- 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

13 years, 3 months

4
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2011