August 2011 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-330) Separate scheduled/unscheduled async cache store configuration

by Galder Zamarreno (JIRA)

Separate scheduled/unscheduled async cache store configuration -------------------------------------------------------------- Key: ISPN-330 URL: https://jira.jboss.org/jira/browse/ISPN-330 Project: Infinispan Issue Type: Sub-task Components: Configuration, Loaders and Stores Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.1.0.BETA1 Implement configuration that allows differentiation between scheduled/unscheduled strategies: <async enabled="true"> <scheduled frequency="1000" /> </async> <async enabled="true"> <unscheduled poolsize="50" /> </async> This format allows for easier extension of properties in scheduled/unscheduled modes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

3
5
0 / 0

[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] 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-1337) Infinispan query module: searchManagerImpl.extractType() throws exception on some OS.

by JaeHee Roh (JIRA)

Infinispan query module: searchManagerImpl.extractType() throws exception on some OS. ------------------------------------------------------------------------------------- Key: ISPN-1337 URL: https://issues.jboss.org/browse/ISPN-1337 Project: Infinispan Issue Type: Bug Components: Querying Affects Versions: 5.0.0.FINAL Environment: JAVA java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) OS # uname -ovr 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011 GNU/Linux Tested with Infinispan 5.0.0.FINAL and 5.0.0.CR8. Both versions failed on this Ubuntu platform. However, it is ok on Suse platform. # uname -ovr 2.6.16.60-0.85.1-smp #1 SMP Thu Mar 17 11:45:06 UTC 2011 GNU/Linux Reporter: JaeHee Roh Assignee: Manik Surtani Priority: Critical This is a same problem as https://issues.jboss.org/browse/ISPN-1232 which fixed in 5.0.0.CR8 and 5.0.0.FINAL but it seems that fix is working on some OS but not all of OS. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (ISPN-1141) BigMemory Direct buffer

by Magnus Magnus (JIRA)

BigMemory Direct buffer ----------------------- Key: ISPN-1141 URL: https://issues.jboss.org/browse/ISPN-1141 Project: Infinispan Issue Type: Enhancement Components: Distributed Cache Reporter: Magnus Magnus Assignee: Manik Surtani It should be configurable if data stored by NIO buffer or not. It means data stored outside of java heap. Create, destroy in the external memory should be managed by infinispan. With this solution gc can run fast however infinispan node can handle huge amount of memory. In the current case the optional size of the java memory of a node is smaller or equals than 4GB because of garbage collection issues above 4GB. See a similar thing in EHCache BigMemory. http://www.snoopal.com/documents/GaSovOTchHCsOF5X7bG691/-Scale-over-the-l... 12nd page -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

5
8
0 / 0

[JBoss JIRA] Created: (ISPN-469) HotRod client in .NET

by Manik Surtani (JIRA)

HotRod client in .NET --------------------- Key: ISPN-469 URL: https://jira.jboss.org/browse/ISPN-469 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.0.0.BETA1, 5.0.0.Final .NET client impl for HotRod. Protocol is documented here: http://community.jboss.org/wiki/HotRodProtocol Could be based off the Java reference impl client: http://fisheye.jboss.org/browse/Infinispan/trunk/client/hotrod-client -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues August 2011