December 2020 - infinispan-issues

[Red Hat JIRA] (ISPN-12528) CLI backup create doesn't reflect directory provided

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-12528?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-12528: ------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 12.0.0.CR1 Resolution: Done > CLI backup create doesn't reflect directory provided > ---------------------------------------------------- > > Key: ISPN-12528 > URL: https://issues.redhat.com/browse/ISPN-12528 > Project: Infinispan > Issue Type: Bug > Components: Backup/Restore, CLI > Affects Versions: 12.0.0.Dev06 > Reporter: Dmitry Volodin > Assignee: Ryan Emerson > Priority: Major > Fix For: 12.0.0.CR1 > > > CLI backup create command doesn't reflect directory provided with following output > {code:java} > [example-infinispan-backup-4927@example-infinispan//containers/default/caches/default]> backup create -d /opt/infinispan/backups -n backup1 > Creating backup 'backup1' > {code} > However backup was created in the default backup directory > {code:java} > sh-4.4$ ls -la /opt/infinispan/backups > total 20 > drwxrwsr-x. 3 root 1000600000 4096 Nov 27 13:48 . > drwxrwxr-x. 1 185 root 72 Nov 27 12:41 .. > drwxrws---. 2 root 1000600000 16384 Nov 27 12:31 lost+found > sh-4.4$ ls -la /opt/infinispan/server/data/backup-manager/ > total 0 > drwxrwsr-x. 3 185 1000600000 21 Nov 27 13:40 . > drwxrwsrwx. 3 root 1000600000 234 Nov 27 13:40 .. > drwxrwsr-x. 2 185 1000600000 25 Nov 27 13:40 backup1 > {code} > -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12557) Links to http2.github.io are broken in documentation

by Ramon Gordillo Gutierrez (Jira)

Ramon Gordillo Gutierrez created ISPN-12557: ----------------------------------------------- Summary: Links to http2.github.io are broken in documentation Key: ISPN-12557 URL: https://issues.redhat.com/browse/ISPN-12557 Project: Infinispan Issue Type: Task Components: Documentation Reporter: Ramon Gordillo Gutierrez Links in [https://github.com/infinispan/infinispan/blob/master/documentation/src/ma... broken. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12556) shutdown server/cluster command documentation need to show the consequence for the next start

by Wolf-Dieter Fink (Jira)

Wolf-Dieter Fink created ISPN-12556: --------------------------------------- Summary: shutdown server/cluster command documentation need to show the consequence for the next start Key: ISPN-12556 URL: https://issues.redhat.com/browse/ISPN-12556 Project: Infinispan Issue Type: Enhancement Components: Documentation Reporter: Wolf-Dieter Fink Assignee: Donald Naro If CLI use shudown * server <list> ** it will stop the connected node if there is no <list> ** it will stop all servers in that list ** !! it will not respect any rebalancing, so it is possible to lose data !! * cluster ** All nodes registered in this cluster will go down ** The curent state is persisted and the members are marked as last stable ** ALL nodes are needed for the next starup !! *** the cluster is in DEGRADED state until all nodes are back *** no new node will able to join *** become available after all nodes are back and ready *** !! remove state of one node and the cluster will not become available !! *** Current there is no way to recover from that and start the cluster (incomplete). The data direcory must be cleared and all data is lost This should be clearly documented! -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12524) Utilise quay.io for test images

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-12524?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-12524: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Utilise quay.io for test images > ------------------------------- > > Key: ISPN-12524 > URL: https://issues.redhat.com/browse/ISPN-12524 > Project: Infinispan > Issue Type: Task > Components: Test Suite > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 11.0.9.Final, 12.0.0.Dev07 > > > hub.docker.com now restricts the amount of downloads possible in a month and this limit is being hit by our CI. Therefore we should pull our images from the quay.io repositories. > {code:java} > Caused by: org.testcontainers.containers.ContainerFetchException: Failed to pull image: jboss/keycloak:10.0.1 > at org.testcontainers.images.RemoteDockerImage.resolve(RemoteDockerImage.java:96) > at org.testcontainers.images.RemoteDockerImage.resolve(RemoteDockerImage.java:26) > at org.testcontainers.utility.LazyFuture.getResolvedValue(LazyFuture.java:17) > at org.testcontainers.utility.LazyFuture.get(LazyFuture.java:39) > at org.testcontainers.containers.GenericContainer.getDockerImageName(GenericContainer.java:1282) > ... 29 more > Caused by: com.github.dockerjava.api.exception.InternalServerErrorException: Status 500: {"message":"toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit"} > at org.testcontainers.shaded.com.github.dockerjava.core.DefaultInvocationBuilder.execute(DefaultInvocationBuilder.java:247) > at org.testcontainers.shaded.com.github.dockerjava.core.DefaultInvocationBuilder.lambda$executeAndStream$1(DefaultInvocationBuilder.java:269) > at java.base/java.lang.Thread.run(Thread.java:834) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12524) Utilise quay.io for test images

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-12524?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-12524: ------------------------------- Fix Version/s: 11.0.9.Final (was: 11.0.7.Final) > Utilise quay.io for test images > ------------------------------- > > Key: ISPN-12524 > URL: https://issues.redhat.com/browse/ISPN-12524 > Project: Infinispan > Issue Type: Task > Components: Test Suite > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 12.0.0.Dev07, 11.0.9.Final > > > hub.docker.com now restricts the amount of downloads possible in a month and this limit is being hit by our CI. Therefore we should pull our images from the quay.io repositories. > {code:java} > Caused by: org.testcontainers.containers.ContainerFetchException: Failed to pull image: jboss/keycloak:10.0.1 > at org.testcontainers.images.RemoteDockerImage.resolve(RemoteDockerImage.java:96) > at org.testcontainers.images.RemoteDockerImage.resolve(RemoteDockerImage.java:26) > at org.testcontainers.utility.LazyFuture.getResolvedValue(LazyFuture.java:17) > at org.testcontainers.utility.LazyFuture.get(LazyFuture.java:39) > at org.testcontainers.containers.GenericContainer.getDockerImageName(GenericContainer.java:1282) > ... 29 more > Caused by: com.github.dockerjava.api.exception.InternalServerErrorException: Status 500: {"message":"toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit"} > at org.testcontainers.shaded.com.github.dockerjava.core.DefaultInvocationBuilder.execute(DefaultInvocationBuilder.java:247) > at org.testcontainers.shaded.com.github.dockerjava.core.DefaultInvocationBuilder.lambda$executeAndStream$1(DefaultInvocationBuilder.java:269) > at java.base/java.lang.Thread.run(Thread.java:834) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12524) Utilise quay.io for test images

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-12524?page=com.atlassian.jira.plugi... ] Ryan Emerson updated ISPN-12524: -------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/infinispan/infinispan/pull/8890, https://github.com/infinispan/infinispan/pull/8891, https://github.com/infinispan/infinispan/pull/8912, https://github.com/infinispan/infinispan/pull/8905 (was: https://github.com/infinispan/infinispan/pull/8890, https://github.com/infinispan/infinispan/pull/8891, https://github.com/infinispan/infinispan/pull/8905) > Utilise quay.io for test images > ------------------------------- > > Key: ISPN-12524 > URL: https://issues.redhat.com/browse/ISPN-12524 > Project: Infinispan > Issue Type: Task > Components: Test Suite > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 11.0.7.Final, 12.0.0.Dev07 > > > hub.docker.com now restricts the amount of downloads possible in a month and this limit is being hit by our CI. Therefore we should pull our images from the quay.io repositories. > {code:java} > Caused by: org.testcontainers.containers.ContainerFetchException: Failed to pull image: jboss/keycloak:10.0.1 > at org.testcontainers.images.RemoteDockerImage.resolve(RemoteDockerImage.java:96) > at org.testcontainers.images.RemoteDockerImage.resolve(RemoteDockerImage.java:26) > at org.testcontainers.utility.LazyFuture.getResolvedValue(LazyFuture.java:17) > at org.testcontainers.utility.LazyFuture.get(LazyFuture.java:39) > at org.testcontainers.containers.GenericContainer.getDockerImageName(GenericContainer.java:1282) > ... 29 more > Caused by: com.github.dockerjava.api.exception.InternalServerErrorException: Status 500: {"message":"toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit"} > at org.testcontainers.shaded.com.github.dockerjava.core.DefaultInvocationBuilder.execute(DefaultInvocationBuilder.java:247) > at org.testcontainers.shaded.com.github.dockerjava.core.DefaultInvocationBuilder.lambda$executeAndStream$1(DefaultInvocationBuilder.java:269) > at java.base/java.lang.Thread.run(Thread.java:834) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-11279) Replace UUID.randomUUID() with Util.threadLocalRandomUUID()

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-11279?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-11279: ------------------------------- Fix Version/s: 11.0.9.Final (was: 11.0.8.Final) > Replace UUID.randomUUID() with Util.threadLocalRandomUUID() > ----------------------------------------------------------- > > Key: ISPN-11279 > URL: https://issues.redhat.com/browse/ISPN-11279 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 10.1.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 11.0.9.Final > > > {{UUID.randomUUID()}} is pretty expensive, because it uses {{SecureRandom}}. > We don't need cryptographically strong UUIDs, so we can generate all our UUIDs with {{Util.threadLocalRandomUUID()}} instead. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-11024) Unable to use binary memory eviction with protobuf

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-11024?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-11024: ------------------------------- Fix Version/s: 11.0.9.Final (was: 11.0.8.Final) > Unable to use binary memory eviction with protobuf > -------------------------------------------------- > > Key: ISPN-11024 > URL: https://issues.redhat.com/browse/ISPN-11024 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 10.0.1.Final > Reporter: Jens Reimann > Assignee: Will Burns > Priority: Critical > Fix For: 11.0.9.Final > > > Enabling binary eviction, e.g.: > {code:xml} > <memory> > <binary strategy="REMOVE" size="134217728" eviction="MEMORY"/> > </memory> > {code} > When storing protobuf based types, throws the following exception: > {code} > 15:36:29,859 ERROR [org.infinispan.interceptors.impl.InvocationContextInterceptor] (async-thread--p2-t18) ISPN000136: Error executing command PrepareCommand on Cache 'devices', writing keys []: java.lang.IllegalArgumentException: Size of Class class org.infinispan.query.remote.impl.indexing.ProtobufValueWrapper cannot be determined using given entry size calculator :class org.infinispan.container.entries.PrimitiveEntrySizeCalculator > {code} > As protobuf produces a binary representation of the data, it is possible to calculate a size for that object. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12022) Provide a REST command to reset microprofile metrics

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-12022?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-12022: ------------------------------- Fix Version/s: 11.0.9.Final (was: 11.0.8.Final) > Provide a REST command to reset microprofile metrics > ---------------------------------------------------- > > Key: ISPN-12022 > URL: https://issues.redhat.com/browse/ISPN-12022 > Project: Infinispan > Issue Type: Enhancement > Components: JMX, reporting and management > Affects Versions: 10.1.0.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 11.0.9.Final > > > The microprofile metrics API does not provide a standard way to reset metrics. > We'll need to add one REST handler for this, if possible. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12005) Store purge should ignore errors

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-12005?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-12005: ------------------------------- Fix Version/s: 11.0.9.Final (was: 11.0.8.Final) > Store purge should ignore errors > -------------------------------- > > Key: ISPN-12005 > URL: https://issues.redhat.com/browse/ISPN-12005 > Project: Infinispan > Issue Type: Bug > Components: Core, Loaders and Stores > Affects Versions: 10.1.5.Final, 11.0.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 12.0.0.Final, 11.0.9.Final > > > Purging of expired entries from stores is a pretty involved process, especially with {{RocksDBStore}}. When there's a problem unmarshalling the expired bucket or deleting an expired key, the purge task bails out immediately, without processing the remaining keys. To make matters worse, the exception it not logged anywhere. The only sign that something is wrong is a growing store (in the case of {{RocksDBStore}}, a growing number of SST files). -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2020