[JBoss JIRA] (ISPN-4258) *MassIndexing.testReindexing test fails randomly on RHEL7
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4258?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-4258:
-----------------------------------------------
Vojtech Juranek <vjuranek(a)redhat.com> changed the Status of [bug 1208162|https://bugzilla.redhat.com/show_bug.cgi?id=1208162] from ON_QA to VERIFIED
> *MassIndexing.testReindexing test fails randomly on RHEL7
> -----------------------------------------------------------
>
> Key: ISPN-4258
> URL: https://issues.jboss.org/browse/ISPN-4258
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying
> Affects Versions: 7.0.0.Alpha3
> Reporter: Vitalii Chepeliuk
> Assignee: Gustavo Fernandes
> Labels: testsuite_stability
> Fix For: 7.0.0.Beta2
>
> Attachments: MassIndexingTests.zip
>
>
> Following tests fail with assertion error
> DistProgrammaticMassIndexTest.testReindexing
> TopologyAwareDistMassIndexingTest.testReindexing
> DistributedMassIndexingTest.testReindexing
> DistributedMassIndexingViaJmxTest.testReindexing
> DistributedMassIndexingViaJmxTest.createBeforeClass
> {noformat}
> java.lang.AssertionError: expected:<3> but was:<0>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:555)
> at org.junit.Assert.assertEquals(Assert.java:542)
> at org.infinispan.query.distributed.DistributedMassIndexingTest.verifyFindsCar(DistributedMassIndexingTest.java:89)
> at org.infinispan.query.distributed.DistributedMassIndexingTest.verifyFindsCar(DistributedMassIndexingTest.java:80)
> at org.infinispan.query.distributed.DistributedMassIndexingTest.testReindexing(DistributedMassIndexingTest.java:58)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
> 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:334)
> at org.testng.SuiteRunner.access$000(SuiteRunner.java:37)
> at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368)
> at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:744)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (ISPN-5368) Out of order events produced when using the MassIndexer with async backend
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-5368?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-5368:
-----------------------------------------------
Vojtech Juranek <vjuranek(a)redhat.com> changed the Status of [bug 1208162|https://bugzilla.redhat.com/show_bug.cgi?id=1208162] from ON_QA to VERIFIED
> Out of order events produced when using the MassIndexer with async backend
> --------------------------------------------------------------------------
>
> Key: ISPN-5368
> URL: https://issues.jboss.org/browse/ISPN-5368
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 7.2.0.Beta2, 7.1.1.Final
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Fix For: 7.2.0.CR1, 7.2.0.Final
>
>
> When using async indexing backend on DIST caches with shared index (InfinispanIndexManager), the MassIndexer fails to re-index all the entries, if it is run from a node that is not
> the indexing master.
> Normally the operation sequence of the MassIndexer in the above configuration, for a two node cluster is:
> * Purge the index
> * Send index job to node A and to node B
> * Flush
> Given the backend is async, all index commands are sent to the master RPC-wise asynchronously, and so a reorder can occur and produce like:
> * Send index job to node A
> * Purge
> * Send index job to node B
> * Flush
> Causing previously re-indexed entries to be wiped
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (ISPN-4491) Cluster Listener Event Batching
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4491?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-4491:
-----------------------------------------------
Vojtech Juranek <vjuranek(a)redhat.com> changed the Status of [bug 1212012|https://bugzilla.redhat.com/show_bug.cgi?id=1212012] from ON_QA to VERIFIED
> Cluster Listener Event Batching
> -------------------------------
>
> Key: ISPN-4491
> URL: https://issues.jboss.org/browse/ISPN-4491
> Project: Infinispan
> Issue Type: Enhancement
> Components: Listeners
> Affects Versions: 7.0.2.Final
> Reporter: William Burns
> Assignee: William Burns
> Fix For: 7.1.0.Beta1, 7.1.0.Final
>
>
> Currently when a local listener which was installed for a cluster listener finds an event to send back to the parent it does this 1 message per listener. It might be more beneficial if we had batching so that it wouldn't send 1 message per.
> There are 2 cases I can think of which this would benefit.
> # When the underlying transport is UDP. In this case we can send just 1 message to all the nodes for the event instead of N Unicasts
> # When a node has more than 1 cluster listener installed we could send a single message to notifiy more than 1 listener.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (ISPN-5400) Make JpaStore class loader for entity class configurable
by Tuomas Kiviaho (JIRA)
Tuomas Kiviaho created ISPN-5400:
------------------------------------
Summary: Make JpaStore class loader for entity class configurable
Key: ISPN-5400
URL: https://issues.jboss.org/browse/ISPN-5400
Project: Infinispan
Issue Type: Feature Request
Components: Loaders and Stores
Affects Versions: 7.1.1.Final
Reporter: Tuomas Kiviaho
JpaStore entity class is loaded using Infinispan's class loader. This is not ideal in environments such as OSGi where Infinispan and entities may locate in different class loaders.
My workaround was to patch {{JpaStoreConfigurationParser71.parseJpaCacheStore}} to utilize the entity class loader I has earlier passed to configuration builder holder. By default it seems to point to thread class loader so it should work in modern OSGi environments out-of-the-box.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months