May 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4688) Backport to 5.2.x for EAP 6.4

by Dennis Reed (JIRA)

[ https://issues.jboss.org/browse/ISPN-4688?page=com.atlassian.jira.plugin.... ] Dennis Reed updated ISPN-4688: ------------------------------ Fix Version/s: 5.2.11.Final (was: 5.2.10.Final) Wrong fixed in version -- this was in 5.2.11, not 5.2.10. > Backport to 5.2.x for EAP 6.4 > ----------------------------- > > Key: ISPN-4688 > URL: https://issues.jboss.org/browse/ISPN-4688 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 5.2.8.Final > Reporter: Paul Ferraro > Assignee: Dan Berindei > Priority: Critical > Fix For: 5.2.11.Final > > > Tracking jira for backporting fixes to 5.2.x for EAP 6.4. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5345) Allow eviction for based on approximation of size compared to element count

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5345?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5345: -------------------------------- Status: Open (was: New) > Allow eviction for based on approximation of size compared to element count > --------------------------------------------------------------------------- > > Key: ISPN-5345 > URL: https://issues.jboss.org/browse/ISPN-5345 > Project: Infinispan > Issue Type: Enhancement > Components: Eviction > Reporter: William Burns > Assignee: William Burns > Fix For: 8.0.0.Final > > > It would be nice to have a bounded container that allows for eviction based on how much memory approximately the various arrays would take up. > If possible we may even to enhance the data container to have a callback to provide a user specified way of calculating size for non byte[] values. > This implementation would not know anything about duplicate references in the container and would count it double. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5345) Allow eviction for based on approximation of size compared to element count

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5345?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5345: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3467 > Allow eviction for based on approximation of size compared to element count > --------------------------------------------------------------------------- > > Key: ISPN-5345 > URL: https://issues.jboss.org/browse/ISPN-5345 > Project: Infinispan > Issue Type: Enhancement > Components: Eviction > Reporter: William Burns > Assignee: William Burns > Fix For: 8.0.0.Final > > > It would be nice to have a bounded container that allows for eviction based on how much memory approximately the various arrays would take up. > If possible we may even to enhance the data container to have a callback to provide a user specified way of calculating size for non byte[] values. > This implementation would not know anything about duplicate references in the container and would count it double. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5470) Remote-executor threads should not block to acquire locks

by Dan Berindei (JIRA)

Dan Berindei created ISPN-5470: ---------------------------------- Summary: Remote-executor threads should not block to acquire locks Key: ISPN-5470 URL: https://issues.jboss.org/browse/ISPN-5470 Project: Infinispan Issue Type: Task Components: Core Affects Versions: 7.2.1.Final Reporter: Dan Berindei Fix For: 8.0.0.Alpha1 Currently, enabling the queue on the remote-executor thread pool can cause deadlocks, because a CommitCommand/1PCPrepareCommand could end up in the queue while a remote-executor thread is busy waiting to acquire the same lock that this commit would release. If trying to acquire a lock would free the thread until the key has been acquired, we could enable the queue on the remote-executor/OOB thread pools, and we would need a lot less threads for the same load. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5469) Remote-executor threads should not block during RPCs

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5469?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5469: ------------------------------- Summary: Remote-executor threads should not block during RPCs (was: Remote command invocations should not block the caller thread) > Remote-executor threads should not block during RPCs > ---------------------------------------------------- > > Key: ISPN-5469 > URL: https://issues.jboss.org/browse/ISPN-5469 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 7.2.1.Final > Reporter: Dan Berindei > Fix For: 8.0.0.Alpha1 > > > This is particularly important in non-transactional caches, where the primary owner has to forward a command to the backup owners. The remote-executor thread on the primary should not be blocked while waiting for the backup responses, and instead process other commands. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5469) Remote command invocations should not block the caller thread

by Dan Berindei (JIRA)

Dan Berindei created ISPN-5469: ---------------------------------- Summary: Remote command invocations should not block the caller thread Key: ISPN-5469 URL: https://issues.jboss.org/browse/ISPN-5469 Project: Infinispan Issue Type: Task Components: Core Affects Versions: 7.2.1.Final Reporter: Dan Berindei Fix For: 8.0.0.Alpha1 This is particularly important in non-transactional caches, where the primary owner has to forward a command to the backup owners. The remote-executor thread on the primary should not be blocked while waiting for the backup responses, and instead process other commands. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5468) Change the interceptors to move the new sequential interfaces

by Dan Berindei (JIRA)

Dan Berindei created ISPN-5468: ---------------------------------- Summary: Change the interceptors to move the new sequential interfaces Key: ISPN-5468 URL: https://issues.jboss.org/browse/ISPN-5468 Project: Infinispan Issue Type: Task Components: Core Affects Versions: 7.2.1.Final Reporter: Dan Berindei Fix For: 8.0.0.Final The first step is to move all interceptors to the new sequential interfaces, without actually allowing the command execution to be suspended and resumed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5467) Design new interceptor interfaces for sequential invocation

by Dan Berindei (JIRA)

Dan Berindei created ISPN-5467: ---------------------------------- Summary: Design new interceptor interfaces for sequential invocation Key: ISPN-5467 URL: https://issues.jboss.org/browse/ISPN-5467 Project: Infinispan Issue Type: Task Components: Core Affects Versions: 7.2.1.Final Reporter: Dan Berindei Fix For: 8.0.0.Final We need the interceptors to execute in sequence instead of using a stack in order to allow interrupting the execution of a command on one thread and continuing the execution on another thread. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5466) Unify the implementation and handling of write commands

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5466?page=com.atlassian.jira.plugin.... ] Dan Berindei resolved ISPN-5466. -------------------------------- Fix Version/s: (was: 8.0.0.Final) Resolution: Duplicate Issue Duplicate of ISPN-3664 > Unify the implementation and handling of write commands > ------------------------------------------------------- > > Key: ISPN-5466 > URL: https://issues.jboss.org/browse/ISPN-5466 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 7.2.1.Final > Reporter: Dan Berindei > > PutKeyValueCommand, RemoveCommand, ReplaceCommand are very similar, and they should be replaced with a single SingleWriteCommand. > We will probably still require separate commands for eviction and invalidation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5466) Unify the implementation and handling of write commands

by Dan Berindei (JIRA)

Dan Berindei created ISPN-5466: ---------------------------------- Summary: Unify the implementation and handling of write commands Key: ISPN-5466 URL: https://issues.jboss.org/browse/ISPN-5466 Project: Infinispan Issue Type: Task Components: Core Affects Versions: 7.2.1.Final Reporter: Dan Berindei Fix For: 8.0.0.Final PutKeyValueCommand, RemoveCommand, ReplaceCommand are very similar, and they should be replaced with a single SingleWriteCommand. We will probably still require separate commands for eviction and invalidation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 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 May 2015