January 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9082) Off Heap maxIdle expiration is not implemented

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-9082?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-9082: ----------------------------- Summary: Off Heap maxIdle expiration is not implemented (was: Off Heap maxIdle expiration works like lifespan) > Off Heap maxIdle expiration is not implemented > ---------------------------------------------- > > Key: ISPN-9082 > URL: https://issues.redhat.com/browse/ISPN-9082 > Project: Infinispan > Issue Type: Bug > Components: Expiration, Off Heap > Affects Versions: 9.2.1.Final > Reporter: Will Burns > Priority: Major > > Due to the usage of read/write locks Off Heap cannot easily update the last access time of an off heap entry. It would have to release the read lock and try to acquire the write lock to then finally update the last access time of an object. We would also have to guarantee the address pointer hadn't changed between when the read and write lock were obtained, since the value could have changed during that time period. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10840) Doc Productization: Programmatic Configuration

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-10840?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-10840: ------------------------------- Sprint: DataGrid Sprint #39 > Doc Productization: Programmatic Configuration > ---------------------------------------------- > > Key: ISPN-10840 > URL: https://issues.redhat.com/browse/ISPN-10840 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Affects Versions: 10.0.0.Final > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Update and review chapter on programmatic configuration. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10839) Doc Productization: Declarative Configuration

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-10839?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-10839: ------------------------------- Sprint: DataGrid Sprint #39 > Doc Productization: Declarative Configuration > --------------------------------------------- > > Key: ISPN-10839 > URL: https://issues.redhat.com/browse/ISPN-10839 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Affects Versions: 10.0.0.Final > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Update and review chapter on declarative configuration. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10847) Doc Productization: Clustered and Local Cache Modes

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-10847?page=com.atlassian.jira.plugi... ] Donald Naro closed ISPN-10847. ------------------------------ > Doc Productization: Clustered and Local Cache Modes > --------------------------------------------------- > > Key: ISPN-10847 > URL: https://issues.redhat.com/browse/ISPN-10847 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Affects Versions: 10.0.0.Final > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Configuration Guide > 2. Local Caches > 3. Clustered Caches > Needs to be productized, reviewed, updated, synced with product docs at: https://access.redhat.com/documentation/en-us/red_hat_data_grid/7.2/html-... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10847) Doc Productization: Clustered and Local Cache Modes

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-10847?page=com.atlassian.jira.plugi... ] Donald Naro resolved ISPN-10847. -------------------------------- Resolution: Done ISPN-10605 > Doc Productization: Clustered and Local Cache Modes > --------------------------------------------------- > > Key: ISPN-10847 > URL: https://issues.redhat.com/browse/ISPN-10847 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Affects Versions: 10.0.0.Final > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Configuration Guide > 2. Local Caches > 3. Clustered Caches > Needs to be productized, reviewed, updated, synced with product docs at: https://access.redhat.com/documentation/en-us/red_hat_data_grid/7.2/html-... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10633) Doc Productization: xincludes for JGroups configuration

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-10633?page=com.atlassian.jira.plugi... ] Donald Naro resolved ISPN-10633. -------------------------------- Resolution: Duplicate Issue ISPN-10605 > Doc Productization: xincludes for JGroups configuration > ------------------------------------------------------- > > Key: ISPN-10633 > URL: https://issues.redhat.com/browse/ISPN-10633 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Affects Versions: 10.0.0.Final > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10633) Doc Productization: xincludes for JGroups configuration

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-10633?page=com.atlassian.jira.plugi... ] Donald Naro closed ISPN-10633. ------------------------------ > Doc Productization: xincludes for JGroups configuration > ------------------------------------------------------- > > Key: ISPN-10633 > URL: https://issues.redhat.com/browse/ISPN-10633 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Affects Versions: 10.0.0.Final > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10633) Doc Productization: xincludes for JGroups configuration

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-10633?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-10633: ------------------------------- Description: (was: Documentation for xinclude statements for JGroups configuration.) > Doc Productization: xincludes for JGroups configuration > ------------------------------------------------------- > > Key: ISPN-10633 > URL: https://issues.redhat.com/browse/ISPN-10633 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Affects Versions: 10.0.0.Final > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11129) High Availability for non-shared indexes on DIST caches

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-11129?page=com.atlassian.jira.plugi... ] Work on ISPN-11129 started by Gustavo Fernandes. ------------------------------------------------ > High Availability for non-shared indexes on DIST caches > ------------------------------------------------------- > > Key: ISPN-11129 > URL: https://issues.redhat.com/browse/ISPN-11129 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > > 'Non-shared indexes' is a setup when each node has a local index backed by the file system, using either the near-real-time or the FS index managers. > For REPL caches, a full copy of the index is kept in each node. As long as at least on node is up the queries hit the local index which represents the full index of the data. > But non-shared indexes has some drawbacks for DIST caches: each node only indexes data that the node is the primary owner. If a node goes down, there is no redundancy. This issue aims to solve this issue at two levels: > * Indexing: replicated entries should be indexed for redundancy purposes. If a primary owner goes down, the entry is indexed in the backup owner. This should follow exactly the data distribution on the cache in terms of number of replicas and rebalancing > * Querying: query broadcast is currently used for non-shared indexes. If replicated entries start to be indexed, a mechanism will have to be used to avoid retuning repeated results, since currently the broadcast simply queries all the entries in each node and join the result. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11183) Clustered Max Idle should not have to catch TimeoutException for optimistic writes

by Will Burns (Jira)

Will Burns created ISPN-11183: --------------------------------- Summary: Clustered Max Idle should not have to catch TimeoutException for optimistic writes Key: ISPN-11183 URL: https://issues.redhat.com/browse/ISPN-11183 Project: Infinispan Issue Type: Bug Reporter: Will Burns Assignee: Will Burns ISPN-11020 introduced a new implementation of clustered max idle. Due to how locking in optimistic transactions work and the fact that we try to limit the number of expiration removals for a key it can cause a deadlock. To work around this we ensure that reads use a lock acquisition timeout of 0 and catch and check the exception for a TimeoutException. Exception checking is inherently error prone as the cause/supression of exceptions can change very easily as well as the exception could be thrown for a different reason. We should convert this by possibly changing OptimisticLockingInterceptor to return something different if a lock occurs with a lock acquisition timeout of 0. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2020