May 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

11 years, 6 months

3
20
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

11 years, 7 months

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

11 years, 7 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

11 years, 7 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

11 years, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (ISPN-1090) Hot Rod protocol improvements for version 2

by Galder Zamarreño (JIRA)

Hot Rod protocol improvements for version 2 ------------------------------------------- Key: ISPN-1090 URL: https://issues.jboss.org/browse/ISPN-1090 Project: Infinispan Issue Type: Enhancement Components: Cache Server Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.1.0.BETA1, 5.1.0.Final This JIRA will act as a place to keep track of enhancements to the Hot Rod protocol that should be included in version 2 of the protocol: - We need a new error status code so that clients can detect when a node has been suspected and so react accordingly (i.e. not bubble it up but instead failover). Currently, this can be solved by checking whether the error message contains SuspectException but this is not nice. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

6
18
0 / 0

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

by Erik Salter (JIRA)

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. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

4
6
0 / 0

[JBoss JIRA] Created: (ISPN-1116) Version-aware InternalCacheEntries

by Manik Surtani (JIRA)

Version-aware InternalCacheEntries ---------------------------------- Key: ISPN-1116 URL: https://issues.jboss.org/browse/ISPN-1116 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 is to support a number of things including eventual consistency as well as tombstones for deleted entries. Further, this version would need to be used when doing MVCC concurrent write comparisons for write skews (and not just a reference check which is done at the moment). This also would need to be able to use versions provided in a value's metadata (see ISPN-1103) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

9
17
0 / 0

[JBoss JIRA] Created: (ISPN-871) Out-of-heap data container implementation

by Manik Surtani (JIRA)

Out-of-heap data container implementation ----------------------------------------- Key: ISPN-871 URL: https://issues.jboss.org/browse/ISPN-871 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 The DataContainer interface could be implemented using a off-heap impl in C, using mmap. It would require custom memory management (gc-lite?) to reclaim free space, as well as reimplementing of eviction algorithms to maintain the contract of a self-sizing data container, but the benefits of this would be the ability to address very large amounts of memory with minimal gc overhead from the JVM. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

6
16
0 / 0

[JBoss JIRA] Created: (ISPN-863) Eviction based on JVM memory utilization

by Dave Marion (JIRA)

Eviction based on JVM memory utilization ---------------------------------------- Key: ISPN-863 URL: https://issues.jboss.org/browse/ISPN-863 Project: Infinispan Issue Type: Enhancement Components: Eviction Affects Versions: 4.2.0.Final Environment: N/A Reporter: Dave Marion Assignee: Manik Surtani Allow user to specify percentage threshold upon which eviction will kick in and begin evicting entries based on the specified strategy. This would allow user to create a cache that will attempt to keep as many entries in memory as possible without having to specify maxEntries. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

8
38
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2011