[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)
4 years, 7 months
[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)
4 years, 7 months
[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)
4 years, 7 months
[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)
4 years, 7 months
[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)
4 years, 7 months