July 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-848) Enhance HotRod to allow explicit locking of keys

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-848?page=com.atlassian.jira.plugin.s... ] Mircea Markus updated ISPN-848: ------------------------------- Fix Version/s: (was: 6.0.0.Final) > Enhance HotRod to allow explicit locking of keys > ------------------------------------------------ > > Key: ISPN-848 > URL: https://issues.jboss.org/browse/ISPN-848 > Project: Infinispan > Issue Type: Feature Request > Reporter: Erik Salter > Assignee: Manik Surtani > > Hot Rod clients should allow explicit locking of keys, especially useful for the "find-for-update" design pattern. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2686) Enhance Mapper API with lazy loaded value

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2686?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2686: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Enhance Mapper API with lazy loaded value > ----------------------------------------- > > Key: ISPN-2686 > URL: https://issues.jboss.org/browse/ISPN-2686 > Project: Infinispan > Issue Type: Enhancement > Components: Distributed Execution and Map/Reduce > Affects Versions: 5.2.0.Beta6 > Reporter: Thomas Fromm > Assignee: Vladimir Blagojevic > Priority: Minor > > In situations where Map/Reduce is used and the value is not (always) needed at the Mapper, the value could be loaded lazy, when the map(..) interface is slightly changed: > map(Entry<KIn, VIn> entry, Collector<Entry<KIn, VIn>> collector) > When entry.getValue() is called, the value should be loaded from store or maybe remote node. > Maybe this change to Entry would be also useful for event api ISPN-1802 -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-230) Enable JNDI binding of Cache/CacheManager out of the box

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-230?page=com.atlassian.jira.plugin.s... ] Mircea Markus updated ISPN-230: ------------------------------- Fix Version/s: (was: 6.0.0.Final) > Enable JNDI binding of Cache/CacheManager out of the box > -------------------------------------------------------- > > Key: ISPN-230 > URL: https://issues.jboss.org/browse/ISPN-230 > Project: Infinispan > Issue Type: Feature Request > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Minor > Labels: hackathon > > Note that implementing this has no urgency since it does not really help Brian S for the JBoss AS integration. > See: http://lists.jboss.org/pipermail/infinispan-dev/2009-October/001663.html > So, I'm thinking that we could have a <jndi name="xyz"/> configuration > option both at the global level (for Cache Manager) and at the Cache > level. So, > - if <jndi/> was present in the global section, we'd bind CacheManager > to java:CacheManager > - if <jndi name="xyz"/> was present in the global section, we'd bind > CacheManager to java:xyz > - if <jndi/> was present in the cache section, we'd bind Cache to > java:<name-of-the-cache> > - if <jndi name="xyz"/> was present in the cache section, we'd bind > Cache to java:xyz -- 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, 9 months

1
0
0 / 0

[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: -------------------------------- Priority: Minor (was: Major) > 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 > Priority: Minor > Fix For: 6.0.0.Final > > 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

12 years, 9 months

1
0
0 / 0

[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 commented on ISPN-2575: ------------------------------------- reducing the priority as this has a workaround and the user is informed early on how it should proceed. > 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 > Priority: Minor > Fix For: 6.0.0.Final > > 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2148) Improve lock timeout exception details

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2148?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2148: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Improve lock timeout exception details > -------------------------------------- > > Key: ISPN-2148 > URL: https://issues.jboss.org/browse/ISPN-2148 > Project: Infinispan > Issue Type: Enhancement > Components: Core API, Locking and Concurrency, Transactions > Affects Versions: 5.1.5.FINAL > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Priority: Minor > > I found it much easier to debug locking issues if we log the call originator in TimeoutException raised in LockingManagerImpl.java. Node that sent the call is readily available in InvocationContext#getOrigin() -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1253) Integrate the Tattletale Maven plugin into Infinispan

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1253?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1253: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Integrate the Tattletale Maven plugin into Infinispan > ----------------------------------------------------- > > Key: ISPN-1253 > URL: https://issues.jboss.org/browse/ISPN-1253 > Project: Infinispan > Issue Type: Task > Components: Build process > Reporter: Navin Surtani > Assignee: Navin Surtani > Priority: Minor > Original Estimate: 3 days > Remaining Estimate: 3 days > > Make use of the tattletale maven plugin for infinispan. This way there will not be issues similar to ISPN-1234 cropping up. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-78) Large object support

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-78?page=com.atlassian.jira.plugin.sy... ] Mircea Markus updated ISPN-78: ------------------------------ Fix Version/s: (was: 6.0.0.Final) > Large object support > -------------------- > > Key: ISPN-78 > URL: https://issues.jboss.org/browse/ISPN-78 > Project: Infinispan > Issue Type: Feature Request > Components: Core API > Reporter: Manik Surtani > Assignee: Manik Surtani > Priority: Minor > > if each VM is allocated a 2GB heap and you have a 100 nodes in a grid with 1 redundant copy for each key, you have a theoretical addressable heap of 100GB. But you are limited by (half) the heap of a single VM per entry, since entries are stored whole. > E.g., cache.put(k, my2GBObject) will fail since you need at least 2GB for the object + another 2GB for its serialized form. > This gets worse when you try cache.put(k, my10GBObject). This *should* be possible if we have a theoretical 100GB heap. > Potential solutions here are to fragment large objects, and store each fragment under separate keys. Another approach would be to directly stream objects to disk. etc. Needs thought and design, possibly a separate API to prevent 'pollution" of the more simplistic API. (JumboCache?) > Re: fragmenting, issues to overcome: > How many chunks to fragment into? Max size of each key could be configured, but how do we determine the size of an Object? VM instrumentation? Or perhaps the JumboCache only stores byte[]'s? -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1698) Lazily start transports until needed

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1698?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1698: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Lazily start transports until needed > ------------------------------------ > > Key: ISPN-1698 > URL: https://issues.jboss.org/browse/ISPN-1698 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration > Affects Versions: 5.1.0.FINAL > Reporter: Manik Surtani > Assignee: Manik Surtani > > Currently if a transport is defined in <global />, and only a local mode cache is started off this configuration, the transport is still started. This is unnecessary and the transport should only be started when the first clustered cache is started. -- 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, 9 months

1
0
0 / 0

[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: -------------------------------- Fix Version/s: 6.0.0.Final > 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 > Fix For: 6.0.0.Final > > 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

12 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2013