September 2020 - infinispan-issues

[JBoss JIRA] (ISPN-12325) Hot Rod server instances in tests use too much memory

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12325?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12325: ----------------------------------- Fix Version/s: 12.0.0.Dev05 (was: 12.0.0.Dev04) > Hot Rod server instances in tests use too much memory > ----------------------------------------------------- > > Key: ISPN-12325 > URL: https://issues.redhat.com/browse/ISPN-12325 > Project: Infinispan > Issue Type: Bug > Components: Server, Test Suite > Affects Versions: 12.0.0.Dev03 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 12.0.0.Dev05 > > > When a test class finishes, TestNG does not discard the test instance, instead it keeps it in memory until the test suite finishes. This means test class fields that uses a lot of memory will accumulate in memory, making the test suite use a lot more heap than it should. > ISPN-8478 added a generic way to set {{Cache}} and {{EmbeddedCacheManager}} fields to {{null}} in order to reduce memory usage, but hotrod-client tests do not have anything similar for {{HotRodServer}} and {{RemoteCacheManager}} fields. > That might need to change: hotrod-client tests often keep references to {{HotRodServer}} instances in fields, and the servers use > 3MB, most of it in the {{SerializationContextRegistryImpl}}: > {noformat} > Class Name | Shallow Heap | Retained Heap | Percentage > ------------------------------------------------------------------------------------------------------------------------------------------------------------- > org.infinispan.client.hotrod.ReplTopologyChangeTest @ 0xc52bf018 | 96 | 10,358,136 | 1.02% > |- org.infinispan.server.hotrod.test.HotRodTestingUtil$1 @ 0xe30cc538 | 128 | 3,420,600 | 0.34% > | |- org.infinispan.marshall.protostream.impl.SerializationContextRegistryImpl @ 0xcd18d210 | 24 | 2,493,584 | 0.25% > | | |- org.infinispan.marshall.protostream.impl.SerializationContextRegistryImpl$MarshallerContext @ 0xe3d18c08| 32 | 2,358,320 | 0.23% > | | | |- org.infinispan.protostream.impl.SerializationContextImpl @ 0xe3d18e78 | 64 | 2,357,696 | 0.23% > | | | | |- org.infinispan.protostream.descriptors.FileDescriptor @ 0xe3d67fe0 | 72 | 967,680 | 0.10% > | | | | | |- org.infinispan.protostream.descriptors.FileDescriptor @ 0xe41b8798 | 72 | 690,528 | 0.07% > | | | | | | |- org.infinispan.protostream.descriptors.FileDescriptor @ 0xc997eaf8 | 72 | 413,376 | 0.04% > | | | | | | | |- org.infinispan.protostream.descriptors.FileDescriptor @ 0xc5ed3cd8 | 72 | 214,640 | 0.02% > | | | | | | | | |- org.infinispan.protostream.descriptors.FileDescriptor @ 0xc5ed4b60 | 72 | 183,648 | 0.02% > | | | | | | | | | |- org.infinispan.protostream.descriptors.Descriptor @ 0xc5edabe8 | 72 | 132,104 | 0.01% > ------------------------------------------------------------------------------------------------------------------------------------------------------------- > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12286) Indexed entity declaration not enforced

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12286?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12286: ----------------------------------- Fix Version/s: 12.0.0.Dev05 (was: 12.0.0.Dev04) > Indexed entity declaration not enforced > --------------------------------------- > > Key: ISPN-12286 > URL: https://issues.redhat.com/browse/ISPN-12286 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Affects Versions: 12.0.0.Dev02 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 12.0.0.Dev05 > > > ISPN-11985 was enforcing the declaration of indexed entities in the cache, but the migration to Hibernate Search 6 undid the efforts and the cache starts normally without the entities, causing plenty of errors when doing search operations. > Also, remote query is not checking if the configured entity is indexed or not -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12357) Indexing configurations should not be inherited when explicitly disabled

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12357?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12357: ----------------------------------- Fix Version/s: 12.0.0.Dev05 (was: 12.0.0.Dev04) > Indexing configurations should not be inherited when explicitly disabled > ------------------------------------------------------------------------ > > Key: ISPN-12357 > URL: https://issues.redhat.com/browse/ISPN-12357 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 11.0.0.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 12.0.0.Dev05 > > > When the base config has indexing enabled and the child config disables it we just need to whipe out all inherited indexing properties, transformers, indexed entities because they conflict with the enabled=false flag. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12351) ImmutableListCopy makes too many copies

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12351?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12351: ----------------------------------- Fix Version/s: 12.0.0.Dev05 (was: 12.0.0.Dev04) > ImmutableListCopy makes too many copies > --------------------------------------- > > Key: ISPN-12351 > URL: https://issues.redhat.com/browse/ISPN-12351 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 12.0.0.Dev03 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 12.0.0.Dev05 > > > An array copy is not needed when creating a new {{ImmutableListCopy}} instance from another {{ImmutableListCopy}}. > The constructor with 2 list parameters can also avoid one array allocation by pre-allocating the array, or by using one list's array when the other list is empty. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12250) Add exponential back-off for cross-site network failures

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12250?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12250: ----------------------------------- Fix Version/s: 12.0.0.Dev05 (was: 12.0.0.Dev04) > Add exponential back-off for cross-site network failures > -------------------------------------------------------- > > Key: ISPN-12250 > URL: https://issues.redhat.com/browse/ISPN-12250 > Project: Infinispan > Issue Type: Bug > Components: Cross-Site Replication > Affects Versions: 12.0.0.Dev02 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 11.0.4.Final, 12.0.0.Dev05 > > > If the remote site doesn't exist (crash or shutdown), the IRAC algorithm keeps trying to send the updates to the remote site (until automatic take offline is triggered, when configured). > Add an exponential backoff to avoid CPU consumption. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12278) Restore support for @Field(norms = ...) and @Field(termVector = ...)

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12278?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12278: ----------------------------------- Fix Version/s: 12.0.0.Dev05 (was: 12.0.0.Dev04) > Restore support for @Field(norms = ...) and @Field(termVector = ...) > -------------------------------------------------------------------- > > Key: ISPN-12278 > URL: https://issues.redhat.com/browse/ISPN-12278 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying > Affects Versions: 12.0.0.Dev02 > Reporter: Yoann Rodière > Priority: Major > Fix For: 12.0.0.Dev05 > > > It looks like these attributes of the {{@Field}} annotations were removed by mistake during the migration to Search 6. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12218) Indexed caches with non-indexed entities query inconsistency

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12218?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12218: ----------------------------------- Fix Version/s: 12.0.0.Dev05 (was: 12.0.0.Dev04) > Indexed caches with non-indexed entities query inconsistency > ------------------------------------------------------------ > > Key: ISPN-12218 > URL: https://issues.redhat.com/browse/ISPN-12218 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Affects Versions: 11.0.3.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 12.0.0.Dev05 > > Attachments: IndexedCacheNonIndexedQueryTest.java > > > When a cache is indexed, but the protobuf entitiy is not: > "FROM Entity" returns zero results > "FROM Entity WHERE <predicate>" return results > It appears in the first case the query goes to the index (that will be empty), but not in the second where it does a non-indexed query > On a side note, if I configure a cache as indexed, but do not index any type in the protobuf, it returns {{ISPN014054: Trying to execute query from xyz, but no type is indexed on cache}}. This should be improved to mention the schema needs to be changed -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12279) Default value of @IndexedEmbedded.depth is not correctly interpreted

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12279?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12279: ----------------------------------- Fix Version/s: 12.0.0.Dev05 (was: 12.0.0.Dev04) > Default value of @IndexedEmbedded.depth is not correctly interpreted > -------------------------------------------------------------------- > > Key: ISPN-12279 > URL: https://issues.redhat.com/browse/ISPN-12279 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying > Affects Versions: 12.0.0.Dev02 > Reporter: Yoann Rodière > Priority: Major > Fix For: 12.0.0.Dev05 > > > There was a problem during the migration to Search 6, and the processor for the annotation {{@IndexedEmbedded}} apparently does not correctly intepret {{@IndexedEmbedded()}} as "no depth defined". > As a result, {{@IndexedEmbedded(includePaths = { "foo" })}} will not set the depth to 0 as it should, but to {{Integer.MAX_VALUE}} (the default defined on the {{(a)IndexedEmbedded.depth()}} attribute) and will end up incorrectly including the whole embedded document. > The code to change is this (in {{org.hibernate.search.annotations.IndexedEmbedded}}): > {code} > Integer cleanedUpMaxDepth = annotation.depth(); > if ( cleanedUpMaxDepth.equals( -1 ) ) { > cleanedUpMaxDepth = null; > } > {code} > It should be instead: > {code} > Integer cleanedUpMaxDepth = annotation.depth(); > if ( cleanedUpMaxDepth.equals( Integer.MAX_VALUE ) ) { > cleanedUpMaxDepth = null; > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12275) Restore support for @Field(analyzer = ...) and @Field(normalizer = ...)

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12275?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12275: ----------------------------------- Fix Version/s: 12.0.0.Dev05 (was: 12.0.0.Dev04) > Restore support for @Field(analyzer = ...) and @Field(normalizer = ...) > ----------------------------------------------------------------------- > > Key: ISPN-12275 > URL: https://issues.redhat.com/browse/ISPN-12275 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying > Reporter: Yoann Rodière > Priority: Major > Fix For: 12.0.0.Dev05 > > > In Infinispan 11 (Hibernate Search 5.10/5.11), it used to be possible to assign an analyzer or normalizer to a field with the following syntax: > {code} > @Field(analyzer = @Analyzer(definition = "myAnalyzer")) > private String myProperty; > @Field(analyzer = @Normalizer(definition = "myNormalizer")) > private String myProperty; > {code} > It seems that we made a mistake during the upgrade to Search 6, and support for this syntax was removed. All that's left is the property-scoped syntax, where the analyzer is defined next to the field: > {code} > @Field > @Analyzer(definition = "myAnalyzer") > private String myProperty; > {code} > If we want to provide at least partial backward compatibility in annotations, we should restore support for the former syntax (and keep the latter). > For the record, analyzer assigned using the former syntax take precedence over analyzers assigned using the latter. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12261) Protocol server transport management

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12261?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12261: ----------------------------------- Fix Version/s: 12.0.0.Dev05 (was: 12.0.0.Dev04) > Protocol server transport management > ------------------------------------- > > Key: ISPN-12261 > URL: https://issues.redhat.com/browse/ISPN-12261 > Project: Infinispan > Issue Type: Feature Request > Components: CLI, JMX, reporting and management, Server > Affects Versions: 12.0.0.Dev02 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 12.0.0.Dev05 > > > the WF-server had the ability to stop/start a transport via the CLI (ISPN-11240). > The new server should have a similar capability. > Aside from start/stop, we should also leverage netty's ipfilter handler which allows filtering based on subnet so that traffic can be blocked selectively. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2020