January 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11097) Clusters page unable to resolve "host" when utilising clustered standalone servers

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11097?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-11097: ------------------------------------------ Sprint: DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #38) > Clusters page unable to resolve "host" when utilising clustered standalone servers > ---------------------------------------------------------------------------------- > > Key: ISPN-11097 > URL: https://issues.redhat.com/browse/ISPN-11097 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 9.4.17.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 9.4.18.Final > > > The following page cannot be viewed http://localhost:3000/#/server-groups/default/nodes as the dmr call is trying to access the child-resource "host" which does not exist outside of domain mode. Resulting in the following error message: > {code:json} > { > "outcome" : "failed", > "failure-description" : "WFLYCTL0202: No known child type named host", > "rolled-back" : true > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 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)

6 years, 2 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)

6 years, 2 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)

6 years, 2 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)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11101) Purge on JDBC shared stores can cause deadlocks

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11101?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-11101: ------------------------------------------ Sprint: DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #38) > Purge on JDBC shared stores can cause deadlocks > ----------------------------------------------- > > Key: ISPN-11101 > URL: https://issues.redhat.com/browse/ISPN-11101 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 9.4.17.Final, 10.1.0.CR1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.1.0.Final, 9.4.18.Final > > > ISPN-10337 ensured that the JdbcStringBasedStore correctly acquired the locks of expired rows during the purging of store entries, however it has exposed an issue with shared stores. When the jdbc store is shared, the coordinator locks the rows of the affected entries and releases them once they have all been removed as part of the purge transaction. However, the call to {{ExpirationManager::handleInStoreExpiration}} also sends a {{RemoveExpiredCommand}} to ensure that entries are removed from memory. This results in a {{java.sql.SQLException: Lock wait timeout exceeded; try restarting transaction}} being thrown by the store's delete method when the purge process is still in progress, because the expired rows are still locked and the purge process cannot complete until the {{RemoveExpiredCommand}} has been executed. > In summary: > # purge locks all the rows > # purge sends a RemoveExpiredCommand and waits for it to complete > # RemoveExpiredCommand tries to remove the row but it can't as it is locked > Solution, send the {{RemoveExpiredCommand}} with the {{SKIP_CACHE_STORE}} flag when a store is shared,so that it only removes entries from memory. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[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)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11075) Server security documentation update

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11075?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-11075: ------------------------------------------ Sprint: DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #38) > Server security documentation update > ------------------------------------ > > Key: ISPN-11075 > URL: https://issues.redhat.com/browse/ISPN-11075 > Project: Infinispan > Issue Type: Task > Components: Documentation, Security, Server > Affects Versions: 10.1.0.CR1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.1.0.Final > > > Server security was significantly changed in 10. The docs must be updated to reflect the changes -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 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)

6 years, 2 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)

6 years, 2 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 January 2020