May 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11567) Scattered caches with a single node expire entries immediately

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11567?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11567: ----------------------------------- Fix Version/s: 11.0.0.Final (was: 11.0.0.CR1) > Scattered caches with a single node expire entries immediately > -------------------------------------------------------------- > > Key: ISPN-11567 > URL: https://issues.redhat.com/browse/ISPN-11567 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.1.5.Final, 11.0.0.Dev03 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 11.0.0.Final > > > {{ClusterExpirationManager.checkExpiredMaxIdle()}} sends a {{TouchCommand}} to the other owners and expires the entry locally if the touch was unsuccessful. > {{ScatteredTouchResponseCollector}} is stateless, and reports that the entry has not been touched if it doesn't receive any {{true}} response. However, this is only correct if at least one backup entry existing on another node, and that is not the always the case: e.g. between the backup node leaving the cluster and another node becoming a backup, or when the cluster has a single node. > Since {{ClusterExpirationManager.checkExpiredMaxIdle()}} is called on every read, before the entry being expired on the local node, it means a transient entry in a scattered cache with a single node will expire on the first read, immediately after being inserted. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11519) Cache should not start if it cluster listener replication fails

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11519?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11519: ----------------------------------- Fix Version/s: 11.0.0.Final (was: 11.0.0.CR1) > Cache should not start if it cluster listener replication fails > --------------------------------------------------------------- > > Key: ISPN-11519 > URL: https://issues.redhat.com/browse/ISPN-11519 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.1.5.Final, 11.0.0.Dev03 > Reporter: Dan Berindei > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.Final > > > {{StateConsumerImpl.fetchClusterListeners}} catches any exceptions during the fetch and local installation of cluster listeners from other nodes, and only logs a warning message: > {noformat} > 18:04:14,069 WARN (jgroups-5,Test-NodeD:[]) [StateConsumerImpl] ISPN000284: Problem encountered while installing cluster listener > {noformat} > If a cache starts without installing all the cluster listeners locally, the listeners will miss events for keys that end up with the joiner as the primary owner, which would be pretty hard to debug. We should instea fail fast, and prevent the cache from starting if the cluster listeners cannot be fetched and installed locally. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11482) Provide way for ClusterExecutor to use non blocking thread

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11482?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11482: ----------------------------------- Fix Version/s: 11.0.0.Final (was: 11.0.0.CR1) > Provide way for ClusterExecutor to use non blocking thread > ---------------------------------------------------------- > > Key: ISPN-11482 > URL: https://issues.redhat.com/browse/ISPN-11482 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.Final > > > https://github.com/infinispan/infinispan/pull/7997#discussion_r394122227 changes cluster executor to run tasks on the blocking executor. Unfortunately since a user can run any arbitrary code we don't know if it will block or not. We should provide some way to run non blocking code more easily. Maybe add a new API method that is non blocking? -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11277) Off Heap expiration with custom metadata doesn't work

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11277?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11277: ----------------------------------- Fix Version/s: 11.0.0.Final (was: 11.0.0.CR1) > Off Heap expiration with custom metadata doesn't work > ----------------------------------------------------- > > Key: ISPN-11277 > URL: https://issues.redhat.com/browse/ISPN-11277 > Project: Infinispan > Issue Type: Bug > Components: Core, Off Heap > Reporter: Will Burns > Priority: Major > Fix For: 11.0.0.Final > > > Off heap assumed when a custom metadata was used that it didn't have to track expiration. However this is incorrect, we need to make sure to track the expiration values (created and/or last used) so it can expire properly. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11423) Dump information in panic scenarios

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11423?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11423: ----------------------------------- Fix Version/s: 11.0.0.Final (was: 11.0.0.CR1) > Dump information in panic scenarios > ----------------------------------- > > Key: ISPN-11423 > URL: https://issues.redhat.com/browse/ISPN-11423 > Project: Infinispan > Issue Type: Feature Request > Components: Core, Server > Affects Versions: 10.1.3.Final, 11.0.0.Alpha2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 11.0.0.Final > > > When there is a panic situation (e.g. thread pool exhausted), dump information (e.g. including a thread dump) to a file at FATAL level. > The server should dump the most important information to another log (file) periodically (e.g. every 15 minutes). This log should be enabled by default. > These files can be sent to support via an SOS report. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11395) Indexing configuration serialization broken

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11395?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11395: ----------------------------------- Fix Version/s: 11.0.0.Final (was: 11.0.0.CR1) > Indexing configuration serialization broken > ------------------------------------------- > > Key: ISPN-11395 > URL: https://issues.redhat.com/browse/ISPN-11395 > Project: Infinispan > Issue Type: Bug > Components: Core, Embedded Querying > Affects Versions: 11.0.0.Alpha1, 10.1.3.Final > Reporter: Gustavo Fernandes > Assignee: Nistor Adrian > Priority: Major > Fix For: 11.0.0.Final > > > Some elements are not written to XML such as IndexedEntities and keytransformers -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11381) AdvancedCache.getGroup(key) may return incomplete results during state transfer

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11381?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11381: ----------------------------------- Fix Version/s: 11.0.0.Final (was: 11.0.0.CR1) > AdvancedCache.getGroup(key) may return incomplete results during state transfer > ------------------------------------------------------------------------------- > > Key: ISPN-11381 > URL: https://issues.redhat.com/browse/ISPN-11381 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.4.18.Final, 10.1.2.Final, 11.0.0.Alpha1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 11.0.0.Final > > > {{AdvancedCache.getGroup(groupKey)}} returns all the keys that belong to a group. > If the originator is not an owner, the command is forwarded to the primary owner. If the originator is a primary or a backup owner for the group key, the command is executed locally. > During state transfer, a node may be a write owner for the group key but not a read owner. Currently {{GroupingInterceptor}} uses {{LocalizedCacheTopogy.isWriteOwner(groupKey)}} instead of {{isReadOwner(groupKey)}}, so it executes the command on the originator instead of forwarding it to the primary owner. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11304) Allow scaling up without state transfer

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11304?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11304: ----------------------------------- Fix Version/s: 11.0.0.Final (was: 11.0.0.CR1) > Allow scaling up without state transfer > --------------------------------------- > > Key: ISPN-11304 > URL: https://issues.redhat.com/browse/ISPN-11304 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 10.1.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 11.0.0.Final > > > We should allow a cache to scale up without performing any state transfer, but without losing the data. > To simplify things, the initial version will support a single owner, and will assume that only one node is being added at a time. > The cache must be accessible remotely, but since information about the location of the keys is not accessible from the client, the client is expected to ignore ownership and use a round-robin access strategy. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11248) Add test for ServerTask that utilizes protostream stored entries

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11248?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11248: ----------------------------------- Fix Version/s: 11.0.0.Final (was: 11.0.0.CR1) > Add test for ServerTask that utilizes protostream stored entries > ---------------------------------------------------------------- > > Key: ISPN-11248 > URL: https://issues.redhat.com/browse/ISPN-11248 > Project: Infinispan > Issue Type: Task > Reporter: Will Burns > Priority: Major > Fix For: 11.0.0.Final > > > We currently have a single ServerTask that just prints out "Hello <name>". We should add a new test that actually tests a very likely use case of storing entries in protostream and using a task that deserializes them properly (this could be done automatically by the encoding layer of the cache, if it is working). > We may also want to look into sharing this with a custom loader, as we have users doing this today. And it is quite clunky, so we can see how the usability is in 11.0. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11623) cli -c or --connect should use the default localhost:11222

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11623?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11623: ----------------------------------- Fix Version/s: 11.0.0.Final (was: 11.0.0.CR1) > cli -c or --connect should use the default localhost:11222 > ---------------------------------------------------------- > > Key: ISPN-11623 > URL: https://issues.redhat.com/browse/ISPN-11623 > Project: Infinispan > Issue Type: Enhancement > Components: CLI > Affects Versions: 10.1.5.Final > Reporter: Wolf-Dieter Fink > Assignee: Wolf-Dieter Fink > Priority: Major > Fix For: 11.0.0.Final > > > If cli command is used with connect option without given connection parameter the "-c" option will throw an exception and the "--connect" will not connect without any message. > As before the default should be used to connect -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 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 May 2020