December 2016 - infinispan-issues

[JBoss JIRA] (ISPN-2575) KeyTransformer registration is required on all nodes of the cluster, in case of custom keys

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2575?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2575: -------------------------------- Assignee: Adrian Nistor (was: Sanne Grinovero) > KeyTransformer registration is required on all nodes of the cluster, in case of custom keys > ------------------------------------------------------------------------------------------- > > Key: ISPN-2575 > URL: https://issues.jboss.org/browse/ISPN-2575 > Project: Infinispan > Issue Type: Enhancement > Components: Querying > Affects Versions: 5.2.0.Beta5 > Reporter: Anna Manukyan > Assignee: Adrian Nistor > Attachments: ClusteredCacheTest.java > > > The case is the following: > I have a clustered cache on which I want to perform a search. I'm doing the following: > I'm initializing SearchManager on node1, I'm registering a custom key transformer for my key using the created searchmanager, but then when I'm trying to put data into the cache on node1 (which is in REPL_SYNC mode with cache on node2), I'm getting the exception: > java.lang.IllegalArgumentException: Indexing only works with entries keyed on Strings, primitives and classes that have the @Transformable annotation - you passed in a class org.infinispan.query.test.CustomKey3. Alternatively, see org.infinispan.query.SearchManager#registerKeyTransformer > When I'm initializing the SearchManager using node2 cache and register the keyTransformer on it as well, then everything works perfectly, even though I am not using the second created SearchManager. > The test which reproduces the issue is attached to the jira. Please see the test case: testSearchKeyTransformer() -- 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

1 week

2
1
0 / 0

[JBoss JIRA] (ISPN-2399) CacheManager.startCaches very slow when multiple caches are passed in

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2399?page=com.atlassian.jira.plugin.... ] Dan Berindei resolved ISPN-2399. -------------------------------- Fix Version/s: 7.0.0.Final Resolution: Out of Date Fixed before 7.0.0.Final. > CacheManager.startCaches very slow when multiple caches are passed in > --------------------------------------------------------------------- > > Key: ISPN-2399 > URL: https://issues.jboss.org/browse/ISPN-2399 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 5.2.0.Beta1 > Reporter: Mircea Markus > Priority: Minor > Fix For: 7.0.0.Final > > > the TransactionsSpanningReplicatedCachesTest uses the following code to start multiple caches: > {code:java} > cm1.startCaches("c1", "c2", "cache1", "cache2", CacheContainer.DEFAULT_CACHE_NAME); > cm2.startCaches("c1", "c2", "cache1", "cache2", CacheContainer.DEFAULT_CACHE_NAME); > waitForClusterToForm("c1", "c2", "cache1", "cache2"); > {code} > On my machine(MBP) this executes in 12 mins.The functionally equivalent below executes in 15 secs: > {code:java} > private void startAllCaches() { > startCache("c1"); > startCache("c2"); > startCache("cache1"); > startCache("cache2"); > startCache(CacheContainer.DEFAULT_CACHE_NAME); > } > private void startCache(String c1) { > cm1.getCache(c1); > cm2.getCache(c1); > waitForClusterToForm(c1); > } > {code} > We need to analyse why this takes so long and also updated the test to use the CacheManagers.startCaches.. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6802) Micro-optimizations for read operations

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6802?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6802: ------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/4732, https://github.com/infinispan/infinispan/pull/4746 (was: https://github.com/infinispan/infinispan/pull/4732) > Micro-optimizations for read operations > --------------------------------------- > > Key: ISPN-6802 > URL: https://issues.jboss.org/browse/ISPN-6802 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 9.0.0.Alpha2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.Beta2 > > > * L1 entries are written to the data container by L1TxInterceptor/L1NonTxInterceptor directly, so there is no reason to commit the context entries in EntryWrappingInterceptor or to clear the locks in the locking interceptors. > * ClearCommands can no longer be wrapped in PrepareCommands, so we can stop the state transfer in {{EntryWrappingInterceptor.visitClearCommand()}} instead of checking the type for each command. > * In transactional caches, a read operation without an explicit transaction triggers two queries for the current transaction to the transaction manager, which usually means 2 thread-local lookups. > * IsMarshallerInterceptor shouldn't do anything unless there is an asynchronous store > * Transactional remote get commands use NonTxInvocationInterceptor instead of SingleKeyNonTxInterceptor. > * Configuration attributes should be cached, as reading them requires accessing multiple instances + a cast in Attribute.get() -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5989) Use DC.keyEquivalence().hashCode() for hashing into segments

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5989?page=com.atlassian.jira.plugin.... ] Dan Berindei resolved ISPN-5989. -------------------------------- Fix Version/s: 9.0.0.Beta1 Resolution: Out of Date The DataContainer equivalence configuration is ignored since the ISPN-6998 fix. > Use DC.keyEquivalence().hashCode() for hashing into segments > ------------------------------------------------------------ > > Key: ISPN-5989 > URL: https://issues.jboss.org/browse/ISPN-5989 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 8.1.0.Beta1 > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.0.0.Beta1 > > > Custom Equivalence is not taken into account in key -> segment decision. > This is also related to ISPN-3905, the fix should remove the expensive string encoding as well. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4098) DataContainer Equivalence is not used properly

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4098?page=com.atlassian.jira.plugin.... ] Dan Berindei resolved ISPN-4098. -------------------------------- Fix Version/s: 9.0.0.Beta1 Resolution: Out of Date The DataContainer equivalence configuration is no longer used since the ISPN-6998 fix. > DataContainer Equivalence is not used properly > ---------------------------------------------- > > Key: ISPN-4098 > URL: https://issues.jboss.org/browse/ISPN-4098 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.0.0.Alpha1 > Reporter: William Burns > Fix For: 9.0.0.Beta1 > > > The DefaultDataContainer uses an EquivalentHashMap under the scenes. The values() method doesn't return a collection that obeys the value Equivalence however. Also to note the provided value equivalence would have to be wrapped with an Equivalence for ICE to be used properly as shown with the new typing changes in ISPN-4079. > Also to note any users of DataContainer values, keySet methods would have to also use the proper equivalence. An example is the KeySetCommand, ValuesCommand and EntrySetCommand should obey these Equivalences. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7304) infinispan-bom not published in 9.0.0-Beta1

by Ben Manes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7304?page=com.atlassian.jira.plugin.... ] Ben Manes closed ISPN-7304. --------------------------- Resolution: Out of Date Seems to have been fixed. > infinispan-bom not published in 9.0.0-Beta1 > ------------------------------------------- > > Key: ISPN-7304 > URL: https://issues.jboss.org/browse/ISPN-7304 > Project: Infinispan > Issue Type: Bug > Components: Build process > Affects Versions: 9.0.0.Beta1 > Reporter: Ben Manes > > I was updating the dependencies in Caffeine and ran into this. Presumably I can remove it instead since Infinispan adopted it, but was going to play around first. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7123) Kill JDBC binary and mixed stores

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7123?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-7123: ------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/4745 > Kill JDBC binary and mixed stores > --------------------------------- > > Key: ISPN-7123 > URL: https://issues.jboss.org/browse/ISPN-7123 > Project: Infinispan > Issue Type: Task > Components: Loaders and Stores > Affects Versions: 9.0.0.Alpha4 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > > The JDBC binary stores are terribly inefficient as they require that an entire bucket be deserailised/serialised for store reads/writes, therefore we should remove them in 9.0. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7124) Create JDBC Binary/Mixed Store Migrator

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7124?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-7124: ------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/4745 > Create JDBC Binary/Mixed Store Migrator > --------------------------------------- > > Key: ISPN-7124 > URL: https://issues.jboss.org/browse/ISPN-7124 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Affects Versions: 9.0.0.Alpha4 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > > As we are removing the JDBC mixed/binary stores it is necessary for us to include a migration tool to the string based store. This could be an opportunity to create a generic store migrator, with a JDBC specific implementation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7325) Shared transactional store warnings not applicable to local caches

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7325?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-7325: ------------------------------- Status: Open (was: New) > Shared transactional store warnings not applicable to local caches > ------------------------------------------------------------------ > > Key: ISPN-7325 > URL: https://issues.jboss.org/browse/ISPN-7325 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 9.0.0.Beta1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > > Currently a CacheConfigurationException is thrown if a cache store is configured as transactional but not shared, for all cache modes. This exception shouldn't be thrown for a local cache. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7325) Shared transactional store warnings not applicable to local caches

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7325?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-7325: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4745 > Shared transactional store warnings not applicable to local caches > ------------------------------------------------------------------ > > Key: ISPN-7325 > URL: https://issues.jboss.org/browse/ISPN-7325 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 9.0.0.Beta1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > > Currently a CacheConfigurationException is thrown if a cache store is configured as transactional but not shared, for all cache modes. This exception shouldn't be thrown for a local cache. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2016