March 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5301) Make CompositeNotifyingFuture more generic

by Gustavo Fernandes (JIRA)

Gustavo Fernandes created ISPN-5301: --------------------------------------- Summary: Make CompositeNotifyingFuture more generic Key: ISPN-5301 URL: https://issues.jboss.org/browse/ISPN-5301 Project: Infinispan Issue Type: Task Components: Core Affects Versions: 7.2.0.Alpha1 Reporter: Gustavo Fernandes -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5258) Upgrade to Hibernate Search 5.1.1.Final, Apache Lucene 4.10.4

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-5258?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-5258: ---------------------------------- Status: Open (was: New) > Upgrade to Hibernate Search 5.1.1.Final, Apache Lucene 4.10.4 > ------------------------------------------------------------- > > Key: ISPN-5258 > URL: https://issues.jboss.org/browse/ISPN-5258 > Project: Infinispan > Issue Type: Component Upgrade > Components: Embedded Querying, Lucene Directory > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 7.2.0.Beta1, 7.1.2.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5258) Upgrade to Hibernate Search 5.1.1.Final, Apache Lucene 4.10.4

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-5258?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-5258: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3308 > Upgrade to Hibernate Search 5.1.1.Final, Apache Lucene 4.10.4 > ------------------------------------------------------------- > > Key: ISPN-5258 > URL: https://issues.jboss.org/browse/ISPN-5258 > Project: Infinispan > Issue Type: Component Upgrade > Components: Embedded Querying, Lucene Directory > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 7.2.0.Beta1, 7.1.2.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5258) Upgrade to Hibernate Search 5.1.1.Final, Apache Lucene 4.10.4

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-5258?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-5258: ---------------------------------- Summary: Upgrade to Hibernate Search 5.1.1.Final, Apache Lucene 4.10.4 (was: Upgrade to Hibernate Search 5.1.0.Final, Apache Lucene 4.10.4) > Upgrade to Hibernate Search 5.1.1.Final, Apache Lucene 4.10.4 > ------------------------------------------------------------- > > Key: ISPN-5258 > URL: https://issues.jboss.org/browse/ISPN-5258 > Project: Infinispan > Issue Type: Component Upgrade > Components: Embedded Querying, Lucene Directory > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 7.2.0.Beta1, 7.1.2.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-4810) Local Transactional Cache loses data when eviction is enabled and there are multiple readers and one writer

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4810?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4810: ------------------------------- Fix Version/s: 7.2.0.Beta1 5.2.11.Final > Local Transactional Cache loses data when eviction is enabled and there are multiple readers and one writer > ----------------------------------------------------------------------------------------------------------- > > Key: ISPN-4810 > URL: https://issues.jboss.org/browse/ISPN-4810 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.2.Final > Environment: Windows 7 x64 (NTFS) > Oracle JDK1.7.0_40 > Apache Maven 3.0.5 > Reporter: Horia Chiorean > Assignee: William Burns > Labels: modeshape > Fix For: 7.2.0.Beta1, 5.2.11.Final > > Attachments: ispn_concurrent.zip > > > Using Infinispan 6.0.2 and a local, transactional cache backed by a <singleFile> store, with eviction enabled and a small {{max-entries}} setting, we have the following scenario: > * the main thread (i.e. the "writer") starts a transaction, adds a batch of strings into the cache and also appends the same strings into a List cache entry and then commits the transaction > * after the above has finished (i.e. after tx.commit) it fires a number of reader threads where each reader thread > ** checks that the string entries were added into the cache and > ** checks that the entries were correctly appended to the List entry > * the above steps are repeated a number of times > On any given run, based on timing, we're seeing that at some point (after some time) some of the reader threads will not see the latest version of the List entry (i.e. will not see the latest elements that were added into the list) but rather an old, stale List (sort of a "lost update" scenario). > If we either: > * disable eviction or > * set the {{max-entries}} to a large enough value (which I suspect has the same effect - not evicting anything) the problem doesn't show up. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3023) Re-implement BoundedConcurrentHashMap using CHMv8 designs

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3023?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3023: ------------------------------- Fix Version/s: 5.2.11.Final > Re-implement BoundedConcurrentHashMap using CHMv8 designs > --------------------------------------------------------- > > Key: ISPN-3023 > URL: https://issues.jboss.org/browse/ISPN-3023 > Project: Infinispan > Issue Type: Feature Request > Components: Core, Eviction > Affects Versions: 5.2.5.Final > Reporter: Manik Surtani > Assignee: William Burns > Priority: Minor > Labels: performance > Fix For: 7.2.0.Final, 5.2.11.Final > > > This is better than the current segment-based approach, in terms of memory footprint as well as performance under high concurrency. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5298) HotRod millisecond precision for lifespan/maxidle

by Ion Savin (JIRA)

[ https://issues.jboss.org/browse/ISPN-5298?page=com.atlassian.jira.plugin.... ] Ion Savin commented on ISPN-5298: --------------------------------- We could add 2 new optional (defaulting to 0) vInt fields to HotRod for the sub-second part with TimeUnit.NANOSECOND precision. > HotRod millisecond precision for lifespan/maxidle > ------------------------------------------------- > > Key: ISPN-5298 > URL: https://issues.jboss.org/browse/ISPN-5298 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols > Affects Versions: 7.2.0.Alpha1 > Reporter: Ion Savin > > Currently lifespan/maxidle precision is SECONDS. > JSR-107 requires MILLISECONDS precision. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5300) CacheEventFilterAsKeyValueFilter must pass the value and metadata as 'new' to the underlying CacheEventFilter

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5300?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5300: -------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/3297, https://github.com/infinispan/infinispan/pull/3307 (was: https://github.com/infinispan/infinispan/pull/3297) > CacheEventFilterAsKeyValueFilter must pass the value and metadata as 'new' to the underlying CacheEventFilter > ------------------------------------------------------------------------------------------------------------- > > Key: ISPN-5300 > URL: https://issues.jboss.org/browse/ISPN-5300 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.Beta1, 7.2.0.Final, 7.1.2.Final > > > Current implementetion passes the value as old value to the wrapped filter. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5295) Remote cache entries with sub-second lifetime never expire

by Ion Savin (JIRA)

[ https://issues.jboss.org/browse/ISPN-5295?page=com.atlassian.jira.plugin.... ] Ion Savin edited comment on ISPN-5295 at 3/13/15 11:39 AM: ----------------------------------------------------------- Opened another issue for MILLISECOND precision over hotrod https://issues.jboss.org/browse/ISPN-5298 was (Author: isavin): Open another issue for MILLISECOND precision over hotrod https://issues.jboss.org/browse/ISPN-5298 > Remote cache entries with sub-second lifetime never expire > ---------------------------------------------------------- > > Key: ISPN-5295 > URL: https://issues.jboss.org/browse/ISPN-5295 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 7.2.0.Alpha1 > Reporter: Ion Savin > > remoteCache.put("key", "value", 999, TimeUnit.MILLISECOND) > Expected: the entry expires after 999 millis > Actual: the entry never expires > HotRod lifespan is specified with second granularity but during conversion the subsecond part is truncated: > remoteCache.put("key", "value", 1999, TimeUnit.MILLISECOND) > Expected: after 1998 millis the entry is still present > Actual: after 1000 millis the entry is expired -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5300) CacheEventFilterAsKeyValueFilter must pass the value and metadata as 'new' to the underlying CacheEventFilter

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5300?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5300: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3297 > CacheEventFilterAsKeyValueFilter must pass the value and metadata as 'new' to the underlying CacheEventFilter > ------------------------------------------------------------------------------------------------------------- > > Key: ISPN-5300 > URL: https://issues.jboss.org/browse/ISPN-5300 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.Beta1, 7.2.0.Final, 7.1.2.Final > > > Current implementetion passes the value as old value to the wrapped filter. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2015