June 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2931) async mode changes remove behaviour

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2931?page=com.atlassian.jira.plugin.... ] Galder Zamarreño resolved ISPN-2931. ------------------------------------ Fix Version/s: (was: 6.0.0.Final) Resolution: Rejected The issue is not present in master right now. We have a test that can be modified this scenario (https://github.com/infinispan/infinispan/blob/master/core/src/test/java/o... - set testRetVals=true), and it works fine. > async mode changes remove behaviour > ----------------------------------- > > Key: ISPN-2931 > URL: https://issues.jboss.org/browse/ISPN-2931 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache > Affects Versions: 5.2.1.Final > Reporter: Sebastian Tusk > Assignee: Galder Zamarreño > > With a cache setup as clustering dist, 2 owners and async mode the Cache.remove API does not behave correctly. Cache.remove(key) should return the old value and Cache.remove(key, value) should return true if the entry was removed. Both methods only work correctly if invoked on the primary owner of the key. If invoked on another node remove(key) returns null every time and remove(key,value) returns false every time. The Infinispan documentation says that in async mode these operations should work as expected. https://docs.jboss.org/author/display/ISPN/Asynchronous+Options > Complete cache config: > <namedCache name="distributed"> >  > <jmxStatistics enabled="true" /> > > <clustering mode="dist"> > <stateTransfer fetchInMemoryState="true" timeout="20000" /> > <hash numOwners="2"/> > <async/> > </clustering> > <locking isolationLevel="READ_COMMITTED" > lockAcquisitionTimeout="15000" useLockStriping="false" /> > > <eviction maxEntries="10000" strategy="LRU" /> > <expiration maxIdle="3600000" wakeUpInterval="5000"/> > <storeAsBinary storeKeysAsBinary="true" storeValuesAsBinary="false" enabled="false" /> > </namedCache> -- 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-3238) infinispan-config-5.3.xsd missing "compatibility" element

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3238?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3238: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1912 > infinispan-config-5.3.xsd missing "compatibility" element > --------------------------------------------------------- > > Key: ISPN-3238 > URL: https://issues.jboss.org/browse/ISPN-3238 > Project: Infinispan > Issue Type: Feature Request > Components: Documentation > Affects Versions: 5.3.0.CR2 > Reporter: Erik Pearson > Assignee: Galder Zamarreño > Priority: Critical > Fix For: 5.3.0.Final > > > The schema documentation for and publicly available http://www.jboss.org/schema/infinispan/infinispan-config-5.3.xsd are missing the "compatibility" element under default/namedCache. -- 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-3241) Memcached server should not redefine its cache if it already exists

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3241?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3241: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1911 > Memcached server should not redefine its cache if it already exists > ------------------------------------------------------------------- > > Key: ISPN-3241 > URL: https://issues.jboss.org/browse/ISPN-3241 > Project: Infinispan > Issue Type: Feature Request > Affects Versions: 5.2.6.Final, 5.3.0.CR2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3241) Memcached server should not redefine its cache if it already exists

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3241?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3241: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 975361|https://bugzilla.redhat.com/show_bug.cgi?id=975361] from NEW to ASSIGNED > Memcached server should not redefine its cache if it already exists > ------------------------------------------------------------------- > > Key: ISPN-3241 > URL: https://issues.jboss.org/browse/ISPN-3241 > Project: Infinispan > Issue Type: Feature Request > Affects Versions: 5.2.6.Final, 5.3.0.CR2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3244) TopologyAwareSyncConsistentHashFactory should limit the number of segments per node

by Dan Berindei (JIRA)

Dan Berindei created ISPN-3244: ---------------------------------- Summary: TopologyAwareSyncConsistentHashFactory should limit the number of segments per node Key: ISPN-3244 URL: https://issues.jboss.org/browse/ISPN-3244 Project: Infinispan Issue Type: Bug Components: State transfer Affects Versions: 5.3.0.CR2, 5.2.6.Final Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 5.3.0.Final Let's say we have a cluster with 5 nodes: A(r1), B(r2), C(r2), D(r3), E(r3) TopologyAwareConsistentSyncHashFactory will spread the segments equally on each rack, meaning A will own 2x segments compared to the other nodes. TopologyAwareConsistentHashFactory limits the maximum number per node, so that A owns just as many segments as the other nodes. With a slight limitation: the number of racks must be greater than numOwners, otherwise each rack must hold (at least) one copy of all the data. TopologyAwareConsistentSyncHashFactory is a little random, so we can't distribute the data perfectly, but we can limit the number of segments on each node to something like 1.5x the average number of segments. -- 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-3243) Inconsistent behaviour of operations HotRod.clear vs Memcached.flushAll wrt CacheStore

by Michal Linhard (JIRA)

Michal Linhard created ISPN-3243: ------------------------------------ Summary: Inconsistent behaviour of operations HotRod.clear vs Memcached.flushAll wrt CacheStore Key: ISPN-3243 URL: https://issues.jboss.org/browse/ISPN-3243 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 5.2.6.Final, 5.3.0.Final Reporter: Michal Linhard Assignee: Mircea Markus Affecting 5.3.0-SNAPSHOT and 5.2.x branch When using hot rod client the clear() operation deletes all entries also in the cache store When using memcached client the flush_all operation deletes entries only in the memory hotrod behaviour: https://github.com/infinispan/infinispan/blob/5.3.x/server/hotrod/src/mai... memcached behaviour: https://github.com/infinispan/infinispan/blob/5.3.x/server/memcached/src/... shouldn't they be consistent ? -- 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-3232) ClassCastException in LevelDBCacheStore

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3232?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-3232: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=975808 > ClassCastException in LevelDBCacheStore > --------------------------------------- > > Key: ISPN-3232 > URL: https://issues.jboss.org/browse/ISPN-3232 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 5.3.0.CR1 > Reporter: Michal Linhard > Assignee: Mircea Markus > > The test org/infinispan/loaders/leveldb/LevelDBCacheStoreTest.java shows this error in the log: > {code} > 2013-06-14 15:20:13,136 ERROR [AbstractCacheStore] (main) ISPN000045: Problems encountered while purging expired > org.infinispan.loaders.CacheLoaderException: org.infinispan.loaders.CacheLoaderException: java.lang.ClassCastException: [B cannot be cast to java.lang.Long > at org.infinispan.loaders.leveldb.LevelDBCacheStore.purgeInternal(LevelDBCacheStore.java:412) > at org.infinispan.loaders.AbstractCacheStore$2.run(AbstractCacheStore.java:111) > at org.infinispan.util.concurrent.WithinThreadExecutor.execute(WithinThreadExecutor.java:44) > at org.infinispan.loaders.AbstractCacheStore.purgeExpired(AbstractCacheStore.java:107) > at org.infinispan.loaders.BaseCacheStoreTest.purgeExpired(BaseCacheStoreTest.java:214) > at org.infinispan.loaders.BaseCacheStoreTest.testLoadAndStoreWithIdle(BaseCacheStoreTest.java:202) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:335) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:330) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291) > at org.testng.SuiteRunner.run(SuiteRunner.java:240) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1149) > at org.testng.TestNG.run(TestNG.java:1057) > at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:111) > at org.testng.remote.RemoteTestNG.initAndRun(RemoteTestNG.java:204) > at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:175) > Caused by: org.infinispan.loaders.CacheLoaderException: java.lang.ClassCastException: [B cannot be cast to java.lang.Long > at org.infinispan.loaders.leveldb.LevelDBCacheStore.purgeInternal(LevelDBCacheStore.java:403) > ... 29 more > Caused by: java.lang.ClassCastException: [B cannot be cast to java.lang.Long > at org.infinispan.loaders.leveldb.LevelDBCacheStore.purgeInternal(LevelDBCacheStore.java:367) > ... 29 more > {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-3242) Require the use of Java7 for building Infinispan

by Manik Surtani (JIRA)

[ https://issues.jboss.org/browse/ISPN-3242?page=com.atlassian.jira.plugin.... ] Manik Surtani updated ISPN-3242: -------------------------------- Description: Note that this doesn't force Java7 at runtime, just build-time. Need to take into account continuous integration runs where the project will need to be built using Java7 but tested on Java6. (was: Note that this doesn't force Java7 at runtime, just build-time.) > Require the use of Java7 for building Infinispan > ------------------------------------------------ > > Key: ISPN-3242 > URL: https://issues.jboss.org/browse/ISPN-3242 > Project: Infinispan > Issue Type: Feature Request > Components: Build process > Affects Versions: 5.3.0.Final > Reporter: Manik Surtani > Assignee: Mircea Markus > Fix For: 6.0.0.Alpha1, 6.0.0.Final > > > Note that this doesn't force Java7 at runtime, just build-time. Need to take into account continuous integration runs where the project will need to be built using Java7 but tested on Java6. -- 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-3242) Require the use of Java7 for building Infinispan

by Manik Surtani (JIRA)

Manik Surtani created ISPN-3242: ----------------------------------- Summary: Require the use of Java7 for building Infinispan Key: ISPN-3242 URL: https://issues.jboss.org/browse/ISPN-3242 Project: Infinispan Issue Type: Feature Request Components: Build process Reporter: Manik Surtani Assignee: Mircea Markus Note that this doesn't force Java7 at runtime, just build-time. -- 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-3242) Require the use of Java7 for building Infinispan

by Manik Surtani (JIRA)

[ https://issues.jboss.org/browse/ISPN-3242?page=com.atlassian.jira.plugin.... ] Manik Surtani updated ISPN-3242: -------------------------------- Fix Version/s: 6.0.0.Alpha1 6.0.0.Final > Require the use of Java7 for building Infinispan > ------------------------------------------------ > > Key: ISPN-3242 > URL: https://issues.jboss.org/browse/ISPN-3242 > Project: Infinispan > Issue Type: Feature Request > Components: Build process > Reporter: Manik Surtani > Assignee: Mircea Markus > Fix For: 6.0.0.Alpha1, 6.0.0.Final > > > Note that this doesn't force Java7 at runtime, just build-time. -- 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2013