September 2020 - infinispan-issues

[JBoss JIRA] (ISPN-12206) Create an InfinispanXSiteServerRule and increase the tests coverage

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-12206?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-12206: ------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 12.0.0.Dev04 Resolution: Done > Create an InfinispanXSiteServerRule and increase the tests coverage > ------------------------------------------------------------------- > > Key: ISPN-12206 > URL: https://issues.redhat.com/browse/ISPN-12206 > Project: Infinispan > Issue Type: Enhancement > Components: Test Suite > Affects Versions: 12.0.0.Dev01 > Reporter: Gustavo Lira e Silva > Assignee: Gustavo Lira e Silva > Priority: Major > Fix For: 12.0.0.Dev04 > > > Create an InfinispanXSiteServerRule to replace [https://github.com/infinispan/infinispan/blob/master/server/test... is using one InfinispanServerRule for each site. > Increase the tests coverage -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12353) REST allow backup restore progress to be submitted and polled

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-12353?page=com.atlassian.jira.plugi... ] Ryan Emerson updated ISPN-12353: -------------------------------- Status: Open (was: New) > REST allow backup restore progress to be submitted and polled > ------------------------------------------------------------- > > Key: ISPN-12353 > URL: https://issues.redhat.com/browse/ISPN-12353 > Project: Infinispan > Issue Type: Enhancement > Components: REST > Affects Versions: 12.0.0.Dev03 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 12.0.0.Final > > > The current rest endpoint for restoring backups is too restrictive, as there is no way to submit a restoration and then poll it's current status. We should add the following so that the endpoints are akin to the process for creating a backup: > {code} > # Create, return 202 or 409 if {restoreName} already exists > POST /rest/v2/cache-managers/{cacheManagerName}/restores/{restoreName} > # Poll progress 201 complete, 202 if in progress, or 404 if not found > HEAD /rest/v2/cache-managers/{cacheManagerName}/restores/{restoreName} > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12353) REST allow backup restore progress to be submitted and polled

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-12353?page=com.atlassian.jira.plugi... ] Ryan Emerson updated ISPN-12353: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8714 > REST allow backup restore progress to be submitted and polled > ------------------------------------------------------------- > > Key: ISPN-12353 > URL: https://issues.redhat.com/browse/ISPN-12353 > Project: Infinispan > Issue Type: Enhancement > Components: REST > Affects Versions: 12.0.0.Dev03 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 12.0.0.Final > > > The current rest endpoint for restoring backups is too restrictive, as there is no way to submit a restoration and then poll it's current status. We should add the following so that the endpoints are akin to the process for creating a backup: > {code} > # Create, return 202 or 409 if {restoreName} already exists > POST /rest/v2/cache-managers/{cacheManagerName}/restores/{restoreName} > # Poll progress 201 complete, 202 if in progress, or 404 if not found > HEAD /rest/v2/cache-managers/{cacheManagerName}/restores/{restoreName} > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-161) Maven compiler plugin 2.8.1 and Protostream seem broken

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/IPROTO-161?page=com.atlassian.jira.plugi... ] Nistor Adrian updated IPROTO-161: --------------------------------- Fix Version/s: 4.3.4.Final > Maven compiler plugin 2.8.1 and Protostream seem broken > ------------------------------------------------------- > > Key: IPROTO-161 > URL: https://issues.redhat.com/browse/IPROTO-161 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 4.3.3.Final > Reporter: Katia Aresti > Assignee: Nistor Adrian > Priority: Blocker > Fix For: 4.3.4.Final > > > Coming from a Quarkus issue, the maven compiler plugin in version 3.8.1 seems not working properly with classes compilation and generation > > Check the Quarkus issue. > > [https://github.com/quarkusio/quarkus/issues/9980] > > This might be a library problem or a maven problem > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-161) Maven compiler plugin 2.8.1 and Protostream seem broken

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/IPROTO-161?page=com.atlassian.jira.plugi... ] Nistor Adrian commented on IPROTO-161: -------------------------------------- Most likely a maven problem, from past experience, but I haven't really looked at the reproducer yet > Maven compiler plugin 2.8.1 and Protostream seem broken > ------------------------------------------------------- > > Key: IPROTO-161 > URL: https://issues.redhat.com/browse/IPROTO-161 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 4.3.3.Final > Reporter: Katia Aresti > Assignee: Nistor Adrian > Priority: Blocker > > Coming from a Quarkus issue, the maven compiler plugin in version 3.8.1 seems not working properly with classes compilation and generation > > Check the Quarkus issue. > > [https://github.com/quarkusio/quarkus/issues/9980] > > This might be a library problem or a maven problem > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-161) Maven compiler plugin 2.8.1 and Protostream seem broken

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/IPROTO-161?page=com.atlassian.jira.plugi... ] Nistor Adrian updated IPROTO-161: --------------------------------- Status: Open (was: New) > Maven compiler plugin 2.8.1 and Protostream seem broken > ------------------------------------------------------- > > Key: IPROTO-161 > URL: https://issues.redhat.com/browse/IPROTO-161 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 4.3.3.Final > Reporter: Katia Aresti > Assignee: Nistor Adrian > Priority: Blocker > > Coming from a Quarkus issue, the maven compiler plugin in version 3.8.1 seems not working properly with classes compilation and generation > > Check the Quarkus issue. > > [https://github.com/quarkusio/quarkus/issues/9980] > > This might be a library problem or a maven problem > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12354) Confusing naming of statistic "total_number_of_entries"

by Wolf-Dieter Fink (Jira)

Wolf-Dieter Fink created ISPN-12354: --------------------------------------- Summary: Confusing naming of statistic "total_number_of_entries" Key: ISPN-12354 URL: https://issues.redhat.com/browse/ISPN-12354 Project: Infinispan Issue Type: Bug Reporter: Wolf-Dieter Fink For a cache there are 3 metrics: "current_number_of_entries_in_memory" : 0, <-- current number in memory "current_number_of_entries" : 14, <-- total number of entries (size) But "total_number_of_entries" is not the total number of entries in this cache but the number of put's for the running server. See code https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o... So the naming "total number" is not correct and should be changed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9776) Disconnected Near Cache

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-9776?page=com.atlassian.jira.plugin... ] Will Burns commented on ISPN-9776: ---------------------------------- So my take on this is having a setting, per cache, that when enabled would not throw an error if it cannot connect to a server. Instead it would return null and use near cache values if present. Then as mentioned in the description upon reconnecting with a given server we would clear the near cache. Also once we have found we are not connected to any server we should probably fall back to returning null quickly, until a connection can be reestablished asynchronously. > Disconnected Near Cache > ----------------------- > > Key: ISPN-9776 > URL: https://issues.redhat.com/browse/ISPN-9776 > Project: Infinispan > Issue Type: Bug > Components: Hot Rod > Reporter: Tristan Tarrant > Priority: Major > Labels: keycloak > > The Hot Rod client with near cache enabled should have the option to be able to work in disconnected mode. On reconnection the near cache should be invalidated. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8824) Invalidate near cache if no servers are accessible

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-8824?page=com.atlassian.jira.plugin... ] Tristan Tarrant reassigned ISPN-8824: ------------------------------------- Assignee: Will Burns > Invalidate near cache if no servers are accessible > -------------------------------------------------- > > Key: ISPN-8824 > URL: https://issues.redhat.com/browse/ISPN-8824 > Project: Infinispan > Issue Type: Bug > Reporter: Galder Zamarreño > Assignee: Will Burns > Priority: Major > > Invalidate near cache if no servers are accessible. > The client has the concept of a cluster restart, so it can try to reconnect to the cluster if completely offline. We'd need to decide exactly when to do this. > Also, check how client's site failover works with this. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12352) Set license information when missing

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-12352?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-12352: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Set license information when missing > ------------------------------------ > > Key: ISPN-12352 > URL: https://issues.redhat.com/browse/ISPN-12352 > Project: Infinispan > Issue Type: Enhancement > Components: Build > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 11.0.4.Final, 12.0.0.Dev04 > > > There are some dependencies that don't report the licenses in the expected places (pom.xml for maven, package.json for nodejs). In those cases, the license is reported as "unknown" or empty. > Create a new class in infinispan-tools where it receives an XML (manually created) with the licenses for "problematic" dependencies and merge it in the licenses.xml file. It shouldn't touch correct reported licenses. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2020