June 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11960) RemoteCache configuration enhancements (wildcards, . in name, URI for config)

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11960?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11960: ----------------------------------- Description: It should be possible to define remote cache names using wildcard globbing {{*}} so that configuration apply to all cache names which match. Additionally we should be able to support cache names containing {{.}} characters in the declarative configuration. In this case names should be enclosed in square brackets, e.g {{[example.MyCache]}} Since passing a cache configuration in XML is cumbersome, we should support passing a URI pointing to a separate file. was: It should be possible to define remote cache names using wildcard globbing {{*}} so that configuration apply to all cache names which match. Additionally we should be able to support cache names containing {{.}} characters in the declarative configuration. In this case names should be enclosed in square brackets, e.g {{[example.MyCache]}} > RemoteCache configuration enhancements (wildcards, . in name, URI for config) > ----------------------------------------------------------------------------- > > Key: ISPN-11960 > URL: https://issues.redhat.com/browse/ISPN-11960 > Project: Infinispan > Issue Type: Enhancement > Components: Hot Rod > Affects Versions: 11.0.0.CR1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 11.0.0.Final > > > It should be possible to define remote cache names using wildcard globbing {{*}} so that configuration apply to all cache names which match. > Additionally we should be able to support cache names containing {{.}} characters in the declarative configuration. In this case names should be enclosed in square brackets, e.g {{[example.MyCache]}} > Since passing a cache configuration in XML is cumbersome, we should support passing a URI pointing to a separate file. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11960) RemoteCache configuration enhancements (wildcards, . in name, URI for config)

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11960?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11960: ----------------------------------- Summary: RemoteCache configuration enhancements (wildcards, . in name, URI for config) (was: Support wildcard globbing and names with . in per-RemoteCache configuration ) > RemoteCache configuration enhancements (wildcards, . in name, URI for config) > ----------------------------------------------------------------------------- > > Key: ISPN-11960 > URL: https://issues.redhat.com/browse/ISPN-11960 > Project: Infinispan > Issue Type: Enhancement > Components: Hot Rod > Affects Versions: 11.0.0.CR1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 11.0.0.Final > > > It should be possible to define remote cache names using wildcard globbing {{*}} so that configuration apply to all cache names which match. > Additionally we should be able to support cache names containing {{.}} characters in the declarative configuration. In this case names should be enclosed in square brackets, e.g {{[example.MyCache]}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11960) Support wildcard globbing and names with . in per-RemoteCache configuration

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11960?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11960: ----------------------------------- Description: It should be possible to define remote cache names using wildcard globbing {{*}} so that configuration apply to all cache names which match. Additionally we should be able to support cache names containing {{.}} characters in the declarative configuration. In this case names should be enclosed in square brackets, e.g {{[example.MyCache]}} was:It should be possible to define remote cache names using wildcard globbing (*) so that configuration apply to all cache names which match. > Support wildcard globbing and names with . in per-RemoteCache configuration > ----------------------------------------------------------------------------- > > Key: ISPN-11960 > URL: https://issues.redhat.com/browse/ISPN-11960 > Project: Infinispan > Issue Type: Enhancement > Components: Hot Rod > Affects Versions: 11.0.0.CR1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 11.0.0.Final > > > It should be possible to define remote cache names using wildcard globbing {{*}} so that configuration apply to all cache names which match. > Additionally we should be able to support cache names containing {{.}} characters in the declarative configuration. In this case names should be enclosed in square brackets, e.g {{[example.MyCache]}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11960) Support wildcard globbing and names with . in per-RemoteCache configuration

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11960?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11960: ----------------------------------- Summary: Support wildcard globbing and names with . in per-RemoteCache configuration (was: Support wildcard globbing in per-RemoteCache configuration ) > Support wildcard globbing and names with . in per-RemoteCache configuration > ----------------------------------------------------------------------------- > > Key: ISPN-11960 > URL: https://issues.redhat.com/browse/ISPN-11960 > Project: Infinispan > Issue Type: Enhancement > Components: Hot Rod > Affects Versions: 11.0.0.CR1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 11.0.0.Final > > > It should be possible to define remote cache names using wildcard globbing (*) so that configuration apply to all cache names which match. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11960) Support wildcard globbing in per-RemoteCache configuration

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-11960: -------------------------------------- Summary: Support wildcard globbing in per-RemoteCache configuration Key: ISPN-11960 URL: https://issues.redhat.com/browse/ISPN-11960 Project: Infinispan Issue Type: Enhancement Components: Hot Rod Affects Versions: 11.0.0.CR1 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 11.0.0.Final It should be possible to define remote cache names using wildcard globbing (*) so that configuration apply to all cache names which match. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11950) Create a new module called server-integration module into integrationtests module

by Gustavo Lira e Silva (Jira)

[ https://issues.redhat.com/browse/ISPN-11950?page=com.atlassian.jira.plugi... ] Gustavo Lira e Silva updated ISPN-11950: ---------------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/8423 > Create a new module called server-integration module into integrationtests module > --------------------------------------------------------------------------------- > > Key: ISPN-11950 > URL: https://issues.redhat.com/browse/ISPN-11950 > Project: Infinispan > Issue Type: Enhancement > Components: Test Suite > Affects Versions: 11.0.0.Dev05 > Reporter: Gustavo Lira e Silva > Assignee: Gustavo Lira e Silva > Priority: Major > Labels: qe-task > > As a QE I would like to create new tests and modules into {{integrationtests}} module. > We need a new module to run infinispan server, we will use this module as parent for some other modules. > The structure will be like: > {noformat} > integrationtests/server-integration (new module) > integrationtests/server-integration/wildfly-modules (will be moved to here) > integrationtests/server-integration/backward-compatibility > integrationtests/server-integration/third-party-servers > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11937) JDBCStringBasedStore needs test around a rollback occurring

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-11937?page=com.atlassian.jira.plugi... ] Ryan Emerson resolved ISPN-11937. --------------------------------- Assignee: Will Burns Resolution: Done > JDBCStringBasedStore needs test around a rollback occurring > ----------------------------------------------------------- > > Key: ISPN-11937 > URL: https://issues.redhat.com/browse/ISPN-11937 > Project: Infinispan > Issue Type: Task > Components: Loaders and Stores > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.Final > > > We are missing some coverage around a store rolling back and it working properly. As JDBCStore is our only store that currently implements the transactional support it should be simple to add a test to it. > https://github.com/infinispan/infinispan/pull/8400#discussion_r432506704 -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11959) Add custom NonBlockingStore test

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11959?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11959: ------------------------------ Status: Open (was: New) > Add custom NonBlockingStore test > -------------------------------- > > Key: ISPN-11959 > URL: https://issues.redhat.com/browse/ISPN-11959 > Project: Infinispan > Issue Type: Task > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.Final > > > We have the new SPI with ISPN-10373. We should add a test that verifies this works in the infinispan-server-tests module. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11959) Add custom NonBlockingStore test

by Will Burns (Jira)

Will Burns created ISPN-11959: --------------------------------- Summary: Add custom NonBlockingStore test Key: ISPN-11959 URL: https://issues.redhat.com/browse/ISPN-11959 Project: Infinispan Issue Type: Task Reporter: Will Burns Assignee: Will Burns Fix For: 11.0.0.Final We have the new SPI with ISPN-10373. We should add a test that verifies this works in the infinispan-server-tests module. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11679) Bad uneven segment distributions can happen after the rebalancing with SyncConsistentHashFactory

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11679?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11679: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Bad uneven segment distributions can happen after the rebalancing with SyncConsistentHashFactory > ------------------------------------------------------------------------------------------------ > > Key: ISPN-11679 > URL: https://issues.redhat.com/browse/ISPN-11679 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.4.19.Final, 10.1.6.Final > Reporter: Masafumi Miura > Assignee: Dan Berindei > Priority: Major > Fix For: 11.0.0.Final > > > Uneven segment distribution can happen after rebalancing with SyncConsistentHashFactory. > Even if a larger number of segments than "20 * number of nodes" is configured, some nodes have only around 50-60% number of segments than other nodes after the rebalance in the worst case. > I understand the documentation (like the following) states about the possibility of slight uneven distribution as a potential drawback of SyncConsistentHashFactory. > [Infinispan 10 configuration guide|https://infinispan.org/docs/stable/titles/configuring/configuring.h...] says: > {quote} > This implementation does have some negative points in that the load distribution is slightly uneven. It also moves more segments than strictly necessary on a join or leave. > {quote} > [JDG 7 Developer Guide|https://access.redhat.com/documentation/en-us/red_hat_data_grid/7.2...] says: > {quote} > It has a potential drawback in that it can move a greater number of segments than necessary during re-balancing. This can be mitigated by using a larger number of segments. > Another potential drawback is that the segments are not distributed as evenly as possible, and actually using a very large number of segments can make the distribution of segments worse. > {quote} > However, only half segments than others is not a slight uneven. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2020