May 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4196) Local transaction not removed from transaction table with keySet, entrySet, values operations

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4196?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4196: ----------------------------------------------- Martin Gencur <mgencur(a)redhat.com> changed the Status of [bug 1087281|https://bugzilla.redhat.com/show_bug.cgi?id=1087281] from ON_QA to VERIFIED > Local transaction not removed from transaction table with keySet, entrySet, values operations > --------------------------------------------------------------------------------------------- > > Key: ISPN-4196 > URL: https://issues.jboss.org/browse/ISPN-4196 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 7.0.0.Alpha1 > Reporter: Adrian Nistor > Assignee: Martin Gencur > Fix For: 7.0.0.Alpha4, 7.0.0.Final > > > The cleanup phase of FilesystemQueryDslIterationTest of this test is based on Cache.clear() and is very slow , taking about 30 seconds, or at least that's how much we gain if the cache cleanup is removed. Without the cleanup, this test takes about 2.5 seconds, so we need to investigate why Cache.clear() creates a problem here or in general. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4119) Merge JPA Cache Store back into main repo

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4119?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4119: ----------------------------------------------- Martin Gencur <mgencur(a)redhat.com> changed the Status of [bug 1077101|https://bugzilla.redhat.com/show_bug.cgi?id=1077101] from ON_QA to VERIFIED > Merge JPA Cache Store back into main repo > ----------------------------------------- > > Key: ISPN-4119 > URL: https://issues.jboss.org/browse/ISPN-4119 > Project: Infinispan > Issue Type: Task > Components: Loaders and Stores > Affects Versions: 7.0.0.Alpha1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 7.0.0.Alpha2, 7.0.0.Final > > > The JPA CacheStore should move back into the main repository. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4081) JBoss Marshalling 1.4.4.Final (ASL)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4081?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4081: ----------------------------------------------- Martin Gencur <mgencur(a)redhat.com> changed the Status of [bug 1090040|https://bugzilla.redhat.com/show_bug.cgi?id=1090040] from ON_QA to VERIFIED > JBoss Marshalling 1.4.4.Final (ASL) > ----------------------------------- > > Key: ISPN-4081 > URL: https://issues.jboss.org/browse/ISPN-4081 > Project: Infinispan > Issue Type: Component Upgrade > Affects Versions: 6.0.1.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Labels: 630 > Fix For: 6.0.2.Final, 7.0.0.Alpha2, 7.0.0.Final > > > JBoss Marshalling 1.4.4.Final has been licensed under the ASL (and fixes a couple of bugs). -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4097) Add SKIP_CACHE_LOAD flag for Hot Rod

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4097?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-4097: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Add SKIP_CACHE_LOAD flag for Hot Rod > ------------------------------------ > > Key: ISPN-4097 > URL: https://issues.jboss.org/browse/ISPN-4097 > Project: Infinispan > Issue Type: Feature Request > Components: Server > Reporter: Galder Zamarreño > Assignee: Pedro Ruivo > Labels: 630 > Fix For: 7.0.0.Alpha4, 7.0.0.Final > > > Add SKIP_CACHE_LOAD flag to Hot Rod protocol to allow for data to be not be loaded from the cache store. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4217) Use ArrayList instead of LinkedList for DeltaAware and Delta in M/R

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-4217?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-4217: ------------------------------------- You should also take a look at ArrayDeque, depending on what you need. I normally use ArrayList as my fallback collection, but more recently I have been using ArrayDeque which seems even better. > Use ArrayList instead of LinkedList for DeltaAware and Delta in M/R > ------------------------------------------------------------------- > > Key: ISPN-4217 > URL: https://issues.jboss.org/browse/ISPN-4217 > Project: Infinispan > Issue Type: Enhancement > Components: Distributed Execution and Map/Reduce > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > > Investigate switching to ArrayList as implementation of DeltaAware and Delta as ArrayList uses less memory than LinkedList. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4217) Use ArrayList instead of LinkedList for DeltaAware and Delta in M/R

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-4217?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic commented on ISPN-4217: ------------------------------------------- ArrayList is less memory intensive than Linked List [1] [2] [1] http://stackoverflow.com/questions/11564352/arraylist-vs-linkedlist-from-... [2] https://code.google.com/p/memory-measurer/wiki/ElementCostInDataStructures > Use ArrayList instead of LinkedList for DeltaAware and Delta in M/R > ------------------------------------------------------------------- > > Key: ISPN-4217 > URL: https://issues.jboss.org/browse/ISPN-4217 > Project: Infinispan > Issue Type: Enhancement > Components: Distributed Execution and Map/Reduce > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > > Investigate switching to ArrayList as implementation of DeltaAware and Delta as ArrayList uses less memory than LinkedList. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3967) Create a feature file for HotRod client for easy installation in Karaf

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3967?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3967: ----------------------------------------------- Martin Gencur <mgencur(a)redhat.com> changed the Status of [bug 1083017|https://bugzilla.redhat.com/show_bug.cgi?id=1083017] from NEW to POST > Create a feature file for HotRod client for easy installation in Karaf > ---------------------------------------------------------------------- > > Key: ISPN-3967 > URL: https://issues.jboss.org/browse/ISPN-3967 > Project: Infinispan > Issue Type: Feature Request > Reporter: Martin Gencur > Assignee: Martin Gencur > Labels: 630, 630betablocker > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > A "feature" file is a descriptor of bundles required by a feature. (More info at http://icodebythesea.blogspot.cz/2012/03/making-osgi-deployments-easier-w...) > We should provide such a file for easy deployment on Karaf. Otherwise users will have to install all artifacts one by one (jboss-loggin, jgroups, infinispan-commons, infinispan-core, commons-pool, jboss-marshalling-osgi, ...) -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4259) lucene index directory lock by multiple embedded cache

by Gaetan talmant (JIRA)

Gaetan talmant created ISPN-4259: ------------------------------------ Summary: lucene index directory lock by multiple embedded cache Key: ISPN-4259 URL: https://issues.jboss.org/browse/ISPN-4259 Project: Infinispan Issue Type: Feature Request Components: Configuration, Embedded Querying Affects Versions: 6.0.2.Final Environment: software plateform Reporter: Gaetan talmant Assignee: Dan Berindei Fix For: 6.0.2.Final While creating Infinispan Cache, i noticed Apache Lucene was used. But i can't find any place to configure where Lucene Directories/Files should be created. My infinispan jars is embedded throughout 6 different tomcat on the same physical server, and the consequence is i have only one lucene directory shared for my multiple tomcats. (directory created in ~) How could we configure lucene directory path ? -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3894) SingleFileStore can optimize space usage by coalescing adjacent free entry blocks.

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3894?page=com.atlassian.jira.plugin.... ] Dan Berindei reassigned ISPN-3894: ---------------------------------- Assignee: Dan Berindei (was: Mircea Markus) > SingleFileStore can optimize space usage by coalescing adjacent free entry blocks. > ---------------------------------------------------------------------------------- > > Key: ISPN-3894 > URL: https://issues.jboss.org/browse/ISPN-3894 > Project: Infinispan > Issue Type: Patch > Components: Loaders and Stores > Affects Versions: 6.0.0.Final > Environment: Oracle JDK 1.7, Windows Server 2008 R2 > Reporter: Rajesh Jangam > Assignee: Dan Berindei > Fix For: 7.0.0.Alpha4 > > Attachments: CoalesceEntries.java > > > This issue is related to issue ISPN-3877. > Here we have a use case where the size of the entries gradually keeps on increasing and then finally those entries expire. > 1. Smaller entries expire and new bigger entries start getting added > 2. These new bigger entries will not fit into the free slots (entries) created due to the expiry of smaller entries. > 3. Thus, these new bigger entries only get allocated at the end of the file resulting in growth of file size. > The optimization proposed is to: > 1. Coalesce/Combine adjacent free entries during the periodic purge cycle to create bigger/larger free entries. > 2. While allocating from an existing free entry, check if the size of the free entry is more than required for the new request being allocated. If yes, then, split the free entry into two free entries: > a. First part equal to the length being requested > This is returned as a part of the allocation activity. > b. Second part equal to the remainder of the space. > This added back as a free entry to the freeList. > Thus free space created due to expiry of smaller entries becomes available for consumption for the larger entries to some extent. > This reduces file size of the store. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3894) SingleFileStore can optimize space usage by coalescing adjacent free entry blocks.

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3894?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3894: ------------------------------- Status: Pull Request Sent (was: Open) > SingleFileStore can optimize space usage by coalescing adjacent free entry blocks. > ---------------------------------------------------------------------------------- > > Key: ISPN-3894 > URL: https://issues.jboss.org/browse/ISPN-3894 > Project: Infinispan > Issue Type: Patch > Components: Loaders and Stores > Affects Versions: 6.0.0.Final > Environment: Oracle JDK 1.7, Windows Server 2008 R2 > Reporter: Rajesh Jangam > Assignee: Mircea Markus > Fix For: 7.0.0.Alpha4 > > Attachments: CoalesceEntries.java > > > This issue is related to issue ISPN-3877. > Here we have a use case where the size of the entries gradually keeps on increasing and then finally those entries expire. > 1. Smaller entries expire and new bigger entries start getting added > 2. These new bigger entries will not fit into the free slots (entries) created due to the expiry of smaller entries. > 3. Thus, these new bigger entries only get allocated at the end of the file resulting in growth of file size. > The optimization proposed is to: > 1. Coalesce/Combine adjacent free entries during the periodic purge cycle to create bigger/larger free entries. > 2. While allocating from an existing free entry, check if the size of the free entry is more than required for the new request being allocated. If yes, then, split the free entry into two free entries: > a. First part equal to the length being requested > This is returned as a part of the allocation activity. > b. Second part equal to the remainder of the space. > This added back as a free entry to the freeList. > Thus free space created due to expiry of smaller entries becomes available for consumption for the larger entries to some extent. > This reduces file size of the store. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 12 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2014