March 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2956) putIfAbsent on Hot Rod Java client doesn't reliably fulfil contract

by Ion Savin (JIRA)

[ https://issues.jboss.org/browse/ISPN-2956?page=com.atlassian.jira.plugin.... ] Ion Savin updated ISPN-2956: ---------------------------- Fix Version/s: 7.0.0.Alpha3 (was: 7.0.0.Alpha2) > putIfAbsent on Hot Rod Java client doesn't reliably fulfil contract > ------------------------------------------------------------------- > > Key: ISPN-2956 > URL: https://issues.jboss.org/browse/ISPN-2956 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Minor > Labels: hotrod-java-client, remote-clients > Fix For: 7.0.0.Alpha3 > > > Hot Rod's putIfAbsent might have issues on some edge cases: > {quote}I want to know whether the putting entry already exists in the remote > cache cluster, or not. > I thought that RemoteCache.putIfAbsent() would be useful for that > purpose, i.e., > {code} > if (remoteCache.putIfAbsent(k,v) == null) { > // new entry. > } else { > // k already exists. > } > {code} > But no. > The putIfAbsent() for new entry may return non-null value, if one of the > server crushed while putting. > The behavior is like the following: > 1. Client do putIfAbsent(k,v). > 2. The server receives the request and sends replication requests to > other servers. If the server crushed before completing replication, some > servers own that (k,v), but others not. > 3. Client receives the error. The putIfAbsent() internally retries the > same request to the next server in the cluster server list. > 4. If the next server owns the (k,v), the putIfAbsent() returns the > replicated (k,v) at the step 2, without any error. > So, putIfAbsent() is not reliable for knowing whether the putting entry > is *exactly* new or not. > Does anyone have any idea/workaround for this purpose?{quote} > A workaround is to do this: > {quote}We got a simple solution, which can be applied to our customer's application. > If each value part of putting (k,v) is unique or contains unique value, > the client can do *double check* wether the entry is new. > {code} > val = System.nanoTime(); // or uuid is also useful. > if ((ret = cache.putIfAbsent(key, val)) == null > || ret.equals(val)) { > // new entry, if the return value is just the same. > } else { > // key already exists. > } > {code} > We are proposing this workaround which almost works fine.{quote} > However, this is a bit of a cludge. > Hot Rod should be improved with an operation that allows a version to be passed when entry is created, instead of relying on the client generating it. -- 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
0
0 / 0

[JBoss JIRA] (ISPN-2854) REST server discards Content Encoding information from client

by Ion Savin (JIRA)

[ https://issues.jboss.org/browse/ISPN-2854?page=com.atlassian.jira.plugin.... ] Ion Savin updated ISPN-2854: ---------------------------- Fix Version/s: 7.0.0.Alpha3 (was: 7.0.0.Alpha2) > REST server discards Content Encoding information from client > ------------------------------------------------------------- > > Key: ISPN-2854 > URL: https://issues.jboss.org/browse/ISPN-2854 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 5.2.2.Final > Reporter: NadirX > Fix For: 7.0.0.Alpha3 > > > The REST server discards the Content-Encoding header from the client and therefore does not serve it back when the content is being read, possibly causing misinterpretation -- 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
0
0 / 0

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

by Ion Savin (JIRA)

[ https://issues.jboss.org/browse/ISPN-3159?page=com.atlassian.jira.plugin.... ] Ion Savin updated ISPN-3159: ---------------------------- Fix Version/s: 7.0.0.Alpha3 (was: 7.0.0.Alpha2) > 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: 7.0.0.Alpha3 > > > 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

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3093) Design remote Map/Reduce functionality in Infinispan

by Ion Savin (JIRA)

[ https://issues.jboss.org/browse/ISPN-3093?page=com.atlassian.jira.plugin.... ] Ion Savin updated ISPN-3093: ---------------------------- Fix Version/s: 7.0.0.Alpha3 (was: 7.0.0.Alpha2) > Design remote Map/Reduce functionality in Infinispan > ---------------------------------------------------- > > Key: ISPN-3093 > URL: https://issues.jboss.org/browse/ISPN-3093 > Project: Infinispan > Issue Type: Task > Components: Remote Protocols > Reporter: Mircea Markus > Assignee: Mircea Markus > Fix For: 7.0.0.Alpha3 > > -- 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
0
0 / 0

[JBoss JIRA] (ISPN-3039) Add JCache quickstarts

by Ion Savin (JIRA)

[ https://issues.jboss.org/browse/ISPN-3039?page=com.atlassian.jira.plugin.... ] Ion Savin updated ISPN-3039: ---------------------------- Fix Version/s: 7.0.0.Alpha3 (was: 7.0.0.Alpha2) > Add JCache quickstarts > ---------------------- > > Key: ISPN-3039 > URL: https://issues.jboss.org/browse/ISPN-3039 > Project: Infinispan > Issue Type: Task > Components: JCache > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.0.0.Alpha3 > > > Quickstarts should be added to https://github.com/infinispan/infinispan-quickstart so that users can get started quickly with JCache API. -- 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
0
0 / 0

[JBoss JIRA] (ISPN-3047) Drop encoding from CLI once servers store raw values

by Ion Savin (JIRA)

[ https://issues.jboss.org/browse/ISPN-3047?page=com.atlassian.jira.plugin.... ] Ion Savin updated ISPN-3047: ---------------------------- Fix Version/s: 7.0.0.Alpha3 (was: 7.0.0.Alpha2) > Drop encoding from CLI once servers store raw values > ---------------------------------------------------- > > Key: ISPN-3047 > URL: https://issues.jboss.org/browse/ISPN-3047 > Project: Infinispan > Issue Type: Task > Components: CLI > Affects Versions: 5.3.0.Alpha1 > Reporter: NadirX > Assignee: Tristan Tarrant > Fix For: 7.0.0.Alpha3 > > -- 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
0
0 / 0

[JBoss JIRA] (ISPN-3045) Drop wrappers from RemoteCacheStore once HotRod server supports raw keys/values

by Ion Savin (JIRA)

[ https://issues.jboss.org/browse/ISPN-3045?page=com.atlassian.jira.plugin.... ] Ion Savin updated ISPN-3045: ---------------------------- Fix Version/s: 7.0.0.Alpha3 (was: 7.0.0.Alpha2) > Drop wrappers from RemoteCacheStore once HotRod server supports raw keys/values > ------------------------------------------------------------------------------- > > Key: ISPN-3045 > URL: https://issues.jboss.org/browse/ISPN-3045 > Project: Infinispan > Issue Type: Task > Components: Remote Protocols > Reporter: NadirX > Assignee: Tristan Tarrant > Fix For: 7.0.0.Alpha3 > > -- 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
0
0 / 0

[JBoss JIRA] (ISPN-3337) Define an approach to allow the injection of Configuration and GlobalConfiguration beans for overriding

by Ion Savin (JIRA)

[ https://issues.jboss.org/browse/ISPN-3337?page=com.atlassian.jira.plugin.... ] Ion Savin updated ISPN-3337: ---------------------------- Fix Version/s: 7.0.0.Alpha3 (was: 7.0.0.Alpha2) > Define an approach to allow the injection of Configuration and GlobalConfiguration beans for overriding > ------------------------------------------------------------------------------------------------------- > > Key: ISPN-3337 > URL: https://issues.jboss.org/browse/ISPN-3337 > Project: Infinispan > Issue Type: Feature Request > Components: Spring Integration > Reporter: Navin Surtani > Assignee: Navin Surtani > Fix For: 7.0.0.Alpha3 > > > ISPN-3279 removed the ConfigurationOverrides and GlobalConfigurationOverrides classes in the Spring module. These classes contained older set() calls in order to override Cache configurations and given the way that programmatic Configuration currently works in Infinispan, that approach is not maintainable. > We hence need a clean way to provide (Global) Configuration beans as a newer, cleaner approach. -- 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
0
0 / 0

[JBoss JIRA] (ISPN-3273) Dist L1 owners that aren't primary don't respect assumeOriginKeptEntryInL1

by Ion Savin (JIRA)

[ https://issues.jboss.org/browse/ISPN-3273?page=com.atlassian.jira.plugin.... ] Ion Savin updated ISPN-3273: ---------------------------- Fix Version/s: 7.0.0.Alpha3 (was: 7.0.0.Alpha2) > Dist L1 owners that aren't primary don't respect assumeOriginKeptEntryInL1 > -------------------------------------------------------------------------- > > Key: ISPN-3273 > URL: https://issues.jboss.org/browse/ISPN-3273 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: William Burns > Assignee: William Burns > Fix For: 7.0.0.Alpha3 > > Attachments: DistSyncFuncTest.java > > > When a write operation occurs causing a L1 invalidation, there is a boolean to say assumeOriginKeptEntryInL1 which means the owner won't send an invalidation to the originating node that caused this update. This works fine for the primary owner, however any additional backups think the origin is the primary owner and such send invalidations to possibly the real origin. > -This affects both tx and non tx caches. Tx caches that are sync don't see the problem since locking prevents the invalidation, however it causes an unneeded network roundtrip which can cause delay.- > Actually this only affects non-tx caches, as tx caches send the prepare/commit directly to the owner(s) instead of having it relayed. -- 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
0
0 / 0

[JBoss JIRA] (ISPN-3336) Extended Statistics check list

by Ion Savin (JIRA)

[ https://issues.jboss.org/browse/ISPN-3336?page=com.atlassian.jira.plugin.... ] Ion Savin updated ISPN-3336: ---------------------------- Fix Version/s: 7.0.0.Alpha3 (was: 7.0.0.Alpha2) > Extended Statistics check list > ------------------------------ > > Key: ISPN-3336 > URL: https://issues.jboss.org/browse/ISPN-3336 > Project: Infinispan > Issue Type: Task > Components: Core > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Critical > Labels: core > Fix For: 7.0.0.Alpha3 > > > * add documentation > * check for duplicate stats; > * check for not exposed statistics > * try to improve the code (reduce the number of access to the CHM) > * add tests to check if they are exported via JMX correctly > * failing test: OptimisticLockingTxClusterExtendedStatisticLogicTest.testWriteSkewOnNonOwner > * failing test: PessimisticLockingTxClusterExtendedStatisticLogicTest.testDeadlockOnNonOwnerWithRemoteTx -- 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
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2014