October 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9533) ProtobufValueWrapper needs a more efficient key transformer when used as key in an indexed cache

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9533?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9533: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > ProtobufValueWrapper needs a more efficient key transformer when used as key in an indexed cache > ------------------------------------------------------------------------------------------------ > > Key: ISPN-9533 > URL: https://issues.jboss.org/browse/ISPN-9533 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Querying > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.1.Final > > > DefaultTransformer is very very wasteful. Right now (9.x) we do not put protobuf keys in cache wrapped in a ProtobufValueWrapper but we'll start doing that once we implement query on keys. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9513) Transformers registered via SearchManagerImplementor.registerKeyTransformer should be propagated in the cluster

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9513?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9513: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Transformers registered via SearchManagerImplementor.registerKeyTransformer should be propagated in the cluster > --------------------------------------------------------------------------------------------------------------- > > Key: ISPN-9513 > URL: https://issues.jboss.org/browse/ISPN-9513 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 5.2.0.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.1.Final > > > This can be achieved in a similar manner QueryKnownClasses is used to propagate indexed entities to other nodes. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9579) The server does too many ConcurrentHashMap lookups to get the cache

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9579?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9579: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > The server does too many ConcurrentHashMap lookups to get the cache > ------------------------------------------------------------------- > > Key: ISPN-9579 > URL: https://issues.jboss.org/browse/ISPN-9579 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 9.4.0.CR3 > Reporter: Dan Berindei > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 10.0.1.Final > > > Got a profiler snapshot while investigating ISPN-9198, and there are a lot of map lookups just to find the cache with the right flags and make sure it's not ignored. > ||Stack Trace||Sample Count||Percentage(%)|| > |org.infinispan.server.hotrod.CacheRequestProcessor.get(HotRodHeader, Subject, byte[])|6,554|41.615| > |+org.infinispan.server.hotrod.CacheRequestProcessor.handleGet(HotRodHeader, CacheEntry, Throwable)|2,659|16.884| > |+org.infinispan.cache.impl.AbstractDelegatingAdvancedCache.getCacheEntry(Object)|2,569|16.312| > |+org.infinispan.server.hotrod.HotRodServer.cache(HotRodHeader, Subject)|793|5.035| > |+org.infinispan.server.hotrod.HotRodServer.cache(HotRodHeader, Subject, String)|793|5.035| > |++java.util.concurrent.ConcurrentHashMap.get(Object)|349|2.216| > |++org.infinispan.server.hotrod.HotRodServer.getCacheConfiguration(String)|203|1.289| > |++org.infinispan.server.hotrod.HotRodHeader.getOptimizedCache(AdvancedCache, Configuration)|152|0.965| > |++org.infinispan.server.core.AbstractCacheIgnoreAware.isCacheIgnored(String)|88|0.559| > |+org.infinispan.server.hotrod.HotRodServer.getCacheInfo(AdvancedCache, HotRodHeader)|516|3.276| -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9506) ClusteredCacheQueryImpl ignores FetchOptions.fetchSize

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9506?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9506: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > ClusteredCacheQueryImpl ignores FetchOptions.fetchSize > ------------------------------------------------------ > > Key: ISPN-9506 > URL: https://issues.jboss.org/browse/ISPN-9506 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 5.1.0.FINAL > Reporter: Nistor Adrian > Priority: Major > Fix For: 10.0.1.Final > > > Have a look in org.infinispan.query.clustered.DistributedIterator. fetchSize is ignored. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9669) Soft index file store usability umbrella

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9669?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9669: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Soft index file store usability umbrella > ---------------------------------------- > > Key: ISPN-9669 > URL: https://issues.jboss.org/browse/ISPN-9669 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 9.3.4.Final > Reporter: Radim Vansa > Assignee: Radim Vansa > Priority: Major > Fix For: 10.0.1.Final > > > Get these subtasks done to get soft index file store mature and future-proof. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9721) Add non blocking Publisher for a Cache

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9721?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9721: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Add non blocking Publisher for a Cache > -------------------------------------- > > Key: ISPN-9721 > URL: https://issues.jboss.org/browse/ISPN-9721 > Project: Infinispan > Issue Type: Feature Request > Components: Core, Publisher > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.0.1.Final > > > We currently have distributed streams. Unfortunately this requires blocking to operate at various levels. We need to instead expose some sort of distributed publisher that allows for distributed operations but in a totally non blocking way. > I had started a branch that has some ideas for the public API https://github.com/wburns/infinispan/tree/ISPN-9565_publisher. I believe the use of the various compose methods should help reduce complexity as all of the operations can be in a utility class if needed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9582) Lifespan/MaxIdle = 0 from Hot Rod behaviour is inconsistent with embedded

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9582?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9582: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Lifespan/MaxIdle = 0 from Hot Rod behaviour is inconsistent with embedded > ------------------------------------------------------------------------- > > Key: ISPN-9582 > URL: https://issues.jboss.org/browse/ISPN-9582 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.4.0.CR3 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.1.Final > > > In embedded mode, specifying 0 for lifespan or maxIdle results in immediate expiration. > In Hot Rod, however, 0 results in the entry using the default server-side expiration. This was done in order to not introduce a protocol change at the time. > The 2.2 protocol introduced timeunit support with special values for default and infinity. > We should therefore not override a user-specified value of 0 with "default". -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9443) Fail when single region is accessed with multiple strategies

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9443?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9443: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Fail when single region is accessed with multiple strategies > ------------------------------------------------------------ > > Key: ISPN-9443 > URL: https://issues.jboss.org/browse/ISPN-9443 > Project: Infinispan > Issue Type: Enhancement > Components: Hibernate Cache > Affects Versions: 9.3.1.Final > Reporter: Radim Vansa > Priority: Major > Fix For: 10.0.1.Final > > > When we have two entities that share the same region but use different access strategies the Hibernate boot should fail. Right now there's an assertion in {{DomainDataRegionImpl.prepareFor*}} but this does not give much explanation and does not fail when assertions are disabled which leads to cryptic errors later on. > Example: > {code} > @Cache(usage = CacheConcurrencyStrategy.NONSTRICT_READ_WRITE, region = "item") > public static class NonStrictReadWriteVersionedCacheableItem { ... } > @Cache(usage = CacheConcurrencyStrategy.READ_WRITE, region = "item") > public static class ReadWriteVersionedCacheableItem { ... } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9620) Rolling Upgrade Marshaller Changes

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9620?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9620: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Rolling Upgrade Marshaller Changes > ---------------------------------- > > Key: ISPN-9620 > URL: https://issues.jboss.org/browse/ISPN-9620 > Project: Infinispan > Issue Type: Enhancement > Components: Core, Loaders and Stores > Affects Versions: 9.4.0.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.1.Final > > > In order to allow for compatibility between infinispan versions it is necessary for us to utilise a marshalling implementation at both the cluster (internal node-to-node communication) and persistence layer that is strictly defined but allows for future changes. This is necessary in order to facilitate both rolling and start/stop upgrades. Protocol buffers should be utilised as the wire/storage format, with protostream providing the implementation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9634) Deprecate useRawData from remote listeners

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9634?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9634: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Deprecate useRawData from remote listeners > ------------------------------------------ > > Key: ISPN-9634 > URL: https://issues.jboss.org/browse/ISPN-9634 > Project: Infinispan > Issue Type: Enhancement > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 10.0.1.Final > > > Since remote listeners with converters and filters were introduced, it was assumed the user supplied implementations would receive "unmarshalled" data to operate. > A parameter on the remote listener annotation itself called "useRawData" was later introduced to provide a way for filters/converters to use data as it was stored (i.e., without unmarshalling) > Since transcoders were introduced, the choice of format for listeners and converters can be specified on the listeners/converters themselves in the format() method and should not rely on useRawData anymore. -- This message was sent by Atlassian Jira (v7.13.8#713008)

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