June 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4065) Refuse to store an index on an ASYNC Cache

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-4065?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-4065: ------------------------------------ Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/5214 > Refuse to store an index on an ASYNC Cache > ------------------------------------------ > > Key: ISPN-4065 > URL: https://issues.jboss.org/browse/ISPN-4065 > Project: Infinispan > Issue Type: Enhancement > Components: Lucene Directory > Affects Versions: 9.1.0.Beta1 > Reporter: Sanne Grinovero > Assignee: Gustavo Fernandes > Priority: Minor > Labels: 64QueryBlockers, hackathon > Fix For: 9.1.0.Final > > > The Infinispan directory requires writing to the 3 caches, and cannot handle out-of-order operations that occur when ASYNC caches are used. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7944) Encoders should not handle null references

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7944?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-7944: ------------------------------------ Description: As {{null}} is not part of the storage, Encoders should not be presented with such references > Encoders should not handle null references > ------------------------------------------ > > Key: ISPN-7944 > URL: https://issues.jboss.org/browse/ISPN-7944 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.1.0.Beta1 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > > As {{null}} is not part of the storage, Encoders should not be presented with such references -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4065) Refuse to store an index on an ASYNC Cache

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-4065?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-4065: ------------------------------------ Fix Version/s: 9.1.0.Final > Refuse to store an index on an ASYNC Cache > ------------------------------------------ > > Key: ISPN-4065 > URL: https://issues.jboss.org/browse/ISPN-4065 > Project: Infinispan > Issue Type: Enhancement > Components: Lucene Directory > Affects Versions: 9.1.0.Beta1 > Reporter: Sanne Grinovero > Assignee: Gustavo Fernandes > Priority: Minor > Labels: 64QueryBlockers, hackathon > Fix For: 9.1.0.Final > > > The Infinispan directory requires writing to the 3 caches, and cannot handle out-of-order operations that occur when ASYNC caches are used. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7944) Encoders should not handle null references

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7944?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-7944: ------------------------------------ Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/5212 > Encoders should not handle null references > ------------------------------------------ > > Key: ISPN-7944 > URL: https://issues.jboss.org/browse/ISPN-7944 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.1.0.Beta1 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7945) Some public query classes are missing from apidocs

by Pedro Zapata (JIRA)

Pedro Zapata created ISPN-7945: ---------------------------------- Summary: Some public query classes are missing from apidocs Key: ISPN-7945 URL: https://issues.jboss.org/browse/ISPN-7945 Project: Infinispan Issue Type: Bug Components: Documentation-Query Affects Versions: 9.0.0.Alpha3 Reporter: Pedro Zapata Assignee: Adrian Nistor Fix For: 8.2.4.Final, 9.0.0.Beta1, 9.0.0.Final In https://docs.jboss.org/infinispan/9.0/apidocs/ we can see classes from infinispan-query module but nothing from query dsl or remote query. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7872) Emit warning when interceptor does not handle functional commands

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7872?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7872: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5167 > Emit warning when interceptor does not handle functional commands > ----------------------------------------------------------------- > > Key: ISPN-7872 > URL: https://issues.jboss.org/browse/ISPN-7872 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 9.0.1.Final > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.1.0.Final > > > Functional commands are omitted in too many interceptors - last time I've noticed that for partition handling. At worst these should be handled with `UnsupportedOperationException`. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7872) Emit checkstyle warning when interceptor does not handle functional commands

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7872?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7872: ------------------------------- Summary: Emit checkstyle warning when interceptor does not handle functional commands (was: Emit warning when interceptor does not handle functional commands) > Emit checkstyle warning when interceptor does not handle functional commands > ---------------------------------------------------------------------------- > > Key: ISPN-7872 > URL: https://issues.jboss.org/browse/ISPN-7872 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 9.0.1.Final > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.1.0.Final > > > Functional commands are omitted in too many interceptors - last time I've noticed that for partition handling. At worst these should be handled with `UnsupportedOperationException`. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7872) Emit checkstyle warning when interceptor does not handle functional commands

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7872?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7872: ------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.1.0.Final Resolution: Done > Emit checkstyle warning when interceptor does not handle functional commands > ---------------------------------------------------------------------------- > > Key: ISPN-7872 > URL: https://issues.jboss.org/browse/ISPN-7872 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 9.0.1.Final > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.1.0.Final > > > Functional commands are omitted in too many interceptors - last time I've noticed that for partition handling. At worst these should be handled with `UnsupportedOperationException`. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7872) Emit warning when interceptor does not handle functional commands

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7872?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7872: ------------------------------- Status: Open (was: New) > Emit warning when interceptor does not handle functional commands > ----------------------------------------------------------------- > > Key: ISPN-7872 > URL: https://issues.jboss.org/browse/ISPN-7872 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 9.0.1.Final > Reporter: Radim Vansa > Assignee: Radim Vansa > > Functional commands are omitted in too many interceptors - last time I've noticed that for partition handling. At worst these should be handled with `UnsupportedOperationException`. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6997) PessimisticTxPartitionAndMergeDuringRuntimeTest.testOriginatorIsolatedPartition random failures

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6997?page=com.atlassian.jira.plugin.... ] Dan Berindei edited comment on ISPN-6997 at 6/19/17 5:55 AM: ------------------------------------------------------------- I started investigating this again when I stumbled across some new failures on the ISPN-6997 branch. My previous comment was only partially correct: the {{LockControlCommand}} is not delivered during the partition, but immediately before (or possibly in parallel) with the view message. The reason is that {{UNICAST3}} connections are not closed immediately when the peer disappears from the view, and messages sent during the partition stay in the connection's send table and may be delivered after the merge. But the caller already got a {{CacheNotFoundResponse}} when the partition view got installed, so it committed the transaction locally with a {{PrepareCommand(1PC)}}. Crucially, the 1PC command is *not* sent to all the nodes that got the {{LockControlCommand}}, but only those that are still in the cluster. So the {{LockControlCommand}} is retransmitted after the merge, but the {{PrepareCommand(1PC)}}/{{RollbackCommand}} isn't, and the remote transaction is only cleaned up after the remote transaction timeout expires (60 seconds by default). Bela added a [method in {{UNICAST3}}|https://issues.jboss.org/browse/JGRP-2194] to manually close a connection to a peer, but I've decided instead to change our code so that the targets of {{RollbackCommand}} and {{PrepareCommand}} include the targets of any previous {{LockControlCommand}}. was (Author: dan.berindei): I started investigating this again when I stumbled across some new failures on the ISPN-6997 branch. My previous comment was only partially correct: the {{LockControlCommand}} is not delivered during the partition, but immediately before (or possibly in parallel) with the view message. The reason is that {{UNICAST3}} connections are not closed immediately when the peer disappears from the view, and messages sent during the partition stay in the connection's send table and may be delivered after the merge. But the caller already got a {{CacheNotFoundResponse}} when the partition view got installed, so it committed the transaction locally with a {{PrepareCommand(1PC)}}. Crucially, the 1PC command is *not* sent to all the nodes that got the {{LockControlCommand}}, but only those that are still in the cluster. So the {{LockControlCommand}} is retransmitted after the merge, but the {{PrepareCommand(1PC)}}/{{RollbackCommand}} isn't, and the remote transaction is only cleaned up after the remote transaction timeout expires (60 seconds by default). Bela added a method in {{UNICAST3}} to manually close a connection to a peer, but I've decided instead to change our code so that the targets of {{RollbackCommand}} and {{PrepareCommand}} include the targets of any previous {{LockControlCommand}}. > PessimisticTxPartitionAndMergeDuringRuntimeTest.testOriginatorIsolatedPartition random failures > ----------------------------------------------------------------------------------------------- > > Key: ISPN-6997 > URL: https://issues.jboss.org/browse/ISPN-6997 > Project: Infinispan > Issue Type: Bug > Components: Core, Test Suite - Core > Affects Versions: 9.0.0.Alpha4 > Reporter: Dan Berindei > Assignee: Dan Berindei > Labels: testsuite_stability > Fix For: 9.1.0.Final > > > The test starts with a cluster of 4 nodes, and splits it in 2 partitions while a transaction is trying to lock a key. After the transaction fails, it checks that the transaction has been cleaned up properly. > On one of the owners, {{transactionTable.cleanupLeaverTransactions}} is being called only before the split and after the merge, never with the list of members during the split. That means it never sees the transaction as an orphan, and doesn't remove it. > {noformat} > 15:16:18,893 TRACE (testng-PTPAMDRT:[]) [PTPAMDRT] Local tx=[], remote tx=[GlobalTx:PTPAMDRT-NodeI-3337:28616], for cache PTPAMDRT-NodeJ-27814 > 15:16:18,893 ERROR (testng-PTPAMDRT:[]) [TestSuiteProgress] Test failed: org.infinispan.partitionhandling.PTPAMDRT.testOriginatorIsolatedPartition > java.lang.AssertionError: There are pending transactions! > at org.testng.AssertJUnit.fail(AssertJUnit.java:59) ~[testng-6.8.8.jar:?] > at org.testng.AssertJUnit.assertTrue(AssertJUnit.java:24) ~[testng-6.8.8.jar:?] > at org.infinispan.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:223) ~[test-classes/:?] > at org.infinispan.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:519) ~[test-classes/:?] > at org.infinispan.test.MultipleCacheManagersTest.assertNoTransactions(MultipleCacheManagersTest.java:794) ~[test-classes/:?] > at org.infinispan.partitionhandling.BaseTxPartitionAndMergeTest.finalAsserts(BaseTxPartitionAndMergeTest.java:96) ~[test-classes/:?] > at org.infinispan.partitionhandling.BasePessimisticTxPartitionAndMergeTest.doTest(BasePessimisticTxPartitionAndMergeTest.java:82) ~[test-classes/:?] > at org.infinispan.partitionhandling.tionAndMergeDuringRuntimeTest.testOriginatorIsolatedPartition(PessimisticTxPartitionAndMergeDuringRuntimeTest.java:33) ~[test-classes/:?] > {noformat} > {{OptimisticTxPartitionAndMergeDuringCommitTest.testPrimaryOwnerIsolatedPartition}} has similar random failures. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 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 June 2017