[JBoss JIRA] (ISPN-10931) ClassWhiteList should store regex matches in classes Set
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-10931?page=com.atlassian.jira.plugin... ]
Ryan Emerson updated ISPN-10931:
--------------------------------
Summary: ClassWhiteList should store regex matches in classes Set (was: ClassWhiteList should store regex matches in class map)
> ClassWhiteList should store regex matches in classes Set
> --------------------------------------------------------
>
> Key: ISPN-10931
> URL: https://issues.jboss.org/browse/ISPN-10931
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core
> Affects Versions: 10.0.1.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.1.0.Final
>
>
> Even though we pre-compile the Regex Pattern instances, performing a regex check per class can be slow. Therefore, if a class matches a regex, we should add it to the class `Set` to avoid future regex checks.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (ISPN-10931) ClassWhiteList should store regex matches in class map
by Ryan Emerson (Jira)
Ryan Emerson created ISPN-10931:
-----------------------------------
Summary: ClassWhiteList should store regex matches in class map
Key: ISPN-10931
URL: https://issues.jboss.org/browse/ISPN-10931
Project: Infinispan
Issue Type: Enhancement
Components: Core
Affects Versions: 10.0.1.Final
Reporter: Ryan Emerson
Assignee: Ryan Emerson
Fix For: 10.1.0.Final
Even though we pre-compile the Regex Pattern instances, performing a regex check per class can be slow. Therefore, if a class matches a regex, we should add it to the class `Set` to avoid future regex checks.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (ISPN-10855) MultipleCacheManagersTest factory issues are ignored
by Dan Berindei (Jira)
[ https://issues.jboss.org/browse/ISPN-10855?page=com.atlassian.jira.plugin... ]
Dan Berindei updated ISPN-10855:
--------------------------------
Status: Pull Request Sent (was: Reopened)
Git Pull Request: https://github.com/infinispan/infinispan/pull/7498, https://github.com/infinispan/infinispan/pull/7571 (was: https://github.com/infinispan/infinispan/pull/7498)
> MultipleCacheManagersTest factory issues are ignored
> ----------------------------------------------------
>
> Key: ISPN-10855
> URL: https://issues.jboss.org/browse/ISPN-10855
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Affects Versions: 9.4.16.Final, 10.0.0.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 10.1.0.Beta1
>
>
> TestNG doesn't like exceptions being thrown from {{@Factory}} methods, so when {{MultipleCacheManager.defaultFactory()}} finds a problem with the concrete {{factory()}} implementation or with the annotations it replaces the test instance with a {{TestFrameworkFailure}}.
> Turns out that doesn't actually work: TestNG ignores the {{TestFrameworkFailure}} instance and runs the tests on a "default instance" of the test class. This is ok when the problem is the concrete class didn't override {{factory()}} and very likely the test author wanted a single test instance, but it's not ok for other errors like {{factory()}} being copy-pasted from super with the wrong class name.
> We can make TestNG report our factory failures if we implement {{IInstanceInfo}} and mock all the test/configuration methods to throw our exception. We just need to make all configuration methods non-final so we can mock them.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (ISPN-10930) MassIndexer does not reindex cache with OFF_HEAP and protobuf storage
by Gustavo Fernandes (Jira)
Gustavo Fernandes created ISPN-10930:
----------------------------------------
Summary: MassIndexer does not reindex cache with OFF_HEAP and protobuf storage
Key: ISPN-10930
URL: https://issues.jboss.org/browse/ISPN-10930
Project: Infinispan
Issue Type: Bug
Components: Remote Querying
Affects Versions: 10.0.1.Final, 9.4.16.Final
Reporter: Gustavo Fernandes
Assignee: Gustavo Fernandes
The MassIndexer iterates though the data and creates indexing jobs, and in order to a protobuf payload to be reinidex, it needs to be a ProtobufValueWrapper. When using OFF_HEAP, the data container stores values as WrappedBytes and they are ingored when indexing
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (ISPN-10929) ClusterPublisher reduction combineStages concurrency level is too high
by Will Burns (Jira)
Will Burns created ISPN-10929:
---------------------------------
Summary: ClusterPublisher reduction combineStages concurrency level is too high
Key: ISPN-10929
URL: https://issues.jboss.org/browse/ISPN-10929
Project: Infinispan
Issue Type: Bug
Components: Core
Reporter: Will Burns
Assignee: Will Burns
The combineStages method in ClusterPublisherImpl currently uses flatMap without an explicit concurrency level. That means it will subscribe to up to 128 futures at the same time. This isn't a problem when only in memory is used as the stages are completed as they are received. However when a segmented store is in play, this means it will process 128 segments at the same time, even when doing sequential publisher.
We should instead limit the concurrency to the cpuCount when the publisher is parallel and just 1 when it is sequential. The latter matches how many threads the upstream publisher will use as well.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years