October 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-8799) Limit the default number of shards in the AffinityIndexManager

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-8799?page=com.atlassian.jira.plugin.... ] Diego Lovison updated ISPN-8799: -------------------------------- Labels: on-hold (was: ) > Limit the default number of shards in the AffinityIndexManager > -------------------------------------------------------------- > > Key: ISPN-8799 > URL: https://issues.jboss.org/browse/ISPN-8799 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Labels: on-hold > Fix For: 9.4.0.CR3 > > > By default this index manager will create as many Lucene indexes as Infinispan segments (256) which will penalize query performance. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8799) Limit the default number of shards in the AffinityIndexManager

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-8799?page=com.atlassian.jira.plugin.... ] Diego Lovison updated ISPN-8799: -------------------------------- Tester: Diego Lovison > Limit the default number of shards in the AffinityIndexManager > -------------------------------------------------------------- > > Key: ISPN-8799 > URL: https://issues.jboss.org/browse/ISPN-8799 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 9.4.0.CR3 > > > By default this index manager will create as many Lucene indexes as Infinispan segments (256) which will penalize query performance. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9362) Break cycles in exception stack traces

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-9362?page=com.atlassian.jira.plugin.... ] Diego Lovison closed ISPN-9362. ------------------------------- > Break cycles in exception stack traces > -------------------------------------- > > Key: ISPN-9362 > URL: https://issues.jboss.org/browse/ISPN-9362 > Project: Infinispan > Issue Type: Task > Affects Versions: 9.3.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 9.4.0.CR3, 9.3.1.Final > > > As most of the core became non-blocking, the exception stack traces became less relevant, because as the exception is re-thrown on multiple threads yet the stack trace only shows the initial thread. > ISPN-8893 improved this in some methods that are still blocking by catching an {{ExecutionException}}, adding it to the suppressed list of the cause, and rethrowing the cause. However, cycles in the exception trace is not properly supported by all loggers, e.g. {{logback}} only has a fix in the not yet released version 1.3.0. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8518) FunctionalDistributionTest.testDistributionFromNonOwner random failures

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-8518?page=com.atlassian.jira.plugin.... ] Diego Lovison updated ISPN-8518: -------------------------------- Labels: on-hold testsuite_stability (was: testsuite_stability) > FunctionalDistributionTest.testDistributionFromNonOwner random failures > ----------------------------------------------------------------------- > > Key: ISPN-8518 > URL: https://issues.jboss.org/browse/ISPN-8518 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.2.0.Alpha2 > Reporter: Dan Berindei > Assignee: Radim Vansa > Priority: Major > Labels: on-hold, testsuite_stability > Fix For: 9.4.0.CR3 > > > Waiting 100ms is not always enough for the write to be applied on all the owners: > {noformat} > java.lang.NullPointerException > at org.infinispan.functional.FunctionalDistributionTest.lambda$iterate$8(FunctionalDistributionTest.java:97) > at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) > at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175) > at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) > at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1380) > at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481) > at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) > at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708) > at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) > at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499) > at org.infinispan.functional.FunctionalDistributionTest.iterate(FunctionalDistributionTest.java:98) > at org.infinispan.functional.FunctionalDistributionTest.doTestDistribution(FunctionalDistributionTest.java:77) > at org.infinispan.functional.FunctionalDistributionTest.testDistributionFromNonOwner(FunctionalDistributionTest.java:66) > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8431) ScatteredSplitAndMergeTest random failures

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-8431?page=com.atlassian.jira.plugin.... ] Diego Lovison updated ISPN-8431: -------------------------------- Labels: on-hold testsuite_stability (was: testsuite_stability) > ScatteredSplitAndMergeTest random failures > ------------------------------------------ > > Key: ISPN-8431 > URL: https://issues.jboss.org/browse/ISPN-8431 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.2.0.Alpha1 > Environment: Jenkins > Reporter: Tristan Tarrant > Assignee: Radim Vansa > Priority: Major > Labels: on-hold, testsuite_stability > Fix For: 9.4.0.Beta1, 9.4.0.CR3 > > Attachments: ScatteredSplitAndMergeTest_20180129.log.gz, ScatteredSplitAndMergeTest_ISPN-7919_RpcManager_ResponseCollector_20171212.log.gz > > > http://ci.infinispan.org/job/Infinispan/job/master/214/testReport/junit/o... > java.lang.AssertionError: expected [null] but found [v0] > at org.infinispan.partitionhandling.ScatteredSplitAndMergeTest.testSplitAndMerge(ScatteredSplitAndMergeTest.java:80) > at org.infinispan.partitionhandling.ScatteredSplitAndMergeTest.testSplitAndMerge5(ScatteredSplitAndMergeTest.java:51) > 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) > ... Removed 20 stack frames > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9474) ScriptingDataStoresTest fails

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-9474?page=com.atlassian.jira.plugin.... ] Diego Lovison updated ISPN-9474: -------------------------------- Labels: on-hold (was: ) > ScriptingDataStoresTest fails > ----------------------------- > > Key: ISPN-9474 > URL: https://issues.jboss.org/browse/ISPN-9474 > Project: Infinispan > Issue Type: Bug > Components: Tasks > Affects Versions: 9.4.0.CR1 > Reporter: Adrian Nistor > Assignee: Gustavo Fernandes > Priority: Major > Labels: on-hold > Fix For: 9.4.0.CR3 > > > This test is currently not executed because it does not declare params and AbstractInfinispanTest mistakenly detects is as name duplicate. > Running it from command line individually will show 0 executed tests. > Need to add params to make its name unique and pass AbstractInfinispanTest's validation: > {code} > @Override > protected String parameters() { > return "[" + storageType + "]"; > } > {code} > After fixing this you can see that it is finally executed and it fails; here's one of the failures: > {code} > [ERROR] testScriptWithoutParam[OFF_HEAP](org.infinispan.scripting.ScriptingDataStoresTest) Time elapsed: 0.015 s <<< FAILURE! > java.lang.AssertionError: expected:<javaValue:additionFromJavascript> but was:<javaValue> > at org.testng.AssertJUnit.fail(AssertJUnit.java:59) > at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:88) > at org.infinispan.scripting.ScriptingDataStoresTest.testScriptWithoutParam(ScriptingDataStoresTest.java:81) > 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:85) > at org.testng.internal.MethodInvocationHelper$1.runTestMethod(MethodInvocationHelper.java:196) > at org.infinispan.commons.test.TestNGLongTestsHook.run(TestNGLongTestsHook.java:24) > at org.testng.internal.MethodInvocationHelper.invokeHookable(MethodInvocationHelper.java:208) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:635) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:816) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1124) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:108) > at org.testng.TestRunner.privateRun(TestRunner.java:774) > at org.testng.TestRunner.run(TestRunner.java:624) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:359) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:39) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:393) > 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.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9393) getAsync() and getWithMetadata() does not check NearCache

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-9393?page=com.atlassian.jira.plugin.... ] Diego Lovison closed ISPN-9393. ------------------------------- > getAsync() and getWithMetadata() does not check NearCache > --------------------------------------------------------- > > Key: ISPN-9393 > URL: https://issues.jboss.org/browse/ISPN-9393 > Project: Infinispan > Issue Type: Bug > Components: Hot Rod, Remote Protocols > Reporter: Pedro Ruivo > Assignee: Tristan Tarrant > Priority: Blocker > Fix For: 9.4.0.Beta1, 9.4.0.CR3 > > > In ISPN-8618, the java client was made async. > However, the {{getAsync()}} method isn't checking the {{NearCache}} anymore. > EDIT: {{getWithMetadata()}} isn't check the {{NearCache}}. I'm not sure if it is supposed to check it or not. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9393) getAsync() and getWithMetadata() does not check NearCache

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9393?page=com.atlassian.jira.plugin.... ] Tristan Tarrant resolved ISPN-9393. ----------------------------------- Resolution: Done > getAsync() and getWithMetadata() does not check NearCache > --------------------------------------------------------- > > Key: ISPN-9393 > URL: https://issues.jboss.org/browse/ISPN-9393 > Project: Infinispan > Issue Type: Bug > Components: Hot Rod, Remote Protocols > Reporter: Pedro Ruivo > Assignee: Tristan Tarrant > Priority: Blocker > Fix For: 9.4.0.CR3, 9.4.0.Beta1 > > > In ISPN-8618, the java client was made async. > However, the {{getAsync()}} method isn't checking the {{NearCache}} anymore. > EDIT: {{getWithMetadata()}} isn't check the {{NearCache}}. I'm not sure if it is supposed to check it or not. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9393) getAsync() and getWithMetadata() does not check NearCache

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9393?page=com.atlassian.jira.plugin.... ] Tristan Tarrant commented on ISPN-9393: --------------------------------------- This is the correct behavior: puts must always invalidate the near cache entry. > getAsync() and getWithMetadata() does not check NearCache > --------------------------------------------------------- > > Key: ISPN-9393 > URL: https://issues.jboss.org/browse/ISPN-9393 > Project: Infinispan > Issue Type: Bug > Components: Hot Rod, Remote Protocols > Reporter: Pedro Ruivo > Assignee: Tristan Tarrant > Priority: Blocker > Fix For: 9.4.0.Beta1, 9.4.0.CR3 > > > In ISPN-8618, the java client was made async. > However, the {{getAsync()}} method isn't checking the {{NearCache}} anymore. > EDIT: {{getWithMetadata()}} isn't check the {{NearCache}}. I'm not sure if it is supposed to check it or not. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8003) QueryInterceptor and ProtobufMetadataManagerInterceptor fail the InterceptorDefinesAllReadWritesCheck

by Adrian Nistor (Jira)

[ https://issues.jboss.org/browse/ISPN-8003?page=com.atlassian.jira.plugin.... ] Work on ISPN-8003 started by Adrian Nistor. ------------------------------------------- > QueryInterceptor and ProtobufMetadataManagerInterceptor fail the InterceptorDefinesAllReadWritesCheck > ----------------------------------------------------------------------------------------------------- > > Key: ISPN-8003 > URL: https://issues.jboss.org/browse/ISPN-8003 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.2.0.Final, 9.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Major > Fix For: 9.4.1.Final > > > {code} > ProtobufMetadataManagerInterceptor.java:43, InterceptorDefinesAllReadWritesCheck, Priority: Normal > Interceptor defines methods [visitPutKeyValueCommand, visitRemoveCommand, visitPutMapCommand, visitReplaceCommand] but does not define [visitReadWriteKeyCommand, visitReadWriteManyCommand, visitReadWriteKeyValueCommand, visitReadWriteManyEntriesCommand] [not required for tests] > {code} > {code} > QueryInterceptor.java:69, InterceptorDefinesAllReadWritesCheck, Priority: Normal > Interceptor defines methods [visitPutKeyValueCommand, visitRemoveCommand, visitPutMapCommand, visitReplaceCommand] but does not define [visitReadWriteKeyCommand, visitReadWriteManyCommand, visitReadWriteKeyValueCommand, visitReadWriteManyEntriesCommand] [not required for tests] > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 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 October 2018