October 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-8324) Cache listener receives CacheEntriesEvictedEvent for entries irrespective of filter

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8324?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8324: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Cache listener receives CacheEntriesEvictedEvent for entries irrespective of filter > ----------------------------------------------------------------------------------- > > Key: ISPN-8324 > URL: https://issues.jboss.org/browse/ISPN-8324 > Project: Infinispan > Issue Type: Bug > Components: Eviction > Affects Versions: 9.1.1.Final > Reporter: Paul Ferraro > Priority: Major > Fix For: 10.0.1.Final > > Attachments: Test.java > > > If a cache registers a listener using a KeyFilter, should not receive CacheEntriesEvictedEvents for entries that do not honor the filter. See attached reproducer. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8356) Embedded distribution names are confusing

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8356?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8356: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Embedded distribution names are confusing > ----------------------------------------- > > Key: ISPN-8356 > URL: https://issues.jboss.org/browse/ISPN-8356 > Project: Infinispan > Issue Type: Enhancement > Components: Build > Affects Versions: 9.1.1.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.1.Final > > > The binary distribution names for embedded libraries are confusing: > I propose the following names > > - infinispan-${version}-all.zip -> infinispan-embedded-${version}-all.zip > - infinispan-${version}-minimal.zip -> infinispan-embedded-${version}-minimal.zip > - infinispan-${version}-remote.zip -> infinispan-remote-${version}.zip > The website labelling needs to be modified accordingly too -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8441) The module spec used by server config of indexed-entities/indexed-entity and modules/module accepts only deployments

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8441?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8441: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > The module spec used by server config of indexed-entities/indexed-entity and modules/module accepts only deployments > -------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-8441 > URL: https://issues.jboss.org/browse/ISPN-8441 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Affects Versions: 9.1.0.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.1.Final > > > The module name must start with "deployment." due to the use ServiceModuleLoader.moduleServiceName() method to resolve a service name from a module name. This only knows how to handle deployments from 'deployment' dir, regular modules from the 'modules' dir are not handled. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8453) Commit should fail if cache is in degraded mode

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8453?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8453: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Commit should fail if cache is in degraded mode > ----------------------------------------------- > > Key: ISPN-8453 > URL: https://issues.jboss.org/browse/ISPN-8453 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.1.9.Final, 8.2.8.Final, 9.1.2.Final, 9.2.0.Alpha2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.1.Final > > > When the originator receives a {{CacheNotFoundResponse}} and the cache is in degraded mode, the transaction is marked as partially completed, but the commit completes successfully. > I believe that is not correct, because the originator could crash after the commit but before the merge, and in that case the transaction will not be applied on all the owners. The transaction manager will ignore any commit exception in {{NON_XA}}/{{useSynchronization}} mode, but at least in {{FULL_XA}}/{{NON_DURABLE_XA}} mode we can signal to the user that the transaction may be lost. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9028) Write-only segments should be invalidated during the READ_NEW phase

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9028?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9028: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Write-only segments should be invalidated during the READ_NEW phase > ------------------------------------------------------------------- > > Key: ISPN-9028 > URL: https://issues.jboss.org/browse/ISPN-9028 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Labels: testsuite_stability > Fix For: 10.0.1.Final > > > When a rebalance removes a segment X from node A, node A keeps updating entries in segment X until the rebalance finishes, and only deletes the entries of segment X after entering the NO_REBALANCE phase. > This is problematic for tests that work with the data container directly, because {{waitForNoRebalance()}} doesn't wait for the removal of stale entries. The test will work without an explicit wait most of the time, so this is a recipe for random test failures (e.g. ISPN-8728). > As described in ISPN-5021, we can prevent any writes to segment X at the start of the READ_NEW_WRITE_ALL phase, send the phase confirmation to the coordinator, and then remove the entries asynchronously. We just need to keep track of the removal task and only install/confirm the NO_REBALANCE phase once all the entries that we don't own have been removed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8625) PostStart methods should be invoked after ModuleLifecyle.cacheManagerStarted

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8625?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8625: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > PostStart methods should be invoked after ModuleLifecyle.cacheManagerStarted > ---------------------------------------------------------------------------- > > Key: ISPN-8625 > URL: https://issues.jboss.org/browse/ISPN-8625 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.2.0.Beta1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.1.Final > > > The PostStart methods should be invoked after the ModuleLifecycle have executed their cacheManagerStarted methods (which might include global component registrations) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9029) Add test for exception eviction dropping entries after node leave

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9029?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9029: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Add test for exception eviction dropping entries after node leave > ----------------------------------------------------------------- > > Key: ISPN-9029 > URL: https://issues.jboss.org/browse/ISPN-9029 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Core > Affects Versions: 9.2.1.Final > Reporter: Dan Berindei > Assignee: Will Burns > Priority: Major > Fix For: 10.0.1.Final > > > {{ExceptionEvictionTest}} tests what happens when a node is added and N*limit existing entries are redistributed among N+1 nodes. We also need to test what happens when a node crashes and N*limit entries are redistributed among N-1 nodes. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8622) PessimisticStateTransferLocksTest.testPutStartedDuringRebalance random failure

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8622?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8622: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > PessimisticStateTransferLocksTest.testPutStartedDuringRebalance random failure > ------------------------------------------------------------------------------ > > Key: ISPN-8622 > URL: https://issues.jboss.org/browse/ISPN-8622 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.2.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Labels: testsuite_stability > Fix For: 10.0.1.Final > > > {noformat} > java.lang.AssertionError: expected:<[key]> but was:<[]> > at org.infinispan.distribution.rehash.PessimisticStateTransferLocksTest.checkLocksBeforeCommit(PessimisticStateTransferLocksTest.java:185) > at org.infinispan.distribution.rehash.PessimisticStateTransferLocksTest.testPutStartedDuringRebalance(PessimisticStateTransferLocksTest.java:121) > {noformat} > http://ci.infinispan.org/job/Infinispan/job/master/319 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8892) RestStore should only implement CacheLoader

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8892?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8892: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > RestStore should only implement CacheLoader > ------------------------------------------- > > Key: ISPN-8892 > URL: https://issues.jboss.org/browse/ISPN-8892 > Project: Infinispan > Issue Type: Task > Components: Loaders and Stores > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.0.1.Final > > > The RestStore is redundant since a user could just use the RemoteStore which performs better for pretty much every operation. The only real usage for RestStore is if you wanted to pull data from an existing server and wanted to cache that data. As such we should change RestStore to just implement the CacheLoader interface. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9018) SslTest.testClientAuth random failures

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9018?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9018: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > SslTest.testClientAuth random failures > -------------------------------------- > > Key: ISPN-9018 > URL: https://issues.jboss.org/browse/ISPN-9018 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 9.2.1.Final > Reporter: Dan Berindei > Priority: Major > Labels: testsuite_stability > Fix For: 10.0.1.Final > > > The test fails with a timeout exception. There is probably more, but before ISPN-9017 is fixed gathering logs is too difficult. > {noformat} > 09:34:03,524 DEBUG (testng-Test:[]) [ChannelFactory] Creating new channel pool for 127.0.0.1:12411 > 09:34:09,732 INFO (testng-Test:[]) [RemoteCacheManager] ISPN004021: Infinispan version: null > 09:34:13,823 ERROR (testng-Test:[]) [TestSuiteProgress] Test failed: org.infinispan.client.hotrod.SslTest.testClientAuth > org.infinispan.client.hotrod.exceptions.TransportException: java.net.SocketTimeoutException: FaultTolerantPingOperation{(default), flags=0} timed out after 3000 ms > at org.infinispan.client.hotrod.impl.Util.rewrap(Util.java:50) ~[classes/:?] > at org.infinispan.client.hotrod.impl.Util.await(Util.java:25) ~[classes/:?] > at org.infinispan.client.hotrod.impl.RemoteCacheImpl.ping(RemoteCacheImpl.java:472) ~[classes/:?] > at org.infinispan.client.hotrod.impl.RemoteCacheImpl.resolveCompatibility(RemoteCacheImpl.java:736) ~[classes/:?] > at org.infinispan.client.hotrod.RemoteCacheManager.createRemoteCache(RemoteCacheManager.java:312) ~[classes/:?] > at org.infinispan.client.hotrod.RemoteCacheManager.getCache(RemoteCacheManager.java:201) ~[classes/:?] > at org.infinispan.client.hotrod.RemoteCacheManager.getCache(RemoteCacheManager.java:195) ~[classes/:?] > at org.infinispan.client.hotrod.SslTest.initServerAndClient(SslTest.java:103) ~[test-classes/:?] > at org.infinispan.client.hotrod.SslTest.testClientAuth(SslTest.java:131) ~[test-classes/:?] > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 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 October 2019