January 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-8706) HotRodMergeTest Timed out waiting for rebalancing to complete

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-8706?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8706: ------------------------------- Attachment: HotRodMergeTest_20180129.log.gz > HotRodMergeTest Timed out waiting for rebalancing to complete > ------------------------------------------------------------- > > Key: ISPN-8706 > URL: https://issues.jboss.org/browse/ISPN-8706 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 9.2.0.Alpha2 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Attachments: HotRodMergeTest_20180129.log.gz > > > The HotRodMergeTest is now consistently failing with the following error: > {code} > [OK: 321, KO: 1, SKIP: 0] Test failed: org.infinispan.server.hotrod.HotRodMergeTest.testNewTopologySentAfterCleanMerge[DIST_SYNC] > java.lang.RuntimeException: Timed out waiting for rebalancing to complete on node HotRodMergeTest[DIST_SYNC]-NodeA-31095, expected member list is [HotRodMergeTest[DIST_SYNC]-NodeA-31095, HotRodMergeTest[DIST_SYNC]-NodeB-33866], current member list is [HotRodMergeTest[DIST_SYNC]-NodeA-31095]! > at org.infinispan.test.TestingUtil.waitForNoRebalance(TestingUtil.java:388) > at org.infinispan.test.TestingUtil.waitForNoRebalance(TestingUtil.java:424) > at org.infinispan.partitionhandling.BasePartitionHandlingTest$Partition.waitForPartitionToForm(BasePartitionHandlingTest.java:282) > at org.infinispan.partitionhandling.BasePartitionHandlingTest$Partition.merge(BasePartitionHandlingTest.java:258) > at org.infinispan.partitionhandling.BasePartitionHandlingTest$Partition.merge(BasePartitionHandlingTest.java:246) > at org.infinispan.server.hotrod.HotRodMergeTest.testNewTopologySentAfterCleanMerge(HotRodMergeTest.java:87) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:348) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:38) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:382) > at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8706) HotRodMergeTest Timed out waiting for rebalancing to complete

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-8706?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8706: ------------------------------- Status: Open (was: New) > HotRodMergeTest Timed out waiting for rebalancing to complete > ------------------------------------------------------------- > > Key: ISPN-8706 > URL: https://issues.jboss.org/browse/ISPN-8706 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 9.2.0.Alpha2 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Attachments: HotRodMergeTest_20180129.log.gz > > > The HotRodMergeTest is now consistently failing with the following error: > {code} > [OK: 321, KO: 1, SKIP: 0] Test failed: org.infinispan.server.hotrod.HotRodMergeTest.testNewTopologySentAfterCleanMerge[DIST_SYNC] > java.lang.RuntimeException: Timed out waiting for rebalancing to complete on node HotRodMergeTest[DIST_SYNC]-NodeA-31095, expected member list is [HotRodMergeTest[DIST_SYNC]-NodeA-31095, HotRodMergeTest[DIST_SYNC]-NodeB-33866], current member list is [HotRodMergeTest[DIST_SYNC]-NodeA-31095]! > at org.infinispan.test.TestingUtil.waitForNoRebalance(TestingUtil.java:388) > at org.infinispan.test.TestingUtil.waitForNoRebalance(TestingUtil.java:424) > at org.infinispan.partitionhandling.BasePartitionHandlingTest$Partition.waitForPartitionToForm(BasePartitionHandlingTest.java:282) > at org.infinispan.partitionhandling.BasePartitionHandlingTest$Partition.merge(BasePartitionHandlingTest.java:258) > at org.infinispan.partitionhandling.BasePartitionHandlingTest$Partition.merge(BasePartitionHandlingTest.java:246) > at org.infinispan.server.hotrod.HotRodMergeTest.testNewTopologySentAfterCleanMerge(HotRodMergeTest.java:87) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:348) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:38) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:382) > at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8727) REST endpoint MBean is called REST-REST

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-8727?page=com.atlassian.jira.plugin.... ] Martin Gencur updated ISPN-8727: -------------------------------- Affects Version/s: 9.2.0.CR1 (was: 9.1.4.Final) > REST endpoint MBean is called REST-REST > --------------------------------------- > > Key: ISPN-8727 > URL: https://issues.jboss.org/browse/ISPN-8727 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.2.0.CR1 > Reporter: Martin Gencur > Assignee: Martin Gencur > Priority: Minor > Attachments: REST-REST.png > > > The MBean for REST endpoint is called REST-REST when the endpoint xml tag doesn't have any name attribute. This is different for HotRod and Memcached where they have correct names (i.e. "HotRod", "Memcached") . Attaching a screenshot. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8727) REST endpoint MBean is called REST-REST

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-8727?page=com.atlassian.jira.plugin.... ] Martin Gencur updated ISPN-8727: -------------------------------- Status: Open (was: New) > REST endpoint MBean is called REST-REST > --------------------------------------- > > Key: ISPN-8727 > URL: https://issues.jboss.org/browse/ISPN-8727 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.1.4.Final > Reporter: Martin Gencur > Assignee: Martin Gencur > Priority: Minor > Attachments: REST-REST.png > > > The MBean for REST endpoint is called REST-REST when the endpoint xml tag doesn't have any name attribute. This is different for HotRod and Memcached where they have correct names (i.e. "HotRod", "Memcached") . Attaching a screenshot. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8727) REST endpoint MBean is called REST-REST

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-8727?page=com.atlassian.jira.plugin.... ] Martin Gencur updated ISPN-8727: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5704 > REST endpoint MBean is called REST-REST > --------------------------------------- > > Key: ISPN-8727 > URL: https://issues.jboss.org/browse/ISPN-8727 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.1.4.Final > Reporter: Martin Gencur > Assignee: Martin Gencur > Priority: Minor > Attachments: REST-REST.png > > > The MBean for REST endpoint is called REST-REST when the endpoint xml tag doesn't have any name attribute. This is different for HotRod and Memcached where they have correct names (i.e. "HotRod", "Memcached") . Attaching a screenshot. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8727) REST endpoint MBean is called REST-REST

by Martin Gencur (JIRA)

Martin Gencur created ISPN-8727: ----------------------------------- Summary: REST endpoint MBean is called REST-REST Key: ISPN-8727 URL: https://issues.jboss.org/browse/ISPN-8727 Project: Infinispan Issue Type: Bug Components: JMX, reporting and management Affects Versions: 9.1.4.Final Reporter: Martin Gencur Assignee: Martin Gencur Priority: Minor Attachments: REST-REST.png The MBean for REST endpoint is called REST-REST when the endpoint xml tag doesn't have any name attribute. This is different for HotRod and Memcached where they have correct names (i.e. "HotRod", "Memcached") . Attaching a screenshot. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8727) REST endpoint MBean is called REST-REST

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-8727?page=com.atlassian.jira.plugin.... ] Martin Gencur updated ISPN-8727: -------------------------------- Attachment: REST-REST.png > REST endpoint MBean is called REST-REST > --------------------------------------- > > Key: ISPN-8727 > URL: https://issues.jboss.org/browse/ISPN-8727 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.1.4.Final > Reporter: Martin Gencur > Assignee: Martin Gencur > Priority: Minor > Attachments: REST-REST.png > > > The MBean for REST endpoint is called REST-REST when the endpoint xml tag doesn't have any name attribute. This is different for HotRod and Memcached where they have correct names (i.e. "HotRod", "Memcached") . Attaching a screenshot. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8715) Local counters

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-8715?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-8715: ------------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Local counters > -------------- > > Key: ISPN-8715 > URL: https://issues.jboss.org/browse/ISPN-8715 > Project: Infinispan > Issue Type: Feature Request > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 9.2.0.Final, 9.2.0.CR2 > > > If the cache manager doesn't have a transport configured, we don't allow the creation of counters. > We can add non-local counters for that scenario. > The counters created will be based on the {{GlobalConfiguration}} used. > Note: WeakCounters supported? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8651) Use functional commands for JCache operations

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-8651?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-8651: ------------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.2.0.CR2 Resolution: Done > Use functional commands for JCache operations > --------------------------------------------- > > Key: ISPN-8651 > URL: https://issues.jboss.org/browse/ISPN-8651 > Project: Infinispan > Issue Type: Enhancement > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.2.0.CR2 > > > Some JCache operations (especially the {{invoke}}) cannot be executed using single command. We should run those using functional commands if possible. > -Regarding the {{invoke}} we have to find out if the {{EntryProcessor}} is marshallable. If it is we will assume that it does not have any side-effect and can be invoked on remote node; we should let the user opt-out of this behaviour through a system property.- > JSR107 spec says that implementation may require the EntryProcessor to be serializable or marshallable in some manner. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8676) Non-writing functional command should not go to backup

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-8676?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-8676: ------------------------------------ Status: Open (was: New) > Non-writing functional command should not go to backup > ------------------------------------------------------ > > Key: ISPN-8676 > URL: https://issues.jboss.org/browse/ISPN-8676 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.2.0.Beta2 > Reporter: Radim Vansa > Assignee: Radim Vansa > > When a functional read/write or write-only command results in the entry not being changed, the command should not be sent to the backup owner. > Solving this for single entry is trivial (setting {{successful = false}}), the routing logic for multi-key commands is more complex. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 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 2018