[JBoss JIRA] (ISPN-8518) FunctionalDistributionTest.testDistributionFromNonOwner random failures
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-8518?page=com.atlassian.jira.plugin.... ]
Dan Berindei reassigned ISPN-8518:
----------------------------------
Assignee: Radim Vansa
> 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
> Labels: testsuite_stability
> Fix For: 9.2.0.Beta2
>
>
> 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.5.0#75005)
7 years, 2 months
[JBoss JIRA] (ISPN-8518) FunctionalDistributionTest.testDistributionFromNonOwner random failures
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-8518?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-8518:
-------------------------------
Status: Open (was: New)
> 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
> Labels: testsuite_stability
> Fix For: 9.2.0.Beta2
>
>
> 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.5.0#75005)
7 years, 2 months
[JBoss JIRA] (ISPN-8518) FunctionalDistributionTest.testDistributionFromNonOwner random failures
by Dan Berindei (JIRA)
Dan Berindei created ISPN-8518:
----------------------------------
Summary: 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
Fix For: 9.2.0.Beta2
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.5.0#75005)
7 years, 2 months
[JBoss JIRA] (ISPRK-48) Improve Java API for filterByQuery
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPRK-48?page=com.atlassian.jira.plugin.s... ]
Gustavo Fernandes updated ISPRK-48:
-----------------------------------
Description:
When filtering an RDD by a deployed filter, the following Java syntax can be used:
{code}
InfinispanJavaRDD<String, MyEntity> infinispanRDD = ...
JavaPairRDD<String, MyEntity> filtered = infinispanRDD.filterByCustom("my-filter");
{code}
but the same syntatic sugar cannot be used with the newly introduced methods filterByQuery
was:
When filtering an RDD by a deployed filter, the following Java syntax can be used:
{code}
InfinispanJavaRDD<String, MyEntity> infinispanRDD = ...
JavaPairRDD<String, MyEntity> filtered = infinispanRDD.filterByCustom("my-filter");
{code}
but the same syntatic sugar cannot be used with the newly introduced methods filterByQuery
> Improve Java API for filterByQuery
> ----------------------------------
>
> Key: ISPRK-48
> URL: https://issues.jboss.org/browse/ISPRK-48
> Project: Infinispan Spark
> Issue Type: Enhancement
> Components: Java API
> Affects Versions: 0.5
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Fix For: 0.6
>
>
> When filtering an RDD by a deployed filter, the following Java syntax can be used:
> {code}
> InfinispanJavaRDD<String, MyEntity> infinispanRDD = ...
> JavaPairRDD<String, MyEntity> filtered = infinispanRDD.filterByCustom("my-filter");
> {code}
> but the same syntatic sugar cannot be used with the newly introduced methods filterByQuery
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (ISPRK-48) Improve Java API for filterByQuery
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPRK-48?page=com.atlassian.jira.plugin.s... ]
Gustavo Fernandes updated ISPRK-48:
-----------------------------------
Description:
When filtering an RDD by a deployed filter, the following Java syntax can be used:
{code}
InfinispanJavaRDD<String, MyEntity> infinispanRDD = ...
JavaPairRDD<String, MyEntity> filtered = infinispanRDD.filterByCustom("my-filter");
{code}
but the same syntax sugar cannot be used with the newly introduced methods {{filterByQuery}}
was:
When filtering an RDD by a deployed filter, the following Java syntax can be used:
{code}
InfinispanJavaRDD<String, MyEntity> infinispanRDD = ...
JavaPairRDD<String, MyEntity> filtered = infinispanRDD.filterByCustom("my-filter");
{code}
but the same syntatic sugar cannot be used with the newly introduced methods filterByQuery
> Improve Java API for filterByQuery
> ----------------------------------
>
> Key: ISPRK-48
> URL: https://issues.jboss.org/browse/ISPRK-48
> Project: Infinispan Spark
> Issue Type: Enhancement
> Components: Java API
> Affects Versions: 0.5
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Fix For: 0.6
>
>
> When filtering an RDD by a deployed filter, the following Java syntax can be used:
> {code}
> InfinispanJavaRDD<String, MyEntity> infinispanRDD = ...
> JavaPairRDD<String, MyEntity> filtered = infinispanRDD.filterByCustom("my-filter");
> {code}
> but the same syntax sugar cannot be used with the newly introduced methods {{filterByQuery}}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (ISPRK-48) Improve Java API for filterByQuery
by Gustavo Fernandes (JIRA)
Gustavo Fernandes created ISPRK-48:
--------------------------------------
Summary: Improve Java API for filterByQuery
Key: ISPRK-48
URL: https://issues.jboss.org/browse/ISPRK-48
Project: Infinispan Spark
Issue Type: Enhancement
Components: Java API
Affects Versions: 0.5
Reporter: Gustavo Fernandes
Assignee: Gustavo Fernandes
Fix For: 0.6
When filtering an RDD by a deployed filter, the following Java syntax can be used:
{code}
InfinispanJavaRDD<String, MyEntity> infinispanRDD = ...
JavaPairRDD<String, MyEntity> filtered = infinispanRDD.filterByCustom("my-filter");
{code}
but the same syntatic sugar cannot be used with the newly introduced methods filterByQuery
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (ISPRK-48) Improve Java API for filterByQuery
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPRK-48?page=com.atlassian.jira.plugin.s... ]
Gustavo Fernandes updated ISPRK-48:
-----------------------------------
Status: Open (was: New)
> Improve Java API for filterByQuery
> ----------------------------------
>
> Key: ISPRK-48
> URL: https://issues.jboss.org/browse/ISPRK-48
> Project: Infinispan Spark
> Issue Type: Enhancement
> Components: Java API
> Affects Versions: 0.5
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Fix For: 0.6
>
>
> When filtering an RDD by a deployed filter, the following Java syntax can be used:
> {code}
> InfinispanJavaRDD<String, MyEntity> infinispanRDD = ...
> JavaPairRDD<String, MyEntity> filtered = infinispanRDD.filterByCustom("my-filter");
> {code}
> but the same syntatic sugar cannot be used with the newly introduced methods filterByQuery
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (ISPN-8517) Lazily ressurect ice fromMemory
by William Burns (JIRA)
William Burns created ISPN-8517:
-----------------------------------
Summary: Lazily ressurect ice fromMemory
Key: ISPN-8517
URL: https://issues.jboss.org/browse/ISPN-8517
Project: Infinispan
Issue Type: Sub-task
Components: Off Heap
Affects Versions: 9.2.0.Alpha2
Reporter: William Burns
Assignee: William Burns
Currently many places do
{code}
ice = ice = offHeapEntryFactory.fromMemory(address)
if (wrappedKey.equalsWrappedBytes(ice.getKey()))
{code}
In cases where this ends up being a miss, we read the entire value which is wasteful. And the CPU may not have the key in the cache size we read the object into memory. Where as if we do
{code}
if (offHeapEntryFactory.equalsKey(address, key))
ice = ice = offHeapEntryFactory.fromMemory(address)
{code}
we know that CPU is reading from the address location twice in a row, which has a very high chance of still being in CPU caches which should hopefully provide better performance. We also then don't have to read the entire ice object in memory unless there was a hit.
We also should change _performGet_ to return the address instead of the ice. This way callers can use this address for other optimizations such as when doing a _evict_ or _compute_ which have to read the entry first before a remove.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months