May 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11841) Listener leaking and produce OOM error

by Wolf-Dieter Fink (Jira)

[ https://issues.redhat.com/browse/ISPN-11841?page=com.atlassian.jira.plugi... ] Wolf-Dieter Fink updated ISPN-11841: ------------------------------------ Security: (was: Red Hat Internal) > Listener leaking and produce OOM error > -------------------------------------- > > Key: ISPN-11841 > URL: https://issues.redhat.com/browse/ISPN-11841 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 9.4.19.Final > Reporter: Will Burns > Assignee: Will Burns > Priority: Critical > Fix For: 9.4.20.Final > > > Register Listener will end up in a OutOfMemory error because it is never unregistered. > A Listener will be added per client connection and never removed. > Here TransactionRequestProcessor has a bug. > HeapDump analysis will show > {quote} > java.lang.Thread @ 0x760886888 timeout-thread--p3-t1 Native Stack, Thread > '- <Java Local> java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue @ 0x76088ab00 > '- queue java.util.concurrent.RunnableScheduledFuture[24] @ 0x760ec5ef0 > '- [0] java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask @ 0x7617bde40 > '- callable java.util.concurrent.Executors$RunnableAdapter @ 0x7618b76c0 > '- task org.infinispan.transaction.impl.TransactionTable$$Lambda$692 @ 0x7618b76d8 > '- arg$1 org.infinispan.transaction.impl.TransactionTable @ 0x761617028 > '- cacheManagerNotifier org.infinispan.notifications.cachemanagerlistener.CacheManagerNotifierImpl @ 0x760f67878 > '- cacheStoppedListeners java.util.concurrent.CopyOnWriteArrayList @ 0x762068998 > '- array java.lang.Object[647063] @ 0x7951cb888 > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11852) Allow creation of RemoteCacheConfigurations at runtime

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-11852: -------------------------------------- Summary: Allow creation of RemoteCacheConfigurations at runtime Key: ISPN-11852 URL: https://issues.redhat.com/browse/ISPN-11852 Project: Infinispan Issue Type: Enhancement Components: Configuration, Hot Rod Affects Versions: 11.0.0.Dev05 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 11.0.0.CR1 ISPN-11676 added the ability to have per-cache client configurations. It should be possible to add new configurations after a RemoteCacheManager has been started. {code:java} public void remoteCache(String name, Consumer<RemoteCacheConfigurationBuilder> builderConsumer); {code} If the `name` doesn't yet exist, a builder will be created and the `Consumer` invoked to allow configuration, as follows: {code:java} remoteCache("blah", c -> c.nearCacheMode(NearCacheMode.INVALIDATED).templateName(DefaultTemplate.DIST_SYNC)); {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11851) FD_SOCK should use the same bind address as TCP

by Dan Berindei (Jira)

Dan Berindei created ISPN-11851: ----------------------------------- Summary: FD_SOCK should use the same bind address as TCP Key: ISPN-11851 URL: https://issues.redhat.com/browse/ISPN-11851 Project: Infinispan Issue Type: Bug Components: Configuration, Core Affects Versions: 10.1.8.Final, 11.0.0.Dev05 Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 11.0.0.CR1 In the JGroups configuration files we ship, we use a different default for {{TCP.bind_addr}} and {{UDP.bind_addr}} than JGroups does. {code:xml} <TCP bind_addr="${jgroups.bind.address,jgroups.tcp.address:SITE_LOCAL}"/> <UDP bind_addr="${jgroups.bind.address,jgroups.udp.address:SITE_LOCAL}"/> {code} However, we didn't change the default for {{FD_SOCK}}, so it uses the JGroups default: -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11679) Bad uneven segment distributions can happen after the rebalancing with SyncConsistentHashFactory

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11679?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-11679: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8339 > Bad uneven segment distributions can happen after the rebalancing with SyncConsistentHashFactory > ------------------------------------------------------------------------------------------------ > > Key: ISPN-11679 > URL: https://issues.redhat.com/browse/ISPN-11679 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.4.19.Final, 10.1.6.Final > Reporter: Masafumi Miura > Assignee: Dan Berindei > Priority: Major > Fix For: 11.0.0.Final > > > Uneven segment distribution can happen after rebalancing with SyncConsistentHashFactory. > Even if a larger number of segments than "20 * number of nodes" is configured, some nodes have only around 50-60% number of segments than other nodes after the rebalance in the worst case. > I understand the documentation (like the following) states about the possibility of slight uneven distribution as a potential drawback of SyncConsistentHashFactory. > [Infinispan 10 configuration guide|https://infinispan.org/docs/stable/titles/configuring/configuring.h...] says: > {quote} > This implementation does have some negative points in that the load distribution is slightly uneven. It also moves more segments than strictly necessary on a join or leave. > {quote} > [JDG 7 Developer Guide|https://access.redhat.com/documentation/en-us/red_hat_data_grid/7.2...] says: > {quote} > It has a potential drawback in that it can move a greater number of segments than necessary during re-balancing. This can be mitigated by using a larger number of segments. > Another potential drawback is that the segments are not distributed as evenly as possible, and actually using a very large number of segments can make the distribution of segments worse. > {quote} > However, only half segments than others is not a slight uneven. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11837) ContainerInfinispanServerDriver missing cluster size check

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-11837?page=com.atlassian.jira.plugi... ] Ryan Emerson updated ISPN-11837: -------------------------------- Status: Open (was: New) > ContainerInfinispanServerDriver missing cluster size check > ---------------------------------------------------------- > > Key: ISPN-11837 > URL: https://issues.redhat.com/browse/ISPN-11837 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Affects Versions: 11.0.0.Dev05 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 11.0.0.CR1 > > > The tests in {{server/tests}} that are executed in CONTAINER mode do not currently check to ensure that a cluster of {{InfinispanServerTestConfiguration#numServers}} is formed before the tests begin. This means that it's possible for some of the {{ClusteredIT}} tests to pass even if no cluster is formed between the containers. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11837) ContainerInfinispanServerDriver missing cluster size check

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-11837?page=com.atlassian.jira.plugi... ] Ryan Emerson updated ISPN-11837: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8324 > ContainerInfinispanServerDriver missing cluster size check > ---------------------------------------------------------- > > Key: ISPN-11837 > URL: https://issues.redhat.com/browse/ISPN-11837 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Affects Versions: 11.0.0.Dev05 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 11.0.0.CR1 > > > The tests in {{server/tests}} that are executed in CONTAINER mode do not currently check to ensure that a cluster of {{InfinispanServerTestConfiguration#numServers}} is formed before the tests begin. This means that it's possible for some of the {{ClusteredIT}} tests to pass even if no cluster is formed between the containers. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11849) ParamKeyValueFilterConverterFactory missing from Server Extensions

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-11849?page=com.atlassian.jira.plugi... ] Ryan Emerson updated ISPN-11849: -------------------------------- Status: Open (was: New) > ParamKeyValueFilterConverterFactory missing from Server Extensions > ------------------------------------------------------------------ > > Key: ISPN-11849 > URL: https://issues.redhat.com/browse/ISPN-11849 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 11.0.0.Dev05 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 11.0.0.CR1 > > > Currently the {{Extensions}} class is missing a lookup for {{ParamKeyValueFilterConverterFactory}} service implementations, which means that the {{iteration-filter-converter-factory}} is never available in the server. > The {{HotRodCacheQueries}} tests currently pass with the embedded driver as the services are on the classpath of the server, however if the tests are executed in CONTAINER mode they will fail. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11849) ParamKeyValueFilterConverterFactory missing from Server Extensions

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-11849?page=com.atlassian.jira.plugi... ] Ryan Emerson updated ISPN-11849: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8324 > ParamKeyValueFilterConverterFactory missing from Server Extensions > ------------------------------------------------------------------ > > Key: ISPN-11849 > URL: https://issues.redhat.com/browse/ISPN-11849 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 11.0.0.Dev05 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 11.0.0.CR1 > > > Currently the {{Extensions}} class is missing a lookup for {{ParamKeyValueFilterConverterFactory}} service implementations, which means that the {{iteration-filter-converter-factory}} is never available in the server. > The {{HotRodCacheQueries}} tests currently pass with the embedded driver as the services are on the classpath of the server, however if the tests are executed in CONTAINER mode they will fail. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11850) Only a subset of server tests work with driver=CONTAINER

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-11850?page=com.atlassian.jira.plugi... ] Ryan Emerson updated ISPN-11850: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8324 > Only a subset of server tests work with driver=CONTAINER > -------------------------------------------------------- > > Key: ISPN-11850 > URL: https://issues.redhat.com/browse/ISPN-11850 > Project: Infinispan > Issue Type: Bug > Components: Server, Test Suite > Affects Versions: 11.0.0.Dev05 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 11.0.0.CR1 > > > Several of the {{server/tests}} are not executed when the container driver is set, i.e.{{-Dorg.infinispan.test.server.driver=CONTAINER}}. Furthermore, many of the tests when executed do not work as expected with this driver. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11850) Only a subset of server tests work with driver=CONTAINER

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-11850?page=com.atlassian.jira.plugi... ] Ryan Emerson updated ISPN-11850: -------------------------------- Status: Open (was: New) > Only a subset of server tests work with driver=CONTAINER > -------------------------------------------------------- > > Key: ISPN-11850 > URL: https://issues.redhat.com/browse/ISPN-11850 > Project: Infinispan > Issue Type: Bug > Components: Server, Test Suite > Affects Versions: 11.0.0.Dev05 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 11.0.0.CR1 > > > Several of the {{server/tests}} are not executed when the container driver is set, i.e.{{-Dorg.infinispan.test.server.driver=CONTAINER}}. Furthermore, many of the tests when executed do not work as expected with this driver. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2020