February 2019 - infinispan-issues

[JBoss JIRA] (ISPN-8628) Simplify QueryEngine handling of Broadcast vs Fetch queries

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8628?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8628: ---------------------------------- Fix Version/s: 9.4.8.Final (was: 9.4.7.Final) > Simplify QueryEngine handling of Broadcast vs Fetch queries > ----------------------------------------------------------- > > Key: ISPN-8628 > URL: https://issues.jboss.org/browse/ISPN-8628 > Project: Infinispan > Issue Type: Task > Reporter: Gustavo Fernandes > Assignee: Adrian Nistor > Priority: Minor > Fix For: 9.4.8.Final > > > [~anistor] commented > The existence of RemoteQueryDefinition and HsQueryRequest seems to be a symptom of misplaced responsibility. It all starts with QueryDefinition.initialize, which IMO should actually be placed inside QueryEngine, not QueryDefinition. Doing that refactoring will remove the need for RemoteQueryDefinition, which now exists just to differentiate between embedded and remote case, but that differentiation can be done inside the query engine itself. Also, HsQueryRequest is just a data holder that carries the return value of QueryEngine.createHsQuery. If QueryDefinition.initialize is moved to QueryEngine we would also not need this anymore. > I did not think about it in detail but maybe we would also need to make QueryDefinition mutable for QueryEngine and immutable for external parties. In that case we can extract QueryDefinition as an immutable interface (exposing getters only) and it's implementation class could have package local setters accessible to QueryEngine only. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8643) ClientConnectionPoolingTest.testMaxActiveReached random failures

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8643?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8643: ---------------------------------- Fix Version/s: 9.4.8.Final (was: 9.4.7.Final) > ClientConnectionPoolingTest.testMaxActiveReached random failures > ---------------------------------------------------------------- > > Key: ISPN-8643 > URL: https://issues.jboss.org/browse/ISPN-8643 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 9.2.0.Beta2 > Reporter: Dan Berindei > Priority: Major > Labels: testsuite_stability > Fix For: 9.4.8.Final > > > Looks like waiting for 1s for all the connections to be releases is not enough: > {noformat} > java.lang.AssertionError: > at org.infinispan.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:229) > at org.infinispan.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:211) > at org.infinispan.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:187) > at org.infinispan.client.hotrod.ClientConnectionPoolingTest.testMaxActiveReached(ClientConnectionPoolingTest.java:208) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > {noformat} > http://ci.infinispan.org/job/Infinispan/job/master/336 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8890) TransactionXaAdapter does not implement Geronimo's NamedXaResource

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8890?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8890: ---------------------------------- Fix Version/s: 9.4.8.Final (was: 9.4.7.Final) > TransactionXaAdapter does not implement Geronimo's NamedXaResource > ------------------------------------------------------------------ > > Key: ISPN-8890 > URL: https://issues.jboss.org/browse/ISPN-8890 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.2.0.CR2 > Reporter: Dan Berindei > Priority: Major > Fix For: 9.4.8.Final > > > Geronimo uses its own interface for logging transaction resources, {{NamedXAResource}}. Our {{TransactionXaAdapter}} doesn't implement it, so this error is logged for each transaction in Karaf: > {noformat} > 2018-02-28T09:49:05,931 | ERROR | testng-TransactionsSpanningReplicatedCachesTest-9 | Transaction | 68 - org.apache.aries.transaction.manager - 1.3.3 | Please correct the integration and supply a NamedXAResource > java.lang.IllegalStateException: Cannot log transactions as TransactionXaAdapter{localTransaction=LocalXaTransaction{xid=[Xid:globalId=ffffff96ffffff9561ffffffdb611006f72672e6170616368652e61726965732e7472616e73616374696f6e0000000000000000000000000000,length=64,branchId=1000ffffff84ffffff9561ffffffdb611006170616368652e61726965732e7472616e73616374696f6e0000000000000000000000000000,length=64]} LocalTransaction{remoteLockedNodes=[TransactionsSpanningReplicatedCachesTest-NodeS-28818, TransactionsSpanningReplicatedCachesTest-NodeT-4724], isMarkedForRollback=false, lockedKeys=[], backupKeyLocks=[a], topologyId=5, stateTransferFlag=null} org.infinispan.transaction.xa.LocalXaTransaction@1f} is not a NamedXAResource. > at org.apache.geronimo.transaction.manager.TransactionImpl$TransactionBranch.getResourceName(TransactionImpl.java:781) ~[?:?] > at org.apache.geronimo.transaction.log.HOWLLog.prepare(HOWLLog.java:287) ~[?:?] > at org.apache.geronimo.transaction.manager.TransactionImpl.internalPrepare(TransactionImpl.java:467) ~[?:?] > at org.apache.geronimo.transaction.manager.TransactionImpl.commit(TransactionImpl.java:312) ~[?:?] > at org.apache.geronimo.transaction.manager.TransactionManagerImpl.commit(TransactionManagerImpl.java:252) ~[?:?] > at Proxy325c2276_ef50_4396_9e7d_5deaa002f72c.commit(Unknown Source) ~[?:?] > at org.infinispan.tx.TransactionsSpanningReplicatedCachesTest.runTest(TransactionsSpanningReplicatedCachesTest.java:260) ~[?:?] > at org.infinispan.tx.TransactionsSpanningReplicatedCachesTest.testDefaultCacheAndNamedCacheSameNode(TransactionsSpanningReplicatedCachesTest.java:240) ~[?:?] > at org.infinispan.it.osgi.tx.TransactionsSpanningReplicatedCachesTest.testDefaultCacheAndNamedCacheSameNode(TransactionsSpanningReplicatedCachesTest.java:91) ~[?:?] > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8780) WildFly modules no longer provide support for the Lucene Directory Provider for WildFly's Hibernate Search

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8780?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8780: ---------------------------------- Fix Version/s: 9.4.8.Final (was: 9.4.7.Final) > WildFly modules no longer provide support for the Lucene Directory Provider for WildFly's Hibernate Search > ---------------------------------------------------------------------------------------------------------- > > Key: ISPN-8780 > URL: https://issues.jboss.org/browse/ISPN-8780 > Project: Infinispan > Issue Type: Bug > Components: Build > Reporter: Sanne Grinovero > Priority: Blocker > Fix For: 9.4.8.Final > > > The structure of the modules has been "reorganized" but while doing so the strict separation of the modules meant to support the Hibernate Search version of WildFly - separate from the one included in Infinispan - has been confused. > I consider this a critical regression as we have many users relying on this feature. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8648) Support protobuf encoding as a storage format for embedded query

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8648?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8648: ---------------------------------- Fix Version/s: 9.4.8.Final (was: 9.4.7.Final) > Support protobuf encoding as a storage format for embedded query > ---------------------------------------------------------------- > > Key: ISPN-8648 > URL: https://issues.jboss.org/browse/ISPN-8648 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Major > Fix For: 9.4.8.Final > > > This use case is alreay supported in remote mode and should also be supported in embedded mode. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8862) Iteration and stream operations with passivation disabled shouldn't use in memory

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8862?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8862: ---------------------------------- Fix Version/s: 9.4.8.Final (was: 9.4.7.Final) > Iteration and stream operations with passivation disabled shouldn't use in memory > --------------------------------------------------------------------------------- > > Key: ISPN-8862 > URL: https://issues.jboss.org/browse/ISPN-8862 > Project: Infinispan > Issue Type: Enhancement > Reporter: William Burns > Assignee: William Burns > Priority: Major > Fix For: 9.4.8.Final > > > When passivation is disabled all entries are assumed to be in the cache loader/store. We currently try to merge these together in a sloppy way [1]. This first reads in memory and then from the store and keeps all keys from in memory to exclude them from the store. Unfortunately the store still has to pull the entries even for the already read keys, but just ignores them. This leads to a lot of inefficiency and memory bloat. Instead we should just return the store entries as is when passivation is disabled. > [1] https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8861) DIST Iteration shouldn't go remote when a shared cache store is present

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8861?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8861: ---------------------------------- Fix Version/s: 9.4.8.Final (was: 9.4.7.Final) > DIST Iteration shouldn't go remote when a shared cache store is present > ----------------------------------------------------------------------- > > Key: ISPN-8861 > URL: https://issues.jboss.org/browse/ISPN-8861 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: William Burns > Assignee: William Burns > Priority: Major > Fix For: 9.4.8.Final > > > When a user runs a distributed iteration operation with a shared cache store, this shouldn't go remote as the local node would have all the data available to it. This is similar to the optimization when we don't go remote if the current node is an owner for all required segments. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 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: 9.4.8.Final (was: 9.4.7.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: William Burns > Priority: Major > Fix For: 9.4.8.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.12.1#712002)

5 years, 11 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: 9.4.8.Final (was: 9.4.7.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: 9.4.8.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.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9017) HotRod client thread names should include the test name

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9017?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9017: ---------------------------------- Fix Version/s: 9.4.8.Final (was: 9.4.7.Final) > HotRod client thread names should include the test name > ------------------------------------------------------- > > Key: ISPN-9017 > URL: https://issues.jboss.org/browse/ISPN-9017 > Project: Infinispan > Issue Type: Task > Components: Hot Rod, Test Suite - Server > Affects Versions: 9.2.1.Final > Reporter: Dan Berindei > Assignee: Radim Vansa > Priority: Minor > Fix For: 9.4.8.Final > > > I wanted to obtain a trace log for a {{SslTest}} failure I'm seeing locally, but when I filter by test name all I get is this: > {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.12.1#712002)

5 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2019