January 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11108) Move eviction components to impl package

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11108?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-11108: ------------------------------------------ Sprint: DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #38) > Move eviction components to impl package > ---------------------------------------- > > Key: ISPN-11108 > URL: https://issues.redhat.com/browse/ISPN-11108 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 10.1.0.CR1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.1.0.Final > > > {{ActivationManager}} and {{PassivationManager}} are in a public package, probably because they were supposed to be used by custom {{DataContainer}} implementations. We no longer support custom {{DataContainer}} implementations, so we should move them to the impl package. > {{EvictionManager}} is currently accessible through {{AdvancedCache.getEvictionManager()}}, so we can only deprecate it now and remove it in 11.0. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11109) Deprecate and remove usages of state-transfer-executor

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11109?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-11109: ------------------------------------------ Sprint: DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #38) > Deprecate and remove usages of state-transfer-executor > ------------------------------------------------------ > > Key: ISPN-11109 > URL: https://issues.redhat.com/browse/ISPN-11109 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Core > Affects Versions: 10.1.0.CR1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.1.1.Final > > > With ISPN-10310, {{StateConsumerImpl}} applies state asynchronously, so a thread pool specifically for applying state is no longer necessary. > There are some other users remaining, but they can be migrated to the transport executor. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11098) Decommission old infinispan/infinispan-management-console repository

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11098?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-11098: ------------------------------------------ Sprint: DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #38) > Decommission old infinispan/infinispan-management-console repository > -------------------------------------------------------------------- > > Key: ISPN-11098 > URL: https://issues.redhat.com/browse/ISPN-11098 > Project: Infinispan > Issue Type: Task > Components: Console > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Final > > > The old repository is no longer used for upstream development, therefore we should update the master README to point to the new repository. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11113) ScatteredDelayedAvailabilityUpdateTest takes too long

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11113?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-11113: ------------------------------------------ Sprint: DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #38) > ScatteredDelayedAvailabilityUpdateTest takes too long > ----------------------------------------------------- > > Key: ISPN-11113 > URL: https://issues.redhat.com/browse/ISPN-11113 > Project: Infinispan > Issue Type: Bug > Components: Core, Test Suite > Affects Versions: 10.1.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 10.1.2.Final, 11.0.0.Final > > > Partition handling tests use {{LOCAL_PING.setClusterName()}} with a unique name to disable discovery, otherwise partitions would try to merge while they are supposed to stay separate. > But {{LOCAL_PING}} uses the cluster name on stop to remove the node from the static discovery map. If the test doesn't change the cluster name back, {{LOCAL_PING}} doesn't remove the node, the next test method sees an existing coordinator, and tries to connect to it. When a test has lots of test methods, like {{ScatteredDelayedAvailabilityUpdateTest}}, each test method leaves one more coordinator in the discovery map, and each test method takes longer to start the first method. > {noformat} > 09:08:52,758 DEBUG (testng:[]) [GMS] address=NodeA-30899, cluster=org.infinispan.partitionhandling.ScatteredDelayedAvailabilityUpdateTest[SCATTERED_SYNC, bias=NEVER, DENY_READ_WRITES], physical address=127.0.0.1:51941 > 09:08:52,774 TRACE (testng:[]) [GMS] NodeA-30899: discovery took 0 ms, members: 21 rsps (5 coords) [done] > 09:08:52,774 DEBUG (testng:[]) [GMS] NodeA-30899: found multiple coords: [NodeA-2608, NodeA-5606, NodeA-17288, NodeA-64297, NodeA-48475] > 09:08:52,774 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-5606 > 09:08:54,774 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-5606 timed out (after 2000 ms), on try 0 > 09:08:54,774 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-64297 > 09:08:56,775 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-64297 timed out (after 2000 ms), on try 0 > 09:08:56,775 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-48475 > 09:08:58,775 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-48475 timed out (after 2000 ms), on try 0 > 09:08:58,775 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-17288 > 09:09:00,776 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-17288 timed out (after 2000 ms), on try 0 > 09:09:00,776 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-2608 > 09:09:02,776 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-2608 timed out (after 2000 ms), on try 0 > 09:09:02,776 TRACE (testng:[]) [GMS] NodeA-30899: discovery took 0 ms, members: 21 rsps (5 coords) [done] > 09:09:02,776 DEBUG (testng:[]) [GMS] NodeA-30899: found multiple coords: [NodeA-2608, NodeA-5606, NodeA-17288, NodeA-64297, NodeA-48475] > 09:09:02,776 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-5606 > 09:09:04,776 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-5606 timed out (after 2000 ms), on try 1 > ... > 09:09:12,777 TRACE (testng:[]) [GMS] NodeA-30899: discovery took 0 ms, members: 21 rsps (5 coords) [done] > 09:09:12,778 DEBUG (testng:[]) [GMS] NodeA-30899: found multiple coords: [NodeA-2608, NodeA-5606, NodeA-17288, NodeA-64297, NodeA-48475] > 09:09:12,778 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-2608 > 09:09:14,778 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-2608 timed out (after 2000 ms), on try 2 > ... > 09:09:22,780 WARN (testng:[]) [GMS] NodeA-30899: too many JOIN attempts (3): becoming singleton > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11114) NonTxBackupOwnerBecomingPrimaryOwnerTest takes too long

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11114?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-11114: ------------------------------------------ Sprint: DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #38) > NonTxBackupOwnerBecomingPrimaryOwnerTest takes too long > ------------------------------------------------------- > > Key: ISPN-11114 > URL: https://issues.redhat.com/browse/ISPN-11114 > Project: Infinispan > Issue Type: Bug > Components: Core, Test Suite > Affects Versions: 10.1.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 10.1.2.Final, 11.0.0.Final > > > {{NonTxBackupOwnerBecomingPrimaryOwnerTest}} installs a {{LocalTopologyManagerImpl}} to block topology updates, and never stops blocking. That makes cluster shutdown very slow, as each node leaving triggers a topology updates, and since ISPN-10310 the coordinator doesn't spawn a new thread for the topology update. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11074) Support LDAP Connection configuration

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11074?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-11074: ------------------------------------------ Sprint: DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #38) > Support LDAP Connection configuration > ------------------------------------- > > Key: ISPN-11074 > URL: https://issues.redhat.com/browse/ISPN-11074 > Project: Infinispan > Issue Type: Enhancement > Components: Security, Server > Affects Versions: 10.1.0.CR1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.1.0.Final > > > The LDAP realm should support configuring the LDAP connection properties such as timeouts, pooling and referral. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11073) Simplify token mech client configuration

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11073?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-11073: ------------------------------------------ Sprint: DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #38) > Simplify token mech client configuration > ---------------------------------------- > > Key: ISPN-11073 > URL: https://issues.redhat.com/browse/ISPN-11073 > Project: Infinispan > Issue Type: Enhancement > Components: Hot Rod, Security > Affects Versions: 10.1.0.CR1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.1.0.Final > > > Setting up the OAUTHBEARER mech on the client requires implementing a callback handler with an Elytron-specific CredentialCallback check. We should simplify this by providing both a .token(String) method on the AuthenticationConfigurationBuilder as well as a ready-made TokenCallbackHandler -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11072) Initialization of elytron sasl providers should not be forced in a static initializer

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11072?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-11072: ------------------------------------------ Sprint: DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #38) > Initialization of elytron sasl providers should not be forced in a static initializer > ------------------------------------------------------------------------------------- > > Key: ISPN-11072 > URL: https://issues.redhat.com/browse/ISPN-11072 > Project: Infinispan > Issue Type: Bug > Components: Hot Rod > Affects Versions: 10.1.0.CR1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.1.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11076) ParticipantFailsAfterPrepareTest.testNonOriginatorFailsAfterPrepare random failures

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11076?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-11076: ------------------------------------------ Sprint: DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #38) > ParticipantFailsAfterPrepareTest.testNonOriginatorFailsAfterPrepare random failures > ----------------------------------------------------------------------------------- > > Key: ISPN-11076 > URL: https://issues.redhat.com/browse/ISPN-11076 > Project: Infinispan > Issue Type: Bug > Components: Core, Test Suite > Affects Versions: 10.1.0.CR1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Labels: testsuite_stability > Fix For: 10.1.0.Final > > > The test checks that all locks are released properly after a tx participant is killed, but doesn't consider the fact that {{TxCompletionNotificationCommand}} is invoked asynchronously. > {noformat} > 00:55:29,005 TRACE (testng-Test:[]) [DefaultLockManager] Lock key=MagicKey{745/083A744A/71@Test-NodeA-51773} for owner=GlobalTx:Test-NodeA-51773:9335. timeout=10000 (MILLISECONDS) > 00:55:29,177 TRACE (remote-thread-Test-NodeB-p22871-t2:[]) [DefaultLockManager] Lock key=MagicKey{745/083A744A/71@Test-NodeA-51773} for owner=GlobalTx:Test-NodeA-51773:9335. timeout=10000 (MILLISECONDS) > 00:55:29,178 TRACE (jgroups-8,Test-NodeA-51773:[]) [DefaultLockManager] Release locks for keys=[MagicKey{745/083A744A/71@Test-NodeA-51773}]. owner=GlobalTx:Test-NodeA-51773:9335 > 00:55:29,179 TRACE (testng-Test:[]) [JGroupsTransport] Test-NodeA-51773 sending command to [Test-NodeD-59848, Test-NodeA-51773, Test-NodeB-24298, Test-NodeC-43307]: TxCompletionNotificationCommand{ xid=null, internalId=0, topologyId=18, gtx=GlobalTx:Test-NodeA-51773:9335, cacheName=Test} > 00:55:29,184 TRACE (remote-thread-Test-NodeD-p22929-t2:[]) [DefaultLockManager] Release locks for keys=[]. owner=GlobalTx:Test-NodeA-51773:9335 > 00:55:29,184 TRACE (remote-thread-Test-NodeB-p22871-t2:[]) [DefaultLockManager] Release locks for keys=[MagicKey{745/083A744A/71@Test-NodeA-51773}]. owner=GlobalTx:Test-NodeA-51773:9335 > 00:55:29,186 ERROR (testng-Test:[]) [TestSuiteProgress] Test failed: org.infinispan.tx.ParticipantFailsAfterPrepareTest.testNonOriginatorFailsAfterPrepare > java.lang.AssertionError: expected [0] but found [1] > at org.testng.Assert.fail(Assert.java:96) ~[testng-6.14.3.jar:?] > at org.testng.Assert.failNotEquals(Assert.java:776) ~[testng-6.14.3.jar:?] > at org.testng.Assert.assertEqualsImpl(Assert.java:137) ~[testng-6.14.3.jar:?] > at org.testng.Assert.assertEquals(Assert.java:118) ~[testng-6.14.3.jar:?] > at org.testng.Assert.assertEquals(Assert.java:652) ~[testng-6.14.3.jar:?] > at org.testng.Assert.assertEquals(Assert.java:662) ~[testng-6.14.3.jar:?] > at org.infinispan.tx.ParticipantFailsAfterPrepareTest.testNonOriginatorFailsAfterPrepare(ParticipantFailsAfterPrepareTest.java:90) ~[test-classes/:?] > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11077) TransactionsSpanningReplicatedCachesTest.testReadOnlyTransaction random failures

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11077?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-11077: ------------------------------------------ Sprint: DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #38) > TransactionsSpanningReplicatedCachesTest.testReadOnlyTransaction random failures > -------------------------------------------------------------------------------- > > Key: ISPN-11077 > URL: https://issues.redhat.com/browse/ISPN-11077 > Project: Infinispan > Issue Type: Bug > Components: Core, Test Suite > Affects Versions: 10.1.0.CR1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Labels: testsuite_stability > Fix For: 10.1.0.Final > > > I have only seen it once, with trace logging enabled. > Because the test doesn't wait for the rebalance to finish before starting the transaction, the transaction's topology might be smaller than the current topology, and {{TxDistributionInterceptor}} will send the prepare+commit to all the owners "just in case". > {noformat} > 00:55:24,535 TRACE (testng-Test:[]) [TransactionTable] Created a new local transaction: LocalXaTransaction{xid=null} LocalTransaction{remoteLockedNodes=null, isMarkedForRollback=false, lockedKeys=[], backupKeyLocks=[], topologyId=4, stateTransferFlag=null} org.infinispan.transaction.xa.LocalXaTransaction@23b3 > 00:55:24,539 TRACE (transport-thread-Test-NodeA-p22422-t4:[]) [CacheNotifierImpl] Invoking listener: org.infinispan.transaction.xa.XaTransactionTable@7d35d8bc passing event EventImpl{type=TOPOLOGY_CHANGED, pre=false, cache=Cache 'Test'@Test-NodeA-2639, readConsistentHashAtStart=PartitionerConsistentHash:ReplicatedConsistentHash{ns = 256, owners = (2)[Test-NodeA-2639: 128, Test-NodeB-29221: 128]}, writeConsistentHashAtStart=PartitionerConsistentHash:ReplicatedConsistentHash{ns = 256, owners = (2)[Test-NodeA-2639: 128, Test-NodeB-29221: 128]}, readConsistentHashAtEnd=PartitionerConsistentHash:ReplicatedConsistentHash{ns = 256, owners = (2)[Test-NodeA-2639: 128, Test-NodeB-29221: 128]}, writeConsistentHashAtEnd=PartitionerConsistentHash:ReplicatedConsistentHash{ns = 256, owners = (2)[Test-NodeA-2639: 128, Test-NodeB-29221: 128]}, unionConsistentHash=null, newTopologyId=5} > 00:55:24,540 TRACE (testng-Test:[]) [VersionedDistributionInterceptor] Should invoke remotely? true. hasModifications=false, hasRemoteLocksAcquired=false > 00:55:24,557 ERROR (testng-Test:[]) [TestSuiteProgress] Test failed: org.infinispan.tx.TransactionsSpanningReplicatedCachesTest.testReadOnlyTransaction > java.lang.AssertionError: expected:<6> but was:<4> > at org.testng.AssertJUnit.fail(AssertJUnit.java:59) ~[testng-6.14.3.jar:?] > at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364) ~[testng-6.14.3.jar:?] > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80) ~[testng-6.14.3.jar:?] > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:170) ~[testng-6.14.3.jar:?] > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:177) ~[testng-6.14.3.jar:?] > at org.infinispan.tx.TransactionsSpanningReplicatedCachesTest.testReadOnlyTransaction(TransactionsSpanningReplicatedCachesTest.java:71) ~[test-classes/:?] > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 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 January 2020