August 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11345) Introduce integration tests for serverNG

by Diego Lovison (Jira)

[ https://issues.redhat.com/browse/ISPN-11345?page=com.atlassian.jira.plugi... ] Work on ISPN-11345 stopped by Diego Lovison. -------------------------------------------- > Introduce integration tests for serverNG > ---------------------------------------- > > Key: ISPN-11345 > URL: https://issues.redhat.com/browse/ISPN-11345 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 11.0.0.Alpha1 > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Critical > > Introduce integration tests for serverNG > -Support Arquillian > -Arquillian is now optional > -Support multiple Infinispan Servers > *Support Arquillian* > Allow the current Infinispan source code to be deployed in the target container > *Arquillian is now optional* > As a developer, I would like to run the code without worrying about containers > *Support multiple Infinispan Servers* > As a QE, I would like to create a test scenario using multiple Infinispan Servers -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12264) Template or custom configuration should be required to create a cache

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-12264?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-12264: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-console/pull/75 > Template or custom configuration should be required to create a cache > --------------------------------------------------------------------- > > Key: ISPN-12264 > URL: https://issues.redhat.com/browse/ISPN-12264 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 12.0.0.Dev02 > Reporter: Dan Berindei > Assignee: Katia Aresti > Priority: Minor > > If I click only write a cache name and click the {{Create}} button, a {{LOCAL}} cache is created, which is not at all useful on the server. I should be required to either select a template or supply a custom configuration in order to create the cache. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12264) Template or custom configuration should be required to create a cache

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-12264?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-12264: -------------------------------- Status: Open (was: New) > Template or custom configuration should be required to create a cache > --------------------------------------------------------------------- > > Key: ISPN-12264 > URL: https://issues.redhat.com/browse/ISPN-12264 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 12.0.0.Dev02 > Reporter: Dan Berindei > Assignee: Katia Aresti > Priority: Minor > > If I click only write a cache name and click the {{Create}} button, a {{LOCAL}} cache is created, which is not at all useful on the server. I should be required to either select a template or supply a custom configuration in order to create the cache. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11661) Filter above and below threshold for more than 5 nodes

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11661?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-11661: ------------------------------------------ Priority: Minor (was: Major) > Filter above and below threshold for more than 5 nodes > ------------------------------------------------------ > > Key: ISPN-11661 > URL: https://issues.redhat.com/browse/ISPN-11661 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Affects Versions: 10.1.6.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Minor > Labels: console-ng > > Add a filter in the list to display the nodes that have a not even distribution > https://marvelapp.com/e0f1e1a/screen/67971793 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10441) Display endpoints in the console

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-10441?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-10441: ------------------------------------------ Priority: Minor (was: Major) > Display endpoints in the console > -------------------------------- > > Key: ISPN-10441 > URL: https://issues.redhat.com/browse/ISPN-10441 > Project: Infinispan > Issue Type: Feature Request > Components: Console > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Minor > Labels: console-ng > > Display de endpoints in console > Mockup > https://rawgit.com/infinispan/infinispan-console-mockup/master/cache-cont... > Actual console: cluster/ enpoints/hotrd-connector -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12267) CacheIgnoreManager should use global config cache

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12267?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12267: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8656 > CacheIgnoreManager should use global config cache > ------------------------------------------------- > > Key: ISPN-12267 > URL: https://issues.redhat.com/browse/ISPN-12267 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Server > Affects Versions: 12.0.0.Dev02 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 12.0.0.Dev03 > > > The CacheIgnoreManager creates a server config cache, but it should instead use the global config cache which already supports scoping. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12267) CacheIgnoreManager should use global config cache

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12267?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12267: ----------------------------------- Status: Open (was: New) > CacheIgnoreManager should use global config cache > ------------------------------------------------- > > Key: ISPN-12267 > URL: https://issues.redhat.com/browse/ISPN-12267 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Server > Affects Versions: 12.0.0.Dev02 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 12.0.0.Dev03 > > > The CacheIgnoreManager creates a server config cache, but it should instead use the global config cache which already supports scoping. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12267) CacheIgnoreManager should use global config cache

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-12267: -------------------------------------- Summary: CacheIgnoreManager should use global config cache Key: ISPN-12267 URL: https://issues.redhat.com/browse/ISPN-12267 Project: Infinispan Issue Type: Enhancement Components: Configuration, Server Affects Versions: 12.0.0.Dev02 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 12.0.0.Dev03 The CacheIgnoreManager creates a server config cache, but it should instead use the global config cache which already supports scoping. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12266) shutdown cluster should have an option to not block restart if there is no or a shared persistence

by Wolf-Dieter Fink (Jira)

[ https://issues.redhat.com/browse/ISPN-12266?page=com.atlassian.jira.plugi... ] Wolf-Dieter Fink updated ISPN-12266: ------------------------------------ Description: The current implementation of a full cluster restart will save the CH and state for all caches. If caches does not have a persistence or the persistence is a shared one this might not be necesarry as the cache can start correctly with one node (empty or consistent persistence). In that case it should be allowed to start the cache and make it available. There are two approaches - use extra parameter for shutdown to allow it This will leave the default behavior the same and the admin need to decide - change the current behavior and add a parameter to flag a FULL cluster restart The benefit of the full cluster restart is that the caches will be available for clients only if the cluster is completely restarted, so no further state-transfer is needed for optimal performance was: The current implementation of a full cluster restart will save the CH and state for all caches. If caches does not have a persistence or the persistence is a shared one this might not be necesarry as the cache can start correctly with one node (empty or consistent persistence). In that case it should be allowed to start the cache and make it available. There are two approaches - use extra parameter for shutdown to allow it > shutdown cluster should have an option to not block restart if there is no or a shared persistence > -------------------------------------------------------------------------------------------------- > > Key: ISPN-12266 > URL: https://issues.redhat.com/browse/ISPN-12266 > Project: Infinispan > Issue Type: Feature Request > Reporter: Wolf-Dieter Fink > Priority: Minor > Labels: graceful, graceful-start-stop > > The current implementation of a full cluster restart will save the CH and state for all caches. > If caches does not have a persistence or the persistence is a shared one this might not be necesarry as the cache can start correctly with one node (empty or consistent persistence). > In that case it should be allowed to start the cache and make it available. > There are two approaches > - use extra parameter for shutdown to allow it > This will leave the default behavior the same and the admin need to decide > - change the current behavior and add a parameter to flag a FULL cluster restart > The benefit of the full cluster restart is that the caches will be available for clients only if the cluster is completely restarted, so no further state-transfer is needed for optimal performance > > > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12266) shutdown cluster should have an option to not block restart if there is no or a shared persistence

by Wolf-Dieter Fink (Jira)

Wolf-Dieter Fink created ISPN-12266: --------------------------------------- Summary: shutdown cluster should have an option to not block restart if there is no or a shared persistence Key: ISPN-12266 URL: https://issues.redhat.com/browse/ISPN-12266 Project: Infinispan Issue Type: Feature Request Reporter: Wolf-Dieter Fink The current implementation of a full cluster restart will save the CH and state for all caches. If caches does not have a persistence or the persistence is a shared one this might not be necesarry as the cache can start correctly with one node (empty or consistent persistence). In that case it should be allowed to start the cache and make it available. There are two approaches - use extra parameter for shutdown to allow it -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues August 2020