November 2019 - infinispan-issues

[JBoss JIRA] (ISPN-10929) ClusterPublisher reduction combineStages concurrency level is too high

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10929?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10929: ------------------------------ Status: Open (was: New) > 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 > Priority: Major > > 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)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10934) RESTv2 HEAD on cache name

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-10934?page=com.atlassian.jira.plugin... ] Gustavo Fernandes updated ISPN-10934: ------------------------------------- Status: Open (was: New) > RESTv2 HEAD on cache name > ------------------------- > > Key: ISPN-10934 > URL: https://issues.jboss.org/browse/ISPN-10934 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 10.0.1.Final > Reporter: Galder Zamarreño > Assignee: Gustavo Fernandes > Priority: Major > > Checking whether a cache is already defined can be done several ways: One way is to get the list of caches and see if the cache is there. Although it works, it requires the client to parse the list...etc. Another way is to call: > {code} > HEAD rest/v2/caches/{cache_name}?action=config > {code} > This works, but it shouldn't be necessary to add {{?action=config}} to find out if the cache is defined or not. The following should be possible: > {code} > HEAD rest/v2/caches/{cache_name} > {code} > Currently that returns {{400}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10934) RESTv2 HEAD on cache name

by Galder Zamarreño (Jira)

Galder Zamarreño created ISPN-10934: --------------------------------------- Summary: RESTv2 HEAD on cache name Key: ISPN-10934 URL: https://issues.jboss.org/browse/ISPN-10934 Project: Infinispan Issue Type: Bug Components: JMX, reporting and management Affects Versions: 10.0.1.Final Reporter: Galder Zamarreño Assignee: Gustavo Fernandes Checking whether a cache is already defined can be done several ways: One way is to get the list of caches and see if the cache is there. Although it works, it requires the client to parse the list...etc. Another way is to call: {code} HEAD rest/v2/caches/{cache_name}?action=config {code} This works, but it shouldn't be necessary to add {{?action=config}} to find out if the cache is defined or not. The following should be possible: {code} HEAD rest/v2/caches/{cache_name} {code} Currently that returns {{400}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10855) MultipleCacheManagersTest factory issues are ignored

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10855?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10855: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10933) Support for wiping the indexes

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-10933?page=com.atlassian.jira.plugin... ] Gustavo Fernandes updated ISPN-10933: ------------------------------------- Fix Version/s: 10.1.0.Beta1 > Support for wiping the indexes > ------------------------------ > > Key: ISPN-10933 > URL: https://issues.jboss.org/browse/ISPN-10933 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Affects Versions: 10.0.1.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 10.1.0.Beta1 > > > Currently there is no way to simply delete the indexes, the closes option is to run the MassIndexer that does clear them but do a full re-index afterwards -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10933) Support for wiping the indexes

by Gustavo Fernandes (Jira)

Gustavo Fernandes created ISPN-10933: ---------------------------------------- Summary: Support for wiping the indexes Key: ISPN-10933 URL: https://issues.jboss.org/browse/ISPN-10933 Project: Infinispan Issue Type: Bug Components: Embedded Querying, Remote Querying Reporter: Gustavo Fernandes Assignee: Gustavo Fernandes Currently there is no way to simply delete the indexes, the closes option is to run the MassIndexer that does clear them but do a full re-index afterwards -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10933) Support for wiping the indexes

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-10933?page=com.atlassian.jira.plugin... ] Gustavo Fernandes updated ISPN-10933: ------------------------------------- Affects Version/s: 10.0.1.Final > Support for wiping the indexes > ------------------------------ > > Key: ISPN-10933 > URL: https://issues.jboss.org/browse/ISPN-10933 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Affects Versions: 10.0.1.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 10.1.0.Beta1 > > > Currently there is no way to simply delete the indexes, the closes option is to run the MassIndexer that does clear them but do a full re-index afterwards -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10932) Prevent starting multiple MassIndexers in a node

by Gustavo Fernandes (Jira)

Gustavo Fernandes created ISPN-10932: ---------------------------------------- Summary: Prevent starting multiple MassIndexers in a node Key: ISPN-10932 URL: https://issues.jboss.org/browse/ISPN-10932 Project: Infinispan Issue Type: Bug Components: Embedded Querying, Remote Querying Reporter: Gustavo Fernandes Assignee: Gustavo Fernandes Currently the MassIndexer can be started multiple times on a single node causing them to overlap. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10932) Prevent starting multiple MassIndexers in a node

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-10932?page=com.atlassian.jira.plugin... ] Gustavo Fernandes updated ISPN-10932: ------------------------------------- Fix Version/s: 10.1.0.Beta1 > Prevent starting multiple MassIndexers in a node > ------------------------------------------------ > > Key: ISPN-10932 > URL: https://issues.jboss.org/browse/ISPN-10932 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Affects Versions: 10.0.1.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 10.1.0.Beta1 > > > Currently the MassIndexer can be started multiple times on a single node causing them to overlap. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10932) Prevent starting multiple MassIndexers in a node

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-10932?page=com.atlassian.jira.plugin... ] Gustavo Fernandes updated ISPN-10932: ------------------------------------- Affects Version/s: 10.0.1.Final > Prevent starting multiple MassIndexers in a node > ------------------------------------------------ > > Key: ISPN-10932 > URL: https://issues.jboss.org/browse/ISPN-10932 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Affects Versions: 10.0.1.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 10.1.0.Beta1 > > > Currently the MassIndexer can be started multiple times on a single node causing them to overlap. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2019