February 2020 - infinispan-issues

[JBoss JIRA] (ISPN-11386) Use blocking thread pool in Persistent preload

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-11386?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-11386: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Use blocking thread pool in Persistent preload > ---------------------------------------------- > > Key: ISPN-11386 > URL: https://issues.redhat.com/browse/ISPN-11386 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 11.0.0.Alpha2 > > > When preload on a transactional cache, the preload blocks until the transactions is committed. > {noformat} > org.infinispan.commons.CacheException: java.lang.AssertionError: Blocking call! jdk.internal.misc.Unsafe#park on thread Thread[non-blocking-thread-IracMetadataStoreTest-NodeB-p50782-t1,5,main] > at org.infinispan.interceptors.impl.AsyncInterceptorChainImpl.invoke(AsyncInterceptorChainImpl.java:259) ~[classes/:?] > at org.infinispan.transaction.impl.TransactionCoordinator.commitInternal(TransactionCoordinator.java:218) ~[classes/:?] > at org.infinispan.transaction.impl.TransactionCoordinator.commit(TransactionCoordinator.java:162) ~[classes/:?] > at org.infinispan.transaction.xa.XaTransactionTable.commit(XaTransactionTable.java:119) ~[classes/:?] > at org.infinispan.transaction.xa.TransactionXaAdapter.commit(TransactionXaAdapter.java:68) ~[classes/:?] > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelOnePhaseCommit(XAResourceRecord.java:702) ~[narayana-jta-5.9.8.Final.jar:5.9.8.Final (revision: 92f28)] > at com.arjuna.ats.arjuna.coordinator.BasicAction.onePhaseCommit(BasicAction.java:2386) ~[narayana-jta-5.9.8.Final.jar:5.9.8.Final (revision: 92f28)] > at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1497) ~[narayana-jta-5.9.8.Final.jar:5.9.8.Final (revision: 92f28)] > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:96) ~[narayana-jta-5.9.8.Final.jar:5.9.8.Final (revision: 92f28)] > at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:162) ~[narayana-jta-5.9.8.Final.jar:5.9.8.Final (revision: 92f28)] > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1287) ~[narayana-jta-5.9.8.Final.jar:5.9.8.Final (revision: 92f28)] > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126) ~[narayana-jta-5.9.8.Final.jar:5.9.8.Final (revision: 92f28)] > at org.infinispan.persistence.manager.PersistenceManagerImpl.commitIfNeeded(PersistenceManagerImpl.java:1452) ~[classes/:?] > at org.infinispan.persistence.manager.PersistenceManagerImpl.preloadKey(PersistenceManagerImpl.java:1408) ~[classes/:?] > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11241) Deprecate Indexing mode

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11241?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-11241: --------------------------------- Fix Version/s: 11.0.0.Alpha2 > Deprecate Indexing mode > ----------------------- > > Key: ISPN-11241 > URL: https://issues.redhat.com/browse/ISPN-11241 > Project: Infinispan > Issue Type: Bug > Affects Versions: 10.1.1.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 11.0.0.Alpha2, 11.0.0.Final > > > Index.ALL/Index.PRIMARY_OWNER should be automatically detected by Infinispan based on the index manager used by an entity. This configuration is currently at cache level, causing issues such as ISPN-6947 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11241) Deprecate Indexing mode

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11241?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-11241: --------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Merged in master. Thanks [~gustavonalle]! > Deprecate Indexing mode > ----------------------- > > Key: ISPN-11241 > URL: https://issues.redhat.com/browse/ISPN-11241 > Project: Infinispan > Issue Type: Bug > Affects Versions: 10.1.1.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 11.0.0.Final > > > Index.ALL/Index.PRIMARY_OWNER should be automatically detected by Infinispan based on the index manager used by an entity. This configuration is currently at cache level, causing issues such as ISPN-6947 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11396) Requesting a cache that is starting will block

by Will Burns (Jira)

Will Burns created ISPN-11396: --------------------------------- Summary: Requesting a cache that is starting will block Key: ISPN-11396 URL: https://issues.redhat.com/browse/ISPN-11396 Project: Infinispan Issue Type: Sub-task Reporter: Will Burns When a cache is used but is still starting the request must wait for the cache to come up, which is done currently in an await block in the component registry. See https://github.com/infinispan/infinispan/pull/7952#discussion_r385548453 for more information. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11377) Change default flow control protocol back to UFC/MFC

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-11377?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-11377: ------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.4.19.Final Resolution: Done > Change default flow control protocol back to UFC/MFC > ---------------------------------------------------- > > Key: ISPN-11377 > URL: https://issues.redhat.com/browse/ISPN-11377 > Project: Infinispan > Issue Type: Task > Components: Configuration, Core > Affects Versions: 9.4.18.Final, 10.1.2.Final, 11.0.0.Alpha1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.1.4.Final, 11.0.0.Alpha2, 9.4.19.Final > > > The server default configuration started using {{UFC_NB}} and {{MFC_NB}} in order to avoid blocking on the Netty event loop threads, slowing client requests, and then the core default configurations started using {{UFC_NB}} and {{MFC_NB}} as well with ISPN-9886. > Unfortunately the _NB variants aren't really non-blocking: they have an extra queue for messages that require more credits, but that queue is limited (2MB by default), and once the queue is full, they also block. They also have much more complex locking than the blocking variants: we actually had to increase max_credits from 2MB to 3MB in order to get the same performance with {{UFC_NB}} that we had with {{UFC}}. > We're changing the defaults back to {{UFC}} and {{MFC}} while we investigate possible alternatives to avoid blocking. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11280) ConcurrentModificationException in ConditionFuture

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-11280?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-11280: ------------------------------- Fix Version/s: 10.1.4.Final > ConcurrentModificationException in ConditionFuture > -------------------------------------------------- > > Key: ISPN-11280 > URL: https://issues.redhat.com/browse/ISPN-11280 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.1.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.1.4.Final, 11.0.0.Alpha2 > > > {noformat} > java.util.ConcurrentModificationException > at java.base/java.util.IdentityHashMap$IdentityHashMapIterator.remove(IdentityHashMap.java:749) > at java.base/java.util.IdentityHashMap$EntryIterator.remove(IdentityHashMap.java:850) > at org.infinispan.util.concurrent.ConditionFuture.checkConditions(ConditionFuture.java:114) > at org.infinispan.util.concurrent.ConditionFuture.lambda$updateAsync$1(ConditionFuture.java:98) > at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.base/java.lang.Thread.run(Thread.java:834) > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11395) Indexing configuration serialization broken

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-11395?page=com.atlassian.jira.plugi... ] Gustavo Fernandes commented on ISPN-11395: ------------------------------------------ The Widlfly configuration has its own parser, schema, etc which is 99% similar to the core one. With the removal of the WF modules soon, this will be removed > Indexing configuration serialization broken > ------------------------------------------- > > Key: ISPN-11395 > URL: https://issues.redhat.com/browse/ISPN-11395 > Project: Infinispan > Issue Type: Bug > Components: Core, Embedded Querying > Affects Versions: 11.0.0.Alpha1, 10.1.3.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 11.0.0.Beta1 > > > Some elements are not written to XML such as IndexedEntities and keytransformers -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11395) Indexing configuration serialization broken

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-11395?page=com.atlassian.jira.plugi... ] Gustavo Fernandes edited comment on ISPN-11395 at 2/28/20 5:44 AM: ------------------------------------------------------------------- The Widlfly configuration has its own parser, schema, etc which is 99% similar to the core one. With the removal of the WF modules soon, this will be removed and no refactor will be needed was (Author: gustavonalle): The Widlfly configuration has its own parser, schema, etc which is 99% similar to the core one. With the removal of the WF modules soon, this will be removed > Indexing configuration serialization broken > ------------------------------------------- > > Key: ISPN-11395 > URL: https://issues.redhat.com/browse/ISPN-11395 > Project: Infinispan > Issue Type: Bug > Components: Core, Embedded Querying > Affects Versions: 11.0.0.Alpha1, 10.1.3.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 11.0.0.Beta1 > > > Some elements are not written to XML such as IndexedEntities and keytransformers -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11395) Indexing configuration serialization broken

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11395?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-11395: --------------------------------- Fix Version/s: 11.0.0.Beta1 > Indexing configuration serialization broken > ------------------------------------------- > > Key: ISPN-11395 > URL: https://issues.redhat.com/browse/ISPN-11395 > Project: Infinispan > Issue Type: Bug > Components: Core, Embedded Querying > Affects Versions: 11.0.0.Alpha1, 10.1.3.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 11.0.0.Beta1 > > > Some elements are not written to XML such as IndexedEntities and keytransformers -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11395) Indexing configuration serialization broken

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11395?page=com.atlassian.jira.plugi... ] Nistor Adrian commented on ISPN-11395: -------------------------------------- My bad. Seems that when I introduced those configs I've only updated the server side of things, InfinispanSubsystemXMLWriter writes those elements, but Serializer was forgotten. Which makes me wonder why this Serializer - InfinispanSubsystemXMLWriter duplication/duality was ever needed and why we couldn't at least refactor it to a common denominator. > Indexing configuration serialization broken > ------------------------------------------- > > Key: ISPN-11395 > URL: https://issues.redhat.com/browse/ISPN-11395 > Project: Infinispan > Issue Type: Bug > Components: Core, Embedded Querying > Affects Versions: 11.0.0.Alpha1, 10.1.3.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > > Some elements are not written to XML such as IndexedEntities and keytransformers -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2020