October 2020 - infinispan-issues - Jboss List Archives

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

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11024?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11024: ----------------------------------- Fix Version/s: 11.0.5.Final (was: 11.0.4.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.5.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

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

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12005?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12005: ----------------------------------- Fix Version/s: 11.0.5.Final (was: 11.0.4.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.5.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

[JBoss JIRA] (ISPN-11585) Use JavaSerializationMarshaller in jcache TCK modules

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11585?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11585: ----------------------------------- Fix Version/s: 11.0.5.Final (was: 11.0.4.Final) > Use JavaSerializationMarshaller in jcache TCK modules > ----------------------------------------------------- > > Key: ISPN-11585 > URL: https://issues.redhat.com/browse/ISPN-11585 > Project: Infinispan > Issue Type: Task > Components: JCache > Affects Versions: 11.0.0.Dev03 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 11.0.5.Final > > > We should run the JSR-107 TCK with the java serialization marshaller, not with the protostream marshaller, to ensure that Infinispan is usable as a JCache implementation with minimal application code changes. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11873) Add report failure for RxJava Undelivered Errors

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11873?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11873: ----------------------------------- Fix Version/s: 11.0.5.Final (was: 11.0.4.Final) > Add report failure for RxJava Undelivered Errors > ------------------------------------------------ > > Key: ISPN-11873 > URL: https://issues.redhat.com/browse/ISPN-11873 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 11.0.5.Final > > > We should install an error handler into RxJava during the test suite so that if we get any undelivered exceptions they will be reported, similar to uncaught exception handler that was added. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12015) NPE if DefaultCacheManager created with InputStream and `xi:include` required

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12015?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12015: ----------------------------------- Fix Version/s: 11.0.5.Final (was: 11.0.4.Final) > NPE if DefaultCacheManager created with InputStream and `xi:include` required > ----------------------------------------------------------------------------- > > Key: ISPN-12015 > URL: https://issues.redhat.com/browse/ISPN-12015 > Project: Infinispan > Issue Type: Bug > Components: Configuration, Core > Affects Versions: 11.0.0.Final > Reporter: Ryan Emerson > Assignee: Tristan Tarrant > Priority: Major > Fix For: 11.0.5.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 7 months

1
0
0 / 0

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

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12022?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12022: ----------------------------------- Fix Version/s: 11.0.5.Final (was: 11.0.4.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.5.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

[JBoss JIRA] (ISPN-12376) Deal with FAILED Health status in the console

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12376?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12376: ----------------------------------- Fix Version/s: 11.0.5.Final (was: 11.0.4.Final) > Deal with FAILED Health status in the console > --------------------------------------------- > > Key: ISPN-12376 > URL: https://issues.redhat.com/browse/ISPN-12376 > Project: Infinispan > Issue Type: Feature Request > Components: Console > Affects Versions: 11.0.3.Final, 12.0.0.Dev04 > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Critical > Fix For: 12.0.0.Dev05, 11.0.5.Final > > > Health has not a new status 'FAILED' that needs to handled -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12222) Infinispan Backup Operator Integration

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-12222?page=com.atlassian.jira.plugi... ] Ryan Emerson updated ISPN-12222: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-operator/pull/596 > Infinispan Backup Operator Integration > -------------------------------------- > > Key: ISPN-12222 > URL: https://issues.redhat.com/browse/ISPN-12222 > Project: Infinispan > Issue Type: Enhancement > Components: Operator > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > > In kubernetes environments the operator can be used to automate the steps required by a user to perform a backup of container content. > Typically an Infinispan pod will have a minimal volume size in order to prevent excessive resource allocation, say 1GB. However, if a cluster is large then it's very likely that it's in-memory content will exceed this amount. Therefore, during a cluster backup it's necessary to mount a volume with sufficient capacity to accomodate the created backup file. To automate this process we should create a backup CRD. > h3. Workflow > The operator provisions an additional pod with a mounted volume for storing the final backup. This pod joins the Infinispan cluster with {{zero-capacity-node=true}} so that no state-transfer is performed when joining. The operator then initiates the backup procedure on this node, via this node's REST endpoint, using the path of the mounted volume as the backups final destination. On completion, the pod of the zero-capacity-node is terminated. > h4. Restore > The same workflow can be used for restoring a backup from an existing volume. > h3. CR Parameters: > * Backup path > * Resources to include > * Existing volume to mount > * Create volume with x capacity, x could be automatically determined by inspecting the container content > * Shutdown cluster on completion? -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12222) Infinispan Backup Operator Integration

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-12222?page=com.atlassian.jira.plugi... ] Ryan Emerson updated ISPN-12222: -------------------------------- Status: Open (was: New) > Infinispan Backup Operator Integration > -------------------------------------- > > Key: ISPN-12222 > URL: https://issues.redhat.com/browse/ISPN-12222 > Project: Infinispan > Issue Type: Enhancement > Components: Operator > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > > In kubernetes environments the operator can be used to automate the steps required by a user to perform a backup of container content. > Typically an Infinispan pod will have a minimal volume size in order to prevent excessive resource allocation, say 1GB. However, if a cluster is large then it's very likely that it's in-memory content will exceed this amount. Therefore, during a cluster backup it's necessary to mount a volume with sufficient capacity to accomodate the created backup file. To automate this process we should create a backup CRD. > h3. Workflow > The operator provisions an additional pod with a mounted volume for storing the final backup. This pod joins the Infinispan cluster with {{zero-capacity-node=true}} so that no state-transfer is performed when joining. The operator then initiates the backup procedure on this node, via this node's REST endpoint, using the path of the mounted volume as the backups final destination. On completion, the pod of the zero-capacity-node is terminated. > h4. Restore > The same workflow can be used for restoring a backup from an existing volume. > h3. CR Parameters: > * Backup path > * Resources to include > * Existing volume to mount > * Create volume with x capacity, x could be automatically determined by inspecting the container content > * Shutdown cluster on completion? -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12385) ServerRunMode.FORKED mode test driver doesn't work with a secured server

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/ISPN-12385?page=com.atlassian.jira.plugi... ] Radoslav Husar updated ISPN-12385: ---------------------------------- Description: Clients get a 401 with a default server profile e.g. when shutting down an instance and will kill the server instead. (was: Clients get a 401 with a default server profile e.g. when shutting down an instance.) > ServerRunMode.FORKED mode test driver doesn't work with a secured server > ------------------------------------------------------------------------ > > Key: ISPN-12385 > URL: https://issues.redhat.com/browse/ISPN-12385 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 11.0.3.Final, 12.0.0.Dev04 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > Clients get a 401 with a default server profile e.g. when shutting down an instance and will kill the server instead. -- 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 October 2020