September 2019 - infinispan-issues

[JBoss JIRA] (ISPN-10681) Investigate and possibly convert to StampedLock for OffHeap

by Will Burns (Jira)

Will Burns created ISPN-10681: --------------------------------- Summary: Investigate and possibly convert to StampedLock for OffHeap Key: ISPN-10681 URL: https://issues.jboss.org/browse/ISPN-10681 Project: Infinispan Issue Type: Enhancement Components: Off Heap Reporter: Will Burns Assignee: Will Burns We currently use an array of ReentrantReadWriteLock entries to protect critical sections of a off heap map. We shouldn't require reentrancy for our various operations and thus we should be able to hopefully drop in replace these with the equivalent StampedLock write lock instances. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10679) 9.4.x max-idle and expiration

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10679?page=com.atlassian.jira.plugin... ] Donald Naro updated ISPN-10679: ------------------------------- Status: Open (was: New) > 9.4.x max-idle and expiration > ----------------------------- > > Key: ISPN-10679 > URL: https://issues.jboss.org/browse/ISPN-10679 > Project: Infinispan > Issue Type: Enhancement > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Need doc changes in 9.4.x to cover JDG-3204 in 7.3.3. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10679) 9.4.x max-idle and expiration

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10679?page=com.atlassian.jira.plugin... ] Donald Naro updated ISPN-10679: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7364 > 9.4.x max-idle and expiration > ----------------------------- > > Key: ISPN-10679 > URL: https://issues.jboss.org/browse/ISPN-10679 > Project: Infinispan > Issue Type: Enhancement > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Need doc changes in 9.4.x to cover JDG-3204 in 7.3.3. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10600) Create empty XSiteStateTransferManager and related classes

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10600?page=com.atlassian.jira.plugin... ] Ryan Emerson resolved ISPN-10600. --------------------------------- Resolution: Done > Create empty XSiteStateTransferManager and related classes > ---------------------------------------------------------- > > Key: ISPN-10600 > URL: https://issues.jboss.org/browse/ISPN-10600 > Project: Infinispan > Issue Type: Enhancement > Components: Cross-Site Replication > Affects Versions: 10.0.0.CR2 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 10.0.0.CR3 > > > When a cache doesn't have cross-site replication enabled, it can instantiate empty implementation of {{XSiteStateTransferManager}}, {{XSiteStateConsumer}} and {{XSiteStateProvider}} to save some memory and avoid registering uneeded listeners. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10680) Cluster Expiration should only expire primary owned entries

by Wolf-Dieter Fink (Jira)

Wolf-Dieter Fink created ISPN-10680: --------------------------------------- Summary: Cluster Expiration should only expire primary owned entries Key: ISPN-10680 URL: https://issues.jboss.org/browse/ISPN-10680 Project: Infinispan Issue Type: Enhancement Components: Expiration Affects Versions: 9.4.16.Final, 10.0.0.CR2 Reporter: Wolf-Dieter Fink Assignee: Will Burns Fix For: 10.0.0.Final, 9.4.17.Final Today cluster expiration fires for any expired entry it finds. We should instead only expire an entry when it is the primary owner encountering the entry. This will allow expiration to scale much better depending on the number of owners. This also reduces network and locking contention as we may have been sending duplicate expiration commands from backups and primary at the same time. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10679) 9.4.x max-idle and expiration

by Donald Naro (Jira)

Donald Naro created ISPN-10679: ---------------------------------- Summary: 9.4.x max-idle and expiration Key: ISPN-10679 URL: https://issues.jboss.org/browse/ISPN-10679 Project: Infinispan Issue Type: Enhancement Reporter: Donald Naro Assignee: Donald Naro Need doc changes in 9.4.x to cover JDG-3204 in 7.3.3. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10678) Cluster Expiration should only expire primary owned entries

by Will Burns (Jira)

Will Burns created ISPN-10678: --------------------------------- Summary: Cluster Expiration should only expire primary owned entries Key: ISPN-10678 URL: https://issues.jboss.org/browse/ISPN-10678 Project: Infinispan Issue Type: Enhancement Components: Expiration Affects Versions: 10.0.0.CR2, 9.4.16.Final Reporter: Will Burns Assignee: Will Burns Fix For: 10.0.0.Final, 9.4.17.Final Today cluster expiration fires for any expired entry it finds. We should instead only expire an entry when it is the primary owner encountering the entry. This will allow expiration to scale much better depending on the number of owners. This also reduces network and locking contention as we may have been sending duplicate expiration commands from backups and primary at the same time. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10677) Expiration Reaper thread should have a better name than "pool-#-thread-#"

by Wolf-Dieter Fink (Jira)

Wolf-Dieter Fink created ISPN-10677: --------------------------------------- Summary: Expiration Reaper thread should have a better name than "pool-#-thread-#" Key: ISPN-10677 URL: https://issues.jboss.org/browse/ISPN-10677 Project: Infinispan Issue Type: Enhancement Reporter: Wolf-Dieter Fink Assignee: Will Burns To be able to track expiration the thread should have a nice name like "expiration-reaper" or so that makes clear what it is and filter messages easily -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10676) Docs: max-idle expiration and xsite

by Donald Naro (Jira)

Donald Naro created ISPN-10676: ---------------------------------- Summary: Docs: max-idle expiration and xsite Key: ISPN-10676 URL: https://issues.jboss.org/browse/ISPN-10676 Project: Infinispan Issue Type: Enhancement Components: Documentation-Core Reporter: Donald Naro Assignee: Donald Naro Docs for ISPN-10650 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10672) Server default configs issues

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10672?page=com.atlassian.jira.plugin... ] Ryan Emerson resolved ISPN-10672. --------------------------------- Resolution: Done > Server default configs issues > ----------------------------- > > Key: ISPN-10672 > URL: https://issues.jboss.org/browse/ISPN-10672 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 10.0.0.CR2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.CR3 > > > The default server configuration is affected by the following issues: > * it does not set the global state shared persistent location > * they assume that user property files will use plain text password, but the user tool defaults to hashed passwords -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 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 September 2019