October 2011 - infinispan-issues - Jboss List Archives

[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-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

[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

[JBoss JIRA] Created: (ISPN-557) support for same transaction touching multiple nodes (multiple VMs)

by Mircea Markus (JIRA)

support for same transaction touching multiple nodes (multiple VMs) -------------------------------------------------------------------- Key: ISPN-557 URL: https://jira.jboss.org/browse/ISPN-557 Project: Infinispan Issue Type: Feature Request Components: Transactions Reporter: Mircea Markus Assignee: Manik Surtani Fix For: 5.1.0.Final E.g. if a distributed transaction managers touches two embedded Infinispan nodes within the same transaction. Could be implemented using the Hot Rod client approach - but in an embedded fashion! EmbeddedClient <-- implements logic above Except comms are in-VM for local entries And via RpcDispatcher for remote entries RemoteClient extends EmbeddedClient Adds proper HotRod layer for comms Including failover, smart routing, etc. -- 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

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2011