November 2018 - infinispan-issues

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

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-8862?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8862: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.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.3.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)

7 years, 8 months

1
0
0 / 0

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

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-8861?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8861: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.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.3.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)

7 years, 8 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 Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-8780?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8780: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.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.3.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)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8772) Update Server Licenses

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-8772?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8772: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Update Server Licenses > ---------------------- > > Key: ISPN-8772 > URL: https://issues.jboss.org/browse/ISPN-8772 > Project: Infinispan > Issue Type: Task > Components: Build > Affects Versions: 9.2.0.CR2 > Reporter: Ryan Emerson > Priority: Major > Fix For: 9.4.3.Final > > > After upgrading the server to wildfly 11, the server license files have become outdated and should be updated. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

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

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-8648?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8648: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.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.3.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)

7 years, 8 months

1
0
0 / 0

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

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-8643?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8643: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.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.3.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)

7 years, 8 months

1
0
0 / 0

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

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-8628?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8628: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.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.3.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)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9112) getCache() should not wait for the initial state transfer by default

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-9112?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9112: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > getCache() should not wait for the initial state transfer by default > -------------------------------------------------------------------- > > Key: ISPN-9112 > URL: https://issues.jboss.org/browse/ISPN-9112 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Core > Affects Versions: 9.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 9.4.3.Final > > > {{DefaultCacheManager.getCache(name)}} normally blocks until the local node becomes a full member of the consistent hash and the rebalance has finished. This can cause problems when rebalancing is disabled, either explicitly by the administrator, or implicitly because the cache is in degraded mode. > Blocking can be disabled with {{builder.clustering().stateTransfer().awaitInitialTransfer(false)}} ({{await-initial-transfer="false"}} in XML}}, but we should make the non-blocking behaviour the default. We should also deprecate the method and attribute to enable the blocking behaviour, and instead add a method to {{AdvancedCache}} to wait for the initial state transfer. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9101) EncryptProtocolIT.testEncryptProtocolRegistered random failures

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-9101?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9101: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > EncryptProtocolIT.testEncryptProtocolRegistered random failures > --------------------------------------------------------------- > > Key: ISPN-9101 > URL: https://issues.jboss.org/browse/ISPN-9101 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 9.2.1.Final > Reporter: Dan Berindei > Priority: Critical > Labels: testsuite_stability > Fix For: 9.4.3.Final > > > {noformat} > java.lang.RuntimeException: Could not retrieve HotRod host > at org.infinispan.server.test.security.jgroups.encrypt.EncryptProtocolIT.testEncryptProtocolRegistered(EncryptProtocolIT.java:63) > Caused by: java.lang.IllegalArgumentException: Could not retrieve attribute HostName on MBean jboss.datagrid-infinispan:type=Server,name=HotRod,component=Transport > at org.infinispan.server.test.security.jgroups.encrypt.EncryptProtocolIT.testEncryptProtocolRegistered(EncryptProtocolIT.java:63) > Caused by: javax.management.InstanceNotFoundException: jboss.datagrid-infinispan:type=Server,name=HotRod,component=Transport > {noformat} > The log shows this exception: > {noformat} > &amp#27;[0m&amp#27;[31m13:36:29,258 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.datagrid-jgroups.channel.cluster: org.jboss.msc.service.StartException in service jboss.datagrid-jgroups.channel.cluster: java.security.PrivilegedActionException: java.io.IOException: Invalid secret key format > at org.infinispan.server.jgroups.spi.service.ChannelBuilder.start(ChannelBuilder.java:79) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.security.PrivilegedActionException: java.io.IOException: Invalid secret key format > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:623) > at org.infinispan.server.jgroups.JChannelFactory.createChannel(JChannelFactory.java:104) > at org.infinispan.server.jgroups.spi.service.ChannelBuilder.start(ChannelBuilder.java:77) > ... 8 more > Caused by: java.io.IOException: Invalid secret key format > at com.sun.crypto.provider.JceKeyStore.engineLoad(JceKeyStore.java:856) > at java.security.KeyStore.load(KeyStore.java:1445) > at org.jgroups.protocols.SYM_ENCRYPT.readSecretKeyFromKeystore(SYM_ENCRYPT.java:97) > at org.jgroups.protocols.SYM_ENCRYPT.init(SYM_ENCRYPT.java:78) > at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:840) > at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:479) > at org.jgroups.JChannel.init(JChannel.java:992) > at org.jgroups.JChannel.<init>(JChannel.java:148) > at org.infinispan.server.jgroups.JChannelFactory.lambda$createChannel$0(JChannelFactory.java:103) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:619) > ... 10 more > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9079) Cache operations during Conflict Resolution phase should force CR on that key

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-9079?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9079: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Cache operations during Conflict Resolution phase should force CR on that key > ----------------------------------------------------------------------------- > > Key: ISPN-9079 > URL: https://issues.jboss.org/browse/ISPN-9079 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 9.2.1.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 9.4.3.Final > > > During a partition merge conflict resolution can take a long time when there are many entries, therefore if a user initiates an operation on a key during this phase, it should force CR to occur on the key before executing the operation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 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 November 2018