January 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9786) Update Prometheus JMX agent configuration pattern

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9786?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9786: ---------------------------------- Fix Version/s: 9.4.7.Final (was: 9.4.6.Final) > Update Prometheus JMX agent configuration pattern > ------------------------------------------------- > > Key: ISPN-9786 > URL: https://issues.jboss.org/browse/ISPN-9786 > Project: Infinispan > Issue Type: Enhancement > Components: JMX, reporting and management > Affects Versions: 9.4.3.Final > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Priority: Major > Fix For: 10.0.0.Beta1, 9.4.7.Final > > > The current JMX exporter pattern is not optimal. A better version that we should adopt is provided by Madou Coulibaly at https://github.com/mcouliba/datagrid-prometheus/blob/master/config.yaml -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6162) Drop Query.getResultSize() method

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-6162?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6162: ---------------------------------- Fix Version/s: 9.4.7.Final (was: 9.4.6.Final) > Drop Query.getResultSize() method > --------------------------------- > > Key: ISPN-6162 > URL: https://issues.jboss.org/browse/ISPN-6162 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying, Remote Querying > Reporter: Tristan Tarrant > Assignee: Adrian Nistor > Priority: Major > Fix For: 9.4.7.Final > > > Do we keep org.infinispan.query.dsl.Query.getResultSize? Does it return int or long? Return -1 if actual figure unknown/hard to compute? Result size might be non-trivial for non-indexed or hybrid case and will require full scan even for queries with limit. Deprecate it now, remove in ispn 9. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9792) Add META-INF/licenses.xml to cassandra cache store

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9792?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9792: ---------------------------------- Fix Version/s: 9.4.7.Final (was: 9.4.6.Final) > Add META-INF/licenses.xml to cassandra cache store > -------------------------------------------------- > > Key: ISPN-9792 > URL: https://issues.jboss.org/browse/ISPN-9792 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Affects Versions: 9.4.3.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 9.4.7.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9801) ClusterTopologyManagerImpl hangs when restarting a node with FORK

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9801?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9801: ---------------------------------- Fix Version/s: 9.4.7.Final (was: 9.4.6.Final) > ClusterTopologyManagerImpl hangs when restarting a node with FORK > ----------------------------------------------------------------- > > Key: ISPN-9801 > URL: https://issues.jboss.org/browse/ISPN-9801 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.0.0.Alpha1, 9.4.3.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Beta1, 9.4.7.Final > > > When a server is restarted with `kill -9` or similar, both the old node and the new one can be in the JGroups view for a while. Normally this shouldn't be a problem, but sometimes the new node doesn't receive the {{HeartBeatCommand}} and the coordinator cannot process any new view updates. > {noformat} > 14:29:19,981 INFO (jgroups-12,Test-NodeA:[]) [CLUSTER] ISPN000094: Received new cluster view for channel FORKISPN: [Test-NodeA|4] (5) [Test-NodeA, Test-NodeB, Test-NodeC, Test-NodeD, Test-NodeE] > 14:29:19,982 TRACE (transport-thread-Test-NodeA-p4-t14:[ViewHandling]) [ClusterTopologyManagerImpl] Updating cluster members for all the caches. New list is [Test-NodeA, Test-NodeB, Test-NodeC, Test-NodeD, Test-NodeE] > 14:29:19,982 TRACE (transport-thread-Test-NodeA-p4-t14:[ViewHandling]) [JGroupsTransport] Test-NodeA sending request 9 to all: org.infinispan.topology.HeartBeatCommand@1163beb6 > 14:29:19,986 TRACE (jgroups-6,Test-NodeA:[]) [JGroupsTransport] Test-NodeA received response for request 9 from Test-NodeC: SuccessfulResponse(null) > 14:29:19,987 TRACE (jgroups-9,Test-NodeA:[]) [JGroupsTransport] Test-NodeA received response for request 9 from Test-NodeD: SuccessfulResponse(null) > 14:29:20,032 TRACE (jgroups-6,Test-NodeE:[]) [TCP_NIO2] Test-NodeE: received message batch of 1 messages from Test-NodeA > 14:29:20,032 TRACE (jgroups-6,Test-NodeE:[]) [NAKACK2] Test-NodeE: message Test-NodeA::39 was added to queue (not yet server) > 14:29:20,054 TRACE (jgroups-6,Test-NodeE:[]) [NAKACK2] Test-NodeE: received Test-NodeA#38 > 14:29:20,054 TRACE (jgroups-6,Test-NodeE:[]) [NAKACK2] Test-NodeE: delivering Test-NodeA#38 > # not actually delivered :) > 14:29:20,054 TRACE (jgroups-6,Test-NodeE:[]) [MFC] Test-NodeA used 5 credits, 1999995 remaining > 14:29:20,149 INFO (ForkThread-1,ForkChannelRestartTest:[]) [CLUSTER] ISPN000094: Received new cluster view for channel FORKISPN: [Test-NodeA|4] (5) [Test-NodeA, Test-NodeB, Test-NodeC, Test-NodeD, Test-NodeE] > 14:29:21,119 DEBUG (testng-Test-1:[]) [ForkChannelRestartTest] Stopping channel Test-NodeB > 14:29:23,319 INFO (VERIFY_SUSPECT.TimerThread-32,Test-NodeA:[]) [CLUSTER] ISPN000094: Received new cluster view for channel FORKISPN: [Test-NodeA|5] (4) [Test-NodeA, Test-NodeC, Test-NodeD, Test-NodeE] > 14:29:23,320 TRACE (remote-thread-Test-NodeA-p2-t1:[]) [MultiTargetRequest] Target Test-NodeB of request 9 left the cluster view > {noformat} > So far, it looks like it's a JGroups bug similar to JGRP-2294, but we need to investigate further. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6165) Remove Configuration.ssl from HotRod since it is handled by Configuration.security

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-6165?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6165: ---------------------------------- Fix Version/s: 9.4.7.Final (was: 9.4.6.Final) > Remove Configuration.ssl from HotRod since it is handled by Configuration.security > ---------------------------------------------------------------------------------- > > Key: ISPN-6165 > URL: https://issues.jboss.org/browse/ISPN-6165 > Project: Infinispan > Issue Type: Task > Components: Remote Protocols > Reporter: Tristan Tarrant > Assignee: Galder Zamarreño > Priority: Major > Fix For: 9.4.7.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9886) Use UFC_NB and MFC_NB in default embedded configurations

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9886?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9886: ---------------------------------- Fix Version/s: 9.4.7.Final (was: 9.4.6.Final) > Use UFC_NB and MFC_NB in default embedded configurations > -------------------------------------------------------- > > Key: ISPN-9886 > URL: https://issues.jboss.org/browse/ISPN-9886 > Project: Infinispan > Issue Type: Task > Components: Configuration > Affects Versions: 10.0.0.Alpha2, 9.4.5.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Beta1, 9.4.7.Final > > > Once properly configured, UFC_NB and MFC_NB are just as fast as their blocking siblings (ISPN-9828). We should use the non-blocking variants everywhere to simplify configuration. > We should include UFC_NB even in the TCP configuration, to prevent async messages from overwhelming the receiver (JGRP-2301). -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9859) Upgrade to Netty 4.1.32.Final and Netty tcnative 2.0.20

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9859?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9859: ---------------------------------- Fix Version/s: 9.4.7.Final (was: 9.4.6.Final) > Upgrade to Netty 4.1.32.Final and Netty tcnative 2.0.20 > ------------------------------------------------------- > > Key: ISPN-9859 > URL: https://issues.jboss.org/browse/ISPN-9859 > Project: Infinispan > Issue Type: Component Upgrade > Components: Hot Rod, REST, Security, Server > Affects Versions: 10.0.0.Alpha2, 9.4.5.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Beta1, 9.4.7.Final > > > In order to fix an NPE with IBM JDK we need to upgrade to Netty 4.1.32.Final and Netty tcnative 2.0.20.Final > https://github.com/netty/netty/issues/8170 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6166) Remove deprecated Near Cache modes

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-6166?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6166: ---------------------------------- Fix Version/s: 9.4.7.Final (was: 9.4.6.Final) > Remove deprecated Near Cache modes > ---------------------------------- > > Key: ISPN-6166 > URL: https://issues.jboss.org/browse/ISPN-6166 > Project: Infinispan > Issue Type: Task > Components: Remote Protocols > Reporter: Tristan Tarrant > Assignee: Galder Zamarreño > Priority: Major > Fix For: 9.4.7.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6167) Remove deprecated ConsistentHash.init() method from the HotRod client

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-6167?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6167: ---------------------------------- Fix Version/s: 9.4.7.Final (was: 9.4.6.Final) > Remove deprecated ConsistentHash.init() method from the HotRod client > --------------------------------------------------------------------- > > Key: ISPN-6167 > URL: https://issues.jboss.org/browse/ISPN-6167 > Project: Infinispan > Issue Type: Task > Components: Remote Protocols > Reporter: Tristan Tarrant > Assignee: Galder Zamarreño > Priority: Major > Fix For: 9.4.7.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9887) Upgrade to JGroups 4.0.16.Final

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9887?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9887: ---------------------------------- Fix Version/s: 9.4.7.Final (was: 9.4.6.Final) > Upgrade to JGroups 4.0.16.Final > ------------------------------- > > Key: ISPN-9887 > URL: https://issues.jboss.org/browse/ISPN-9887 > Project: Infinispan > Issue Type: Component Upgrade > Components: Core > Affects Versions: 10.0.0.Alpha2, 9.4.5.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Beta1, 9.4.7.Final > > > [Release notes|http://belaban.blogspot.com/2019/01/jgroups-4016.html] > The most interesting fix for us is JGRP-2324, which might help with the cluster stability when two nodes leave in rapid succession (although JGRP-2293 is not fixed yet). -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2019