February 2017 - infinispan-issues

[JBoss JIRA] (ISPN-7511) Unexpected Store warnings in the testsuite

by Ryan Emerson (JIRA)

Ryan Emerson created ISPN-7511: ---------------------------------- Summary: Unexpected Store warnings in the testsuite Key: ISPN-7511 URL: https://issues.jboss.org/browse/ISPN-7511 Project: Infinispan Issue Type: Bug Components: Test Suite - Core, Test Suite - Server Affects Versions: 9.0.0.CR1 Reporter: Ryan Emerson Assignee: Ryan Emerson -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7484) Upgrade to Apache Lucene 5.5.4

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7484?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-7484: ------------------------------------ Git Pull Request: https://github.com/infinispan/infinispan/pull/4866, https://github.com/infinispan/infinispan/pull/4882 (was: https://github.com/infinispan/infinispan/pull/4866) > Upgrade to Apache Lucene 5.5.4 > ------------------------------ > > Key: ISPN-7484 > URL: https://issues.jboss.org/browse/ISPN-7484 > Project: Infinispan > Issue Type: Component Upgrade > Components: Embedded Querying, Lucene Directory > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 9.0.0.CR2 > > > Various improvements in Lucene, not least the Java 9 compatibility was backported: > - https://lucene.apache.org/core/5_5_4/changes/Changes.html > Related to https://hibernate.atlassian.net/browse/HSEARCH-2591 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7506) Tests fail after upgrading Lucene version

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7506?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-7506: ------------------------------------ Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/4882 > Tests fail after upgrading Lucene version > ----------------------------------------- > > Key: ISPN-7506 > URL: https://issues.jboss.org/browse/ISPN-7506 > Project: Infinispan > Issue Type: Bug > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > > Upgrading Lucene causes clash with the elasticsearch being used in tests: > {noformat} > org.infinispan.test.integration.as (1) > query.ElasticsearchIndexManagerIT > java.lang.AssertionError: Version must be upgraded to [5.5.4] is still set to [5.5.2] > at org.elasticsearch.Version.(Version.java:316) > at org.infinispan.query.test.elasticsearch.ElasticSearchCluster$TestNode.(ElasticSearchCluster.java:59) > at org.infinispan.query.test.elasticsearch.ElasticSearchCluster$ElasticSearchClusterBuilder.buildNode(ElasticSearchCluster.java:123) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7367) CommandAckCollector Improvements

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7367?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7367: ------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.CR2 Resolution: Done > CommandAckCollector Improvements > -------------------------------- > > Key: ISPN-7367 > URL: https://issues.jboss.org/browse/ISPN-7367 > Project: Infinispan > Issue Type: Enhancement > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 9.0.0.CR2 > > > Changes suggested: > * we can have a single {{CommandAckCollector}} per cache manager, since the {{CommandInvocationId}}s are unique. > * It doesn't need the complete {{CommandInvocationId}}. Only the {{long id}} is needed. > Result: > * Smaller payload in acks (no need to send the cache name neither the originator address) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7433) Investigate performance with different xmit_interval values

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7433?page=com.atlassian.jira.plugin.... ] Dan Berindei reopened ISPN-7433: -------------------------------- Looks like the reduced xmit_interval is causing the build to hang and fill the disk with logs: {noformat} 12:04:10,535 DEBUG (testng:[]) [GMS] address=NodeA, cluster=ISPN, physical address=127.0.0.1:8600 12:04:10,574 DEBUG (testng:[]) [GMS] NodeA: installing view [NodeA|0] (1) [NodeA] 12:04:10,648 DEBUG (testng:[]) [GMS] NodeA: created cluster (first member). My view is [NodeA|0], impl is org.jgroups.protocols.pbcast.CoordGmsImpl 12:04:10,730 DEBUG (testng:[]) [GMS] address=NodeB, cluster=ISPN, physical address=127.0.0.1:8601 12:04:10,750 DEBUG (testng:[]) [GMS] NodeB: sending JOIN(NodeB) to NodeA 12:04:12,757 WARN (testng:[]) [GMS] NodeB: JOIN(NodeB) sent to NodeA timed out (after 2000 ms), on try 1 12:04:12,757 DEBUG (testng:[]) [GMS] NodeB: sending JOIN(NodeB) to NodeA 12:04:13,536 DEBUG (testng:[]) [GMS] NodeB: installing view [NodeA|1] (2) [NodeA, NodeB] 12:04:14,071 WARN (jgroups-5,NodeB:[]) [GMS] NodeB: failed to create view from delta-view; dropping view: java.lang.IllegalStateException: the view-id of the delta view ([NodeA|0]) doesn't match the current view-id ([NodeA|1]); discarding delta view [NodeA|2], ref-view=[NodeA|0], joined=[NodeB] 12:04:14,071 DEBUG (jgroups-6,NodeA:[]) [GMS] NodeA: installing view [NodeA|1] (2) [NodeA, NodeB] 12:04:14,104 INFO (jgroups-6,NodeA:[]) [JGroupsTransport] ISPN000094: Received new cluster view for channel ISPN: [NodeA|1] (2) [NodeA, NodeB] 12:04:14,117 WARN (jgroups-6,NodeA:[]) [GMS] NodeA: failed to create view from delta-view; dropping view: java.lang.IllegalStateException: the view-id of the delta view ([NodeA|0]) doesn't match the current view-id ([NodeA|1]); discarding delta view [NodeA|2], ref-view=[NodeA|0], joined=[NodeB] 12:04:14,117 DEBUG (jgroups-5,NodeB:[]) [GMS] NodeB: installing view [NodeA|2] (2) [NodeA, NodeB] 12:04:14,127 INFO (jgroups-5,NodeB:[]) [JGroupsTransport] ISPN000094: Received new cluster view for channel ISPN: [NodeA|2] (2) [NodeA, NodeB] 12:04:15,028 DEBUG (testng:[]) [GMS] address=NodeC-45584, cluster=ISPN, physical address=127.0.0.1:8602 12:04:15,030 DEBUG (testng:[]) [GMS] NodeC-45584: sending JOIN(NodeC-45584) to NodeA 12:04:16,117 DEBUG (jgroups-5,NodeA:[]) [GMS] NodeA: installing view [NodeA|3] (3) [NodeA, NodeB, NodeC-45584] 12:04:16,117 WARN (jgroups-6,NodeB:[]) [GMS] NodeB: failed to create view from delta-view; dropping view: java.lang.IllegalStateException: the view-id of the delta view ([NodeA|1]) doesn't match the current view-id ([NodeA|2]); discarding delta view [NodeA|3], ref-view=[NodeA|1], joined=[NodeC-45584] 12:04:16,346 INFO (jgroups-5,NodeA:[]) [JGroupsTransport] ISPN000094: Received new cluster view for channel ISPN: [NodeA|3] (3) [NodeA, NodeB, NodeC-45584] 12:04:17,032 WARN (testng:[]) [GMS] NodeC-45584: JOIN(NodeC-45584) sent to NodeA timed out (after 2000 ms), on try 1 12:04:17,032 DEBUG (testng:[]) [GMS] NodeC-45584: sending JOIN(NodeC-45584) to NodeA 12:04:18,117 DEBUG (testng:[]) [GMS] NodeC-45584: installing view [NodeA|3] (3) [NodeA, NodeB, NodeC-45584] 12:04:18,461 INFO (testng:[]) [JGroupsTransport] ISPN000094: Received new cluster view for channel ISPN: [NodeA|3] (3) [NodeA, NodeB, NodeC-45584] 12:04:19,427 INFO (testng:[]) [TestSuiteProgress] Test starting: org.infinispan.persistence.ClusteredConditionalCommandPassivationTest.testPutIfAbsentOnBackupOwner[tx=false] 12:04:19,441 DEBUG (testng:[]) [LocalTopologyManagerImpl] Node NodeB joining cache private-store-cache 12:04:19,540 DEBUG (remote-thread-NodeA-p42415-t6:[]) [ClusterTopologyManagerImpl] Ignoring join request from NodeB for cache private-store-cache, joiner's view id is too old: 2 12:04:19,540 DEBUG (testng:[]) [LocalTopologyManagerImpl] Ignoring null join response, coordinator is probably shutting down ... 12:04:25,956 DEBUG (remote-thread-ClusteredConditionalCommandPassivationTest[tx=false]-NodeA-p42415-t6:[]) [ClusterTopologyManagerImpl] Ignoring join request from ClusteredConditionalCommandPassivationTest[tx=false]-NodeB-60608 for cache private-store-cache, joiner's view id is too old: 2 12:04:25,956 DEBUG (testng-ClusteredConditionalCommandPassivationTest[tx=false]:[]) [LocalTopologyManagerImpl] Ignoring null join response, coordinator is probably shutting down 12:04:25,956 DEBUG (remote-thread-ClusteredConditionalCommandPassivationTest[tx=false]-NodeA-p42415-t6:[]) [ClusterTopologyManagerImpl] Ignoring join request from ClusteredConditionalCommandPassivationTest[tx=false]-NodeB-60608 for cache private-store-cache, joiner's view id is too old: 2 12:04:25,956 DEBUG (testng-ClusteredConditionalCommandPassivationTest[tx=false]:[]) [LocalTopologyManagerImpl] Ignoring null join response, coordinator is probably shutting down 12:04:25,956 DEBUG (remote-thread-ClusteredConditionalCommandPassivationTest[tx=false]-NodeA-p42415-t6:[]) [ClusterTopologyManagerImpl] Ignoring join request from ClusteredConditionalCommandPassivationTest[tx=false]-NodeB-60608 for cache private-store-cache, joiner's view id is too old: 2 12:04:25,956 DEBUG (testng-ClusteredConditionalCommandPassivationTest[tx=false]:[]) [LocalTopologyManagerImpl] Ignoring null join response, coordinator is probably shutting down {noformat} > Investigate performance with different xmit_interval values > ----------------------------------------------------------- > > Key: ISPN-7433 > URL: https://issues.jboss.org/browse/ISPN-7433 > Project: Infinispan > Issue Type: Task > Components: Configuration, Core > Affects Versions: 9.0.0.Beta2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Labels: performance > Fix For: 9.0.0.CR2 > > > The default {{UNICAST3.xmit_interval}} is 500ms, and the default {{NAKACK2.xmit_interval}} is 1000ms. According to Bela, a {{xmit_interval}} of 100ms should be much better for performance. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7510) Upgrade to protostream-4.0.0.Alpha7

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-7510?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-7510: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4881 > Upgrade to protostream-4.0.0.Alpha7 > ----------------------------------- > > Key: ISPN-7510 > URL: https://issues.jboss.org/browse/ISPN-7510 > Project: Infinispan > Issue Type: Component Upgrade > Components: Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.CR2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7469) Administration console - some elements have the same IDs

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7469?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic reassigned ISPN-7469: ----------------------------------------- Assignee: Ryan Emerson > Administration console - some elements have the same IDs > -------------------------------------------------------- > > Key: ISPN-7469 > URL: https://issues.jboss.org/browse/ISPN-7469 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.CR1 > Reporter: Roman Macor > Assignee: Ryan Emerson > > Some elements have the same IDs. > Steps to reproduce: > Click on cache container -> cache -> configuration -> store -> select String keyed JDBC store -> click on String keyed table -> several input elements have the same ID -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7510) Upgrade to protostream-4.0.0.Alpha7

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-7510: ----------------------------------- Summary: Upgrade to protostream-4.0.0.Alpha7 Key: ISPN-7510 URL: https://issues.jboss.org/browse/ISPN-7510 Project: Infinispan Issue Type: Component Upgrade Components: Remote Querying Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 9.0.0.CR2 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7510) Upgrade to protostream-4.0.0.Alpha7

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-7510?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-7510: -------------------------------- Status: Open (was: New) > Upgrade to protostream-4.0.0.Alpha7 > ----------------------------------- > > Key: ISPN-7510 > URL: https://issues.jboss.org/browse/ISPN-7510 > Project: Infinispan > Issue Type: Component Upgrade > Components: Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.CR2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7488) Node tries to register component after stopping

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7488?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-7488: ------------------------------------------- At this point those exceptions are harmless. Perhaps we should think about throwing a checked exception by [AbstractComponentRegistry#wireDependencies|https://github.com/infinispan/... > Node tries to register component after stopping > ----------------------------------------------- > > Key: ISPN-7488 > URL: https://issues.jboss.org/browse/ISPN-7488 > Project: Infinispan > Issue Type: Bug > Components: Cloud Integrations, Core, Server > Affects Versions: 9.0.0.Beta2 > Environment: * OpenShift {{v1.5.0-alpha.2+e4b43ee}} > * Custom Infinispan Server build (based on [these instructions|https://github.com/slaskawi/infinispan-1/tree/custom_image]). SHA1 {{2b0731b21649a88a75ed71d21b9cc06ba365e947}} > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Blocker > > When I was performing [Spring Session and Kubernetes Rolling Update demo|https://bluejeans.com/s/pYKUg/] I encountered a couple of problems. > One of the is this: > {noformat} > [transactions-repository-1-4z05w] 18:09:06,122 WARN [org.infinispan.remoting.inboundhandler.GlobalInboundInvocationHandler] (remote-thread--p2-t5) ISPN000071: Caught exception when handling command CacheTopologyControlCommand{cache=___script_cache, type=REBALANCE_CONFIRM, sender=transactions-repository-1-1f8dx, joinInfo=null, topologyId=9, rebalanceId=0, currentCH=null, pendingCH=null, availabilityMode=null, actualMembers=null, throwable=null, viewId=4}: org.infinispan.commons.CacheConfigurationException: Unable to configure component (type: class org.infinispan.topology.CacheTopologyControlCommand, instance CacheTopologyControlCommand{cache=___script_cache, type=REBALANCE_CONFIRM, sender=transactions-repository-1-1f8dx, joinInfo=null, topologyId=9, rebalanceId=0, currentCH=null, pendingCH=null, availabilityMode=null, actualMembers=null, throwable=null, viewId=4}) > [transactions-repository-1-4z05w] at org.infinispan.factories.AbstractComponentRegistry.wireDependencies(AbstractComponentRegistry.java:152) > [transactions-repository-1-4z05w] at org.infinispan.remoting.inboundhandler.GlobalInboundInvocationHandler$2.run(GlobalInboundInvocationHandler.java:160) > [transactions-repository-1-4z05w] at org.infinispan.util.concurrent.BlockingTaskAwareExecutorServiceImpl$RunnableWrapper.run(BlockingTaskAwareExecutorServiceImpl.java:203) > [transactions-repository-1-4z05w] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [transactions-repository-1-4z05w] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [transactions-repository-1-4z05w] at java.lang.Thread.run(Thread.java:745) > [transactions-repository-1-4z05w] Caused by: org.infinispan.IllegalLifecycleStateException: Trying to register a component after stopping: org.infinispan.topology.LocalTopologyManagerFactory > [transactions-repository-1-4z05w] at org.infinispan.factories.AbstractComponentRegistry.registerComponentInternal(AbstractComponentRegistry.java:185) > [transactions-repository-1-4z05w] at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:172) > [transactions-repository-1-4z05w] at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:168) > [transactions-repository-1-4z05w] at org.infinispan.factories.AbstractComponentRegistry.createComponentFactoryInternal(AbstractComponentRegistry.java:349) > [transactions-repository-1-4z05w] at org.infinispan.factories.AbstractComponentRegistry.getFactory(AbstractComponentRegistry.java:328) > [transactions-repository-1-4z05w] at org.infinispan.factories.AbstractComponentRegistry.getOrCreateComponent(AbstractComponentRegistry.java:294) > [transactions-repository-1-4z05w] at org.infinispan.factories.AbstractComponentRegistry.invokeInjectionMethod(AbstractComponentRegistry.java:247) > [transactions-repository-1-4z05w] at org.infinispan.factories.AbstractComponentRegistry.wireDependencies(AbstractComponentRegistry.java:148) > [transactions-repository-1-4z05w] ... 5 more > {noformat} > Full logs from Rolling Update process might be found here: https://gist.github.com/slaskawi/530241bb695f1f490bcb25eabaf9d676 > Steps to reproduce: > * Start local OpenShift Cluster > * invoke `./init_infrastructure.sh` from https://github.com/slaskawi/presentations/tree/ISPN-7487-reproducer > * invoke `cd transaction-creator && mvn fabric8:run` > * Do the rolling update: `oc deploy transactions-repository --latest -n myproject` > * Observe logs `kubetail -l environment=infrastructure` -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2017