November 2018 - infinispan-issues

[JBoss JIRA] (ISPN-8861) DIST Iteration shouldn't go remote when a shared cache store is present

by William Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-8861?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-8861: ------------------------------------- Granted I don't think any shared stores have key optimized stores that wouldn't just want to pull the value as well. > DIST Iteration shouldn't go remote when a shared cache store is present > ----------------------------------------------------------------------- > > Key: ISPN-8861 > URL: https://issues.jboss.org/browse/ISPN-8861 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: William Burns > Assignee: William Burns > Priority: Major > Fix For: 9.4.4.Final > > > When a user runs a distributed iteration operation with a shared cache store, this shouldn't go remote as the local node would have all the data available to it. This is similar to the optimization when we don't go remote if the current node is an owner for all required segments. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8861) DIST Iteration shouldn't go remote when a shared cache store is present

by William Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-8861?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-8861: ------------------------------------- Another problem with this is stores that are optimized for key only traversal such as SingleFileStore may be quite a bit slower, since they will have to resurrect all values from the store. I am liking something like Dan mentioned at https://issues.jboss.org/browse/ISPN-8862?focusedCommentId=13567688&page=... which would allow for that to query the DataContainer for key based optimized stores. > DIST Iteration shouldn't go remote when a shared cache store is present > ----------------------------------------------------------------------- > > Key: ISPN-8861 > URL: https://issues.jboss.org/browse/ISPN-8861 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: William Burns > Assignee: William Burns > Priority: Major > Fix For: 9.4.4.Final > > > When a user runs a distributed iteration operation with a shared cache store, this shouldn't go remote as the local node would have all the data available to it. This is similar to the optimization when we don't go remote if the current node is an owner for all required segments. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8862) Iteration and stream operations with passivation disabled shouldn't use in memory

by William Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-8862?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-8862: ------------------------------------- The other issue with the former idea is if we had a passivation during the iteration process we could miss an entry :( Thus we would have to listen to passivations and if did happen compare if we already returned that key, which is exactly what we do currently :( > Iteration and stream operations with passivation disabled shouldn't use in memory > --------------------------------------------------------------------------------- > > Key: ISPN-8862 > URL: https://issues.jboss.org/browse/ISPN-8862 > Project: Infinispan > Issue Type: Enhancement > Reporter: William Burns > Assignee: William Burns > Priority: Major > Fix For: 9.4.4.Final > > > When passivation is disabled all entries are assumed to be in the cache loader/store. We currently try to merge these together in a sloppy way [1]. This first reads in memory and then from the store and keeps all keys from in memory to exclude them from the store. Unfortunately the store still has to pull the entries even for the already read keys, but just ignores them. This leads to a lot of inefficiency and memory bloat. Instead we should just return the store entries as is when passivation is disabled. > [1] https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8862) Iteration and stream operations with passivation disabled shouldn't use in memory

by William Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-8862?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-8862: ------------------------------------- You are saying keep track if an entry was evicted in the data container when passivation is enabled and if not then only do iteration over the data container, correct? Yeah iterating over the store keys vs keys and value is interesting, but we have no way to do that currently and putting that logic into the store will complicate them all substantially. To be honest I don't know if there is a good answer > Iteration and stream operations with passivation disabled shouldn't use in memory > --------------------------------------------------------------------------------- > > Key: ISPN-8862 > URL: https://issues.jboss.org/browse/ISPN-8862 > Project: Infinispan > Issue Type: Enhancement > Reporter: William Burns > Assignee: William Burns > Priority: Major > Fix For: 9.4.4.Final > > > When passivation is disabled all entries are assumed to be in the cache loader/store. We currently try to merge these together in a sloppy way [1]. This first reads in memory and then from the store and keeps all keys from in memory to exclude them from the store. Unfortunately the store still has to pull the entries even for the already read keys, but just ignores them. This leads to a lot of inefficiency and memory bloat. Instead we should just return the store entries as is when passivation is disabled. > [1] https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9683) Remote getBulk methods from RemoteCache

by William Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-9683?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-9683: -------------------------------- Status: Open (was: New) > Remote getBulk methods from RemoteCache > --------------------------------------- > > Key: ISPN-9683 > URL: https://issues.jboss.org/browse/ISPN-9683 > Project: Infinispan > Issue Type: Sub-task > Components: Hot Rod > Reporter: William Burns > Assignee: William Burns > Priority: Major > Fix For: 10.0.0.Final > > > The getBulk methods have been deprecated for a while on the RemoteCache. We have appropriate streaming based methods for keySet, entrySet and retrieveEntries methods which are much better. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9683) Remote getBulk methods from RemoteCache

by William Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-9683?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-9683: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6483 > Remote getBulk methods from RemoteCache > --------------------------------------- > > Key: ISPN-9683 > URL: https://issues.jboss.org/browse/ISPN-9683 > Project: Infinispan > Issue Type: Sub-task > Components: Hot Rod > Reporter: William Burns > Assignee: William Burns > Priority: Major > Fix For: 10.0.0.Final > > > The getBulk methods have been deprecated for a while on the RemoteCache. We have appropriate streaming based methods for keySet, entrySet and retrieveEntries methods which are much better. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9605) Remove extraneous code related to eager near cache

by William Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-9605?page=com.atlassian.jira.plugin.... ] William Burns resolved ISPN-9605. --------------------------------- Resolution: Duplicate Issue > Remove extraneous code related to eager near cache > -------------------------------------------------- > > Key: ISPN-9605 > URL: https://issues.jboss.org/browse/ISPN-9605 > Project: Infinispan > Issue Type: Sub-task > Components: Listeners > Reporter: William Burns > Priority: Major > Fix For: 10.0.0.Final > > > Eager near caching ended up sending too much data across the socket and thus we removed it in favor of only invalidated near caching. We should remove the old code lying around, such as in NearCacheService. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9605) Remove extraneous code related to eager near cache

by William Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-9605?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-9605: ------------------------------------- Hrmm I would say leaving "___eager-key-value-version-converter" as it is is probably fine. This eagerly converts the key and value before passing along, so I am fine with that name. I am more worried about the eager near cache, which I may have removed it all already in https://github.com/infinispan/infinispan/commit/c5063e7bc7ce9f6aaf118e8ca... > Remove extraneous code related to eager near cache > -------------------------------------------------- > > Key: ISPN-9605 > URL: https://issues.jboss.org/browse/ISPN-9605 > Project: Infinispan > Issue Type: Sub-task > Components: Listeners > Reporter: William Burns > Priority: Major > Fix For: 10.0.0.Final > > > Eager near caching ended up sending too much data across the socket and thus we removed it in favor of only invalidated near caching. We should remove the old code lying around, such as in NearCacheService. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9683) Remote getBulk methods from RemoteCache

by William Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-9683?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-9683: ------------------------------------- Unfortunately server side code cannot be removed until we remove the 2.x protocol support, which will be a while. So this will include just the client side changes. > Remote getBulk methods from RemoteCache > --------------------------------------- > > Key: ISPN-9683 > URL: https://issues.jboss.org/browse/ISPN-9683 > Project: Infinispan > Issue Type: Sub-task > Components: Hot Rod > Reporter: William Burns > Assignee: William Burns > Priority: Major > Fix For: 10.0.0.Final > > > The getBulk methods have been deprecated for a while on the RemoteCache. We have appropriate streaming based methods for keySet, entrySet and retrieveEntries methods which are much better. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9683) Remote getBulk methods from RemoteCache

by William Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-9683?page=com.atlassian.jira.plugin.... ] William Burns reassigned ISPN-9683: ----------------------------------- Assignee: William Burns > Remote getBulk methods from RemoteCache > --------------------------------------- > > Key: ISPN-9683 > URL: https://issues.jboss.org/browse/ISPN-9683 > Project: Infinispan > Issue Type: Sub-task > Components: Hot Rod > Reporter: William Burns > Assignee: William Burns > Priority: Major > Fix For: 10.0.0.Final > > > The getBulk methods have been deprecated for a while on the RemoteCache. We have appropriate streaming based methods for keySet, entrySet and retrieveEntries methods which are much better. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2018