December 2019 - infinispan-issues

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-11081: -------------------------------------- Summary: Data Store Key: ISPN-11081 URL: https://issues.redhat.com/browse/ISPN-11081 Project: Infinispan Issue Type: Task Components: Core Affects Versions: 10.1.0.CR1 Reporter: Tristan Tarrant Assignee: Dan Berindei Fix For: 11.0.0.Final In scenarios where Infinispan is used as a persistent data store, the elasticity provided by rebalancing on scaling down (either voluntarily or because of node failure) can lead to data loss, even with persistent caches if all the owners of a segment leave the cluster before rebalancing can be completed. The remaining cluster should prevent writes to the lost segments until the nodes that own them are restarted. It should be possible to configure Infinispan so that elasticity only applies when scaling up, i.e. adding a node will cause a rebalance. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

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

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11024?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11024: ------------------------------ Summary: Unable to use binary memory eviction with indexing (was: Unable to use binary memory eviction with protobuf) > Unable to use binary memory eviction with indexing > -------------------------------------------------- > > 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 > > 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)

6 years, 4 months

1
0
0 / 0

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

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11024?page=com.atlassian.jira.plugi... ] Work on ISPN-11024 started by Will Burns. ----------------------------------------- > Unable to use binary memory eviction with indexing > -------------------------------------------------- > > 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 > > 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)

6 years, 4 months

1
0
0 / 0

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

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11024?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11024: ------------------------------ Summary: Unable to use binary memory eviction with protobuf (was: Unable to use binary eviction with protobuf) > 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: Blocker > > 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)

6 years, 4 months

1
0
0 / 0

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

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11024?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11024: ------------------------------ Priority: Critical (was: Blocker) > 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 > > 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)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11079) Cluster Expiration and Optimistic Transactions write skew issues

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11079?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11079: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7681 > Cluster Expiration and Optimistic Transactions write skew issues > ---------------------------------------------------------------- > > Key: ISPN-11079 > URL: https://issues.redhat.com/browse/ISPN-11079 > Project: Infinispan > Issue Type: Bug > Components: Expiration > Reporter: Will Burns > Priority: Major > Fix For: 10.1.0.Final, 11.0.0.Final > > > Optimistic write skew and clustered expiration can have some weird issues > One such is: > The issue is the following: > 1. RemoveExpiredCommand reads the expired from the container with version 1 and puts in its context > 2. PutKeyValueCommand sees nothing in container due to expired and adds a new entry with version 1 in its context > 3. Put gets the lock and replaces the value > 4. RemoveExpiredCommand attempts to run and because it saw the old value the lifespans still match (if different) > 5. Then the write skew passes for the remove expired command since the value in container and its context both have version 1 > To workaround this for now we should prevent a get of an expired entry from returning early when using optimistic transactions. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11079) Cluster Expiration and Optimistic Transactions write skew issues

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11079?page=com.atlassian.jira.plugi... ] Will Burns reassigned ISPN-11079: --------------------------------- Assignee: Will Burns > Cluster Expiration and Optimistic Transactions write skew issues > ---------------------------------------------------------------- > > Key: ISPN-11079 > URL: https://issues.redhat.com/browse/ISPN-11079 > Project: Infinispan > Issue Type: Bug > Components: Expiration > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.1.0.Final, 11.0.0.Final > > > Optimistic write skew and clustered expiration can have some weird issues > One such is: > The issue is the following: > 1. RemoveExpiredCommand reads the expired from the container with version 1 and puts in its context > 2. PutKeyValueCommand sees nothing in container due to expired and adds a new entry with version 1 in its context > 3. Put gets the lock and replaces the value > 4. RemoveExpiredCommand attempts to run and because it saw the old value the lifespans still match (if different) > 5. Then the write skew passes for the remove expired command since the value in container and its context both have version 1 > To workaround this for now we should prevent a get of an expired entry from returning early when using optimistic transactions. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11079) Cluster Expiration and Optimistic Transactions write skew issues

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11079?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11079: ------------------------------ Fix Version/s: 10.1.0.Final 11.0.0.Final > Cluster Expiration and Optimistic Transactions write skew issues > ---------------------------------------------------------------- > > Key: ISPN-11079 > URL: https://issues.redhat.com/browse/ISPN-11079 > Project: Infinispan > Issue Type: Bug > Components: Expiration > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.1.0.Final, 11.0.0.Final > > > Optimistic write skew and clustered expiration can have some weird issues > One such is: > The issue is the following: > 1. RemoveExpiredCommand reads the expired from the container with version 1 and puts in its context > 2. PutKeyValueCommand sees nothing in container due to expired and adds a new entry with version 1 in its context > 3. Put gets the lock and replaces the value > 4. RemoveExpiredCommand attempts to run and because it saw the old value the lifespans still match (if different) > 5. Then the write skew passes for the remove expired command since the value in container and its context both have version 1 > To workaround this for now we should prevent a get of an expired entry from returning early when using optimistic transactions. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11079) Cluster Expiration and Optimistic Transactions write skew issues

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11079?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11079: ------------------------------ Status: Open (was: New) > Cluster Expiration and Optimistic Transactions write skew issues > ---------------------------------------------------------------- > > Key: ISPN-11079 > URL: https://issues.redhat.com/browse/ISPN-11079 > Project: Infinispan > Issue Type: Bug > Components: Expiration > Reporter: Will Burns > Priority: Major > > Optimistic write skew and clustered expiration can have some weird issues > One such is: > The issue is the following: > 1. RemoveExpiredCommand reads the expired from the container with version 1 and puts in its context > 2. PutKeyValueCommand sees nothing in container due to expired and adds a new entry with version 1 in its context > 3. Put gets the lock and replaces the value > 4. RemoveExpiredCommand attempts to run and because it saw the old value the lifespans still match (if different) > 5. Then the write skew passes for the remove expired command since the value in container and its context both have version 1 > To workaround this for now we should prevent a get of an expired entry from returning early when using optimistic transactions. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11080) Caches endpoint delete size and add health

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-11080?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-11080: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7680 > Caches endpoint delete size and add health > ------------------------------------------ > > Key: ISPN-11080 > URL: https://issues.redhat.com/browse/ISPN-11080 > Project: Infinispan > Issue Type: Feature Request > Components: Console, REST > Affects Versions: 10.1.0.CR1 > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Labels: console, console-ng, rest, rest_api > Fix For: 10.1.0.Final > > > Instead of calling size at a risk of being a very long operation for all the caches, get the health and display also this information in the console > [ { > "status" : "RUNNING", > "name" : "cache1", > "type" : "local-cache", > "simple_cache" : false, > "transactional" : false, > "persistent" : false, > "bounded": false, > "secured": false, > "indexed": true, > "has_remote_backup": true, > "health":"HEALTHY" > }, { > "status" : "RUNNING", > "name" : "cache2", > "type" : "distributed-cache", > "simple_cache" : false, > "transactional" : true, > "persistent" : false, > "bounded": false, > "secured": false, > "indexed": true, > "has_remote_backup": true, > "health":"HEALTHY" > }] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 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 December 2019