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.CR1 (was: 11.0.0.Dev05) > 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.CR1 > > > {{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, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11759) ProtocolServer should use BlockingManager instead of Executor

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11759?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11759: ----------------------------------- Fix Version/s: 11.0.0.CR1 (was: 11.0.0.Dev05) > ProtocolServer should use BlockingManager instead of Executor > ------------------------------------------------------------- > > Key: ISPN-11759 > URL: https://issues.redhat.com/browse/ISPN-11759 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.CR1 > > > Protocol Servers use an Executor to submit tasks that may block. We should instead use the new BlockingManager as it properly handles the blocking threads. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11717) Deprecate ConsistentHashFactory customization

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11717?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11717: ----------------------------------- Fix Version/s: 11.0.0.CR1 (was: 11.0.0.Dev05) > Deprecate ConsistentHashFactory customization > --------------------------------------------- > > Key: ISPN-11717 > URL: https://issues.redhat.com/browse/ISPN-11717 > Project: Infinispan > Issue Type: Task > Components: Configuration, Core > Affects Versions: 11.0.0.Dev04 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 11.0.0.CR1, 11.0.0.Final > > > There aren't any good reasons to use a {{ConsistentHashFactory}} implementation different than the default selected by {{StateTransferManagerImpl#pickConsistentHashFactory}}. > The configuration attribute made sense when the default was {{DefaultConsistentHashFactory}}, but {{SyncConsistentHashFactory}} is much better nowadays, and it's pretty much impossible to come up with an implementation that works in more than one cache mode with the current API. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11688) Remove rxjava references to internal classes

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11688?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11688: ----------------------------------- Fix Version/s: 11.0.0.CR1 (was: 11.0.0.Dev05) > Remove rxjava references to internal classes > -------------------------------------------- > > Key: ISPN-11688 > URL: https://issues.redhat.com/browse/ISPN-11688 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.CR1 > > > We are utilizing some internal rxjava classes for our custom operator and functions. We should remove this to prevent these from not being visible in the future. We may also be able to make operators that are a bit cleaner as well. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11674) Clean up RemoteCache method overrides

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11674?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11674: ----------------------------------- Fix Version/s: 11.0.0.CR1 (was: 11.0.0.Dev05) > Clean up RemoteCache method overrides > ------------------------------------- > > Key: ISPN-11674 > URL: https://issues.redhat.com/browse/ISPN-11674 > Project: Infinispan > Issue Type: Enhancement > Components: Hot Rod > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.CR1 > > > There are a lot of various method overrides in the RemoteCache. This is because of async, versions and expiration overrides bloating almost all methods by eight times. We should consolidate these so they are simpler to handle and harder to mess up. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11634) Merge TopologyUpdateStableCommand and TopologyUpdateCommand

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11634?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11634: ----------------------------------- Fix Version/s: 11.0.0.CR1 (was: 11.0.0.Dev05) > Merge TopologyUpdateStableCommand and TopologyUpdateCommand > ----------------------------------------------------------- > > Key: ISPN-11634 > URL: https://issues.redhat.com/browse/ISPN-11634 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 11.0.0.Dev04 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 11.0.0.CR1 > > > {code:java} > 19:48:14,672 TRACE (testng-Test:[]) [TopologyManagementHelper] Attempting to execute command on self: StableTopologyUpdateCommand{cacheName='testCache', origin=Test-NodeD, currentCH=DefaultConsistentHash > {ns=256, owners = (1)[Test-NodeE: 256+0]} > , pendingCH=null, actualMembers=[Test-NodeE], persistentUUIDs=[72b17309-62d1-4928-abf6-88a8606ef342], rebalanceId=5, topologyId=27, viewId=7} > 19:48:14,686 INFO (jgroups-5,Test-NodeE:[]) [CLUSTER] ISPN000094: Received new cluster view for channel org.infinispan.statetransfer.Test: [Test-NodeE|8] (1) [Test-NodeE] > 19:48:14,690 TRACE (non-blocking-thread-Test-NodeE-p9541-t5:[Merge-8]) [PreferConsistencyStrategy] Max stable partition topology: CacheTopology{id=25, phase=NO_REBALANCE, rebalanceId=5, currentCH=DefaultConsistentHash > {ns=256, owners = (2)[Test-NodeD: 129+127, Test-NodeE: 127+129]} > , pendingCH=null, unionCH=null, actualMembers=[Test-NodeD, Test-NodeE], persistentUUIDs=[099401f9-c0b6-460d-8dc8-5051699e8287, 72b17309-62d1-4928-abf6-88a8606ef342]} > 19:48:14,690 TRACE (non-blocking-thread-Test-NodeE-p9541-t5:[Merge-8]) [PreferConsistencyStrategy] Max active partition topology: CacheTopology{id=27, phase=NO_REBALANCE, rebalanceId=5, currentCH=DefaultConsistentHash > {ns=256, owners = (1)[Test-NodeE: 256+0]} > , pendingCH=null, unionCH=null, actualMembers=[Test-NodeE], persistentUUIDs=[72b17309-62d1-4928-abf6-88a8606ef342]} > 19:48:14,690 DEBUG (non-blocking-thread-Test-NodeE-p9541-t3:[]) [LocalTopologyManagerImpl] Ignoring topology 27 for cache testCache from old coordinator Test-NodeD > {code} > The old coordinator (NodeD) sent the topology update and the stable topology update, and NodeE received both. However NodeE might ignores the stable topology update because it was processed after it got the new cluster view, with itself as the coordinator. The proper fix is to get rid of the StableTopologyUpdateCommand and add a stable=true/false field in CacheTopology or in TopologyUpdateCommand. > There's still a small chance that the coordinator will shut down before sending the topology update command to any of the other nodes, but it's a small chance. It's much more likely that a separate stable topology update command will be ignored because it is queued by LocalTopologyManagerImpl after the regular topology update command, and the regular topology update has a lot of processing to do in StateConsumerImpl. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11629) Initialize DataConversion storage media type only once

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11629?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11629: ----------------------------------- Fix Version/s: 11.0.0.CR1 (was: 11.0.0.Dev05) > Initialize DataConversion storage media type only once > ------------------------------------------------------ > > Key: ISPN-11629 > URL: https://issues.redhat.com/browse/ISPN-11629 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 11.0.0.Dev03 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 11.0.0.CR1 > > > {{DataConversion}} constructors have a {{storageMediaType}} parameter, but then the storage media type is overridden in {{injectDependencies()}}, except for the static instances defined as constants in {{DataConversion}}. > {{InternalCacheFactory}} can also be simplified to only use the {{DataConversion}} s to create the {{EncoderCache}}, without passing them to the wrapped cache(s). -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11632) Address comments in ISPN-10457

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11632?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11632: ----------------------------------- Fix Version/s: 11.0.0.CR1 (was: 11.0.0.Dev05) > Address comments in ISPN-10457 > ------------------------------ > > Key: ISPN-11632 > URL: https://issues.redhat.com/browse/ISPN-11632 > Project: Infinispan > Issue Type: Task > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.CR1 > > > There were some late comments in https://github.com/infinispan/infinispan/pull/8096 that we can still address. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 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.CR1 (was: 11.0.0.Dev05) > 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.CR1 > > > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11744) ConnectException for ManagedConnectionOperations

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11744?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11744: ----------------------------------- Fix Version/s: 11.0.0.CR1 (was: 11.0.0.Dev05) > ConnectException for ManagedConnectionOperations > ------------------------------------------------ > > Key: ISPN-11744 > URL: https://issues.redhat.com/browse/ISPN-11744 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 11.0.0.Dev04 > Reporter: Diego Lovison > Assignee: Tristan Tarrant > Priority: Major > Fix For: 11.0.0.CR1 > > > ConnectException for ManagedConnectionOperations in CentOS8 > It is working for CentOS7 > {noformat} > org.infinispan.commons.CacheException: Unable to start cache loaders > org.infinispan.persistence.spi.PersistenceException: ISPN000527: Maximum startup attempts exceeded for store org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStore > org.infinispan.persistence.spi.PersistenceException: This might be related to https://jira.jboss.org/browse/ISPN-604 > org.h2.jdbc.JdbcSQLNonTransientConnectionException: Connection is broken: "java.net.ConnectException: Connection refused (Connection refused): 127.0.0.1:20000" [90067-199] > java.net.ConnectException: Connection refused (Connection refused) > at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:337) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:176) > at org.infinispan.client.hotrod.impl.transport.netty.HeaderDecoder.decode(HeaderDecoder.java:139) > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 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