March 2012 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-1103) Soft schema-based storage

by Manik Surtani (JIRA)

Soft schema-based storage ------------------------- Key: ISPN-1103 URL: https://issues.jboss.org/browse/ISPN-1103 Project: Infinispan Issue Type: Feature Request Components: Core API Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.1.0.BETA1, 5.1.0.Final This JIRA is about storing metadata alongside values. Perhaps encapsulating values as SchematicValues, which could be described as: {code} class SchematicValue { String jsonMetadata; String jsonObject; } {code} Metadata would allow for a few interesting features: * Extracting of lifespan and timestamp data if manipulated over a remote protocol (REST, HotRod, etc) * Content type for REST responses * Timestamps for REST headers, will affect HTTP content caches * Validation information (may not be processed by Infinispan, but can be used by client libs) * Classloader/marshaller/classdef version info * General structure of the information stored -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

8
22
0 / 0

[JBoss JIRA] Created: (ISPN-939) Index corruption when remote node dies during commit

by Tristan Tarrant (JIRA)

Index corruption when remote node dies during commit ---------------------------------------------------- Key: ISPN-939 URL: https://issues.jboss.org/browse/ISPN-939 Project: Infinispan Issue Type: Bug Components: Lucene Directory Affects Versions: 4.2.1.CR2 Reporter: Tristan Tarrant Assignee: Sanne Grinovero Using a scenario similar to the one described in ISPN-909: Infinispan: 3 caches: lockCache (replicated, volatile, no eviction), metadataCache (replicated, persisted, no eviction), dataCache (distributed, persisted, eviction, hash numOwners=2) Node 1: coordinator, IndexWriter open constantly and writing a stream of documents, committing after each one Node 2: opens a read-only IndexReader to perform queries, using reopen to keep in sync with the updates coming from node 1 If we "kill -9" node 2 (to simulate a crash), we get a SuspectException in node 1 during the pre-commit phase (within IndexWriter.commit()). Catching the Throwable we then close() the writer but from then on we get "Read past EOF" errors when trying to access the index (both with readers and writers). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

3
20
0 / 0

[JBoss JIRA] Created: (ISPN-1313) Execution timeout should not be linked to replication timeout

by Thomas Peuss (JIRA)

Execution timeout should not be linked to replication timeout ------------------------------------------------------------- Key: ISPN-1313 URL: https://issues.jboss.org/browse/ISPN-1313 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 5.0.0.CR8 Reporter: Thomas Peuss Assignee: Manik Surtani Currently the timeout of a distributed execution is linked to the settings for the replication timeout (we have set the timeout to <sync replTimeout="120000"/> as a workaround). For long running tasks this is really annoying because you get an error back from the framework but the distributed tasks runs till the end without a problem. There should be an extra timeout for the execution of distributed tasks. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

4
8
0 / 0

[JBoss JIRA] (ISPN-1513) Enhance distributed executor framework to be more topology aware

by David B (Created) (JIRA)

Enhance distributed executor framework to be more topology aware ---------------------------------------------------------------- Key: ISPN-1513 URL: https://issues.jboss.org/browse/ISPN-1513 Project: Infinispan Issue Type: Enhancement Components: Distributed Cache Affects Versions: 5.0.1.FINAL Reporter: David B Assignee: Manik Surtani Priority: Minor Our environment has 2 local infinispan/jgroups clusters with a jgroups relay cluster to handle geographic failover. Our sites are geographically distant over a WAN. Currently DistributedExecutorService's submitEverywhere() sends Callables to every node in both local clusters. We would rather have additional methods provided to DistributedExecutorService to constrain submission on Callables to the same/local site. Currently I have extended DefaultExecutorService with my own TopologyAwareExecutorService and added a submitSameSite() method using the TopologyAwareAddress.isSameSite(). I did need to patch DistributedRunnableFuture in DefaultExecutorService to mark it protected vs. private. This could be extended to also provide submitSameRack() & submitSameMachine() though currently we don't have a use case for that. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

6
8
0 / 0

[JBoss JIRA] (ISPN-1524) Make configuration of cache stores fluent

by Pete Muir (Created) (JIRA)

Make configuration of cache stores fluent ----------------------------------------- Key: ISPN-1524 URL: https://issues.jboss.org/browse/ISPN-1524 Project: Infinispan Issue Type: Feature Request Components: Configuration, Loaders and Stores Affects Versions: 5.1.0.BETA4 Reporter: Pete Muir Assignee: Manik Surtani Fix For: 5.2.0.FINAL -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
2
0 / 0

[JBoss JIRA] (ISPN-1827) De-couple cache view installation and state transfer (consistent hash installation)s

by Dan Berindei (JIRA)

Dan Berindei created ISPN-1827: ---------------------------------- Summary: De-couple cache view installation and state transfer (consistent hash installation)s Key: ISPN-1827 URL: https://issues.jboss.org/browse/ISPN-1827 Project: Infinispan Issue Type: Task Components: State transfer Affects Versions: 5.1.0.FINAL Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 5.2.0.FINAL We need to know the primary owner of a key in order to do pretty much anything, and every member of a cache view should compute the same primary owner at all times. So we need a 2PC cache view installation immediately after any leave to ensure that every node determines the primary owner in the same way - we can't coalesce leaves. However, it's highly desirable to coalesce state transfers caused by a node leaving - perhaps because we are shutting down half of the cluster to do an upgrade. So we should separate the state transfer from the cache view installation, and each one should have its own 2PC process. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (ISPN-1192) Map/Reduce over REST

by Manik Surtani (JIRA)

Map/Reduce over REST -------------------- Key: ISPN-1192 URL: https://issues.jboss.org/browse/ISPN-1192 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.2.0.Final Allow Map/Reduce tasks to be executed over REST -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
2
0 / 0

[JBoss JIRA] Created: (ISPN-1094) Map/Reduce over HotRod

by Galder Zamarreño (JIRA)

Map/Reduce over HotRod ---------------------- Key: ISPN-1094 URL: https://issues.jboss.org/browse/ISPN-1094 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Galder Zamarreño Assignee: Manik Surtani Map/Reduce over HotRod. Most probably we'll settle on portable javascript code to be executable remotely. More info in the discussion thread. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

7
13
0 / 0

[JBoss JIRA] Created: (ISPN-1284) change default tx enlistment

by Mircea Markus (JIRA)

change default tx enlistment ---------------------------- Key: ISPN-1284 URL: https://issues.jboss.org/browse/ISPN-1284 Project: Infinispan Issue Type: Feature Request Components: Configuration, Transactions Affects Versions: 5.0.0.CR8 Reporter: Mircea Markus Assignee: Mircea Markus Fix For: 5.1.0.ALPHA1, 5.1.0.FINAL ATM transactions are being enlisted as XAResources with recovery disabled. XAResource enlistment *without* recovery does not bring any benefit over Synchronization enlistment, which is more efficient(30-40%): http://infinispan.blogspot.com/2011/06/transactions-enhancements-in-50.html So the suggested enlistment should be Synchronization (default). Also if xa-enlistment is preferred then recovery should be enabled by default - there's little reason in using XAResource enlistment without recovery. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

9
27
0 / 0

[JBoss JIRA] Created: (ISPN-1409) Introduce a binary-stream upgrading CacheLoader

by Sanne Grinovero (JIRA)

Introduce a binary-stream upgrading CacheLoader ----------------------------------------------- Key: ISPN-1409 URL: https://issues.jboss.org/browse/ISPN-1409 Project: Infinispan Issue Type: Feature Request Reporter: Sanne Grinovero Assignee: Manik Surtani Fix For: 5.1.0.BETA1 We need a CacheLoader decorator able to chain sets of two different Externalizers which are targeting the same Java type to transform from one binary format to the next binary format. Example: a Person object stored in the cache and an Externalizer is coupled to it. In a new release the Externalizer is changed to provide a different binary representation. Using the old one the stream is transformed from a byte[] to a Person, then this Java instance is feed to the new Externalizer implementation to get the new corresponding byte[]; the updated stream is stored in the decorated CacheLoader so that the nodes going to be attached to the cache store and using the new Externalizer will be fine. A little complexity is introduced if the cache has to know about different sets of Externalizers if several different types need to be upgraded. A possible solution is to use a single decorator instance for each type, creating a chain of decorators if they are able to pass "as is" each externalizer id they are not directly coupled to. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

5
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2012