March 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5262) StateTransfer considerably slow with sync indexing

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5262?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5262: ------------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3296 > StateTransfer considerably slow with sync indexing > -------------------------------------------------- > > Key: ISPN-5262 > URL: https://issues.jboss.org/browse/ISPN-5262 > Project: Infinispan > Issue Type: Enhancement > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > > The {{StateResponseCommand}} applies state sequentially, chunk by chunk. > The sequential cache population by a single thread does not take advantage of the index backend automatic batching capabilities when subjected to multiple threads and consequentially state transfer time can become prohibitive for large number of entries. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5262) StateTransfer considerably slow with sync indexing

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5262?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5262: ------------------------------------ Status: Open (was: New) > StateTransfer considerably slow with sync indexing > -------------------------------------------------- > > Key: ISPN-5262 > URL: https://issues.jboss.org/browse/ISPN-5262 > Project: Infinispan > Issue Type: Enhancement > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > > The {{StateResponseCommand}} applies state sequentially, chunk by chunk. > The sequential cache population by a single thread does not take advantage of the index backend automatic batching capabilities when subjected to multiple threads and consequentially state transfer time can become prohibitive for large number of entries. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5279) Some core notification filter implementations have an externalizer and are also Serializable

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5279?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5279: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3295 > Some core notification filter implementations have an externalizer and are also Serializable > -------------------------------------------------------------------------------------------- > > Key: ISPN-5279 > URL: https://issues.jboss.org/browse/ISPN-5279 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.2.0.Alpha1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5278) Require Maven 3.1.1 or newer

by Ion Savin (JIRA)

Ion Savin created ISPN-5278: ------------------------------- Summary: Require Maven 3.1.1 or newer Key: ISPN-5278 URL: https://issues.jboss.org/browse/ISPN-5278 Project: Infinispan Issue Type: Feature Request Components: Build process Affects Versions: 7.2.0.Alpha1 Reporter: Ion Savin Assignee: Ion Savin wildfly-maven-plugin 1.1.0.Alpha1 breaks on 3.0.5, enforce 3.1.1 or newer. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5279) Some core notification filter implementations have an externalizer and are also Serializable

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-5279: ----------------------------------- Summary: Some core notification filter implementations have an externalizer and are also Serializable Key: ISPN-5279 URL: https://issues.jboss.org/browse/ISPN-5279 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 7.2.0.Alpha1 Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 7.2.0.Beta1 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5279) Some core notification filter implementations have an externalizer and are also Serializable

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5279?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5279: -------------------------------- Status: Open (was: New) > Some core notification filter implementations have an externalizer and are also Serializable > -------------------------------------------------------------------------------------------- > > Key: ISPN-5279 > URL: https://issues.jboss.org/browse/ISPN-5279 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.2.0.Alpha1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5274) Inconsistent data after transaction rollback (with success on originator)

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5274?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5274: ------------------------------- Status: Open (was: New) > Inconsistent data after transaction rollback (with success on originator) > ------------------------------------------------------------------------- > > Key: ISPN-5274 > URL: https://issues.jboss.org/browse/ISPN-5274 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Matej Čimbora > Assignee: Dan Berindei > > Scenario > Nodes edg-perf[10-13], partition handling on > 1.Transaction is started on edg-perf10 > {code} > 10:24:48,228 TRACE [org.infinispan.transaction.xa.TransactionXaAdapter] (DefaultStressor-6) start called on tx GlobalTransaction:<edg-perf10-20667>:38910:local > {code} > 2. Value of key_000000000000065B is updated within the transaction > {code} > 10:24:48,405 TRACE [org.radargun.service.InfinispanOperations$Cache] (DefaultStressor-6) PUT cache=testCache key=key_000000000000065B value=[6 #15: 296, 501, 1109, 1119, 1459, 1544, 1999, 2083, 2130, 2257, 2298, 2784, 2941, 3009, 3147, ] > {code} > 3. Transaction is successfully prepared on edg-perf11 & edg-perf12 > {code} > 10:24:48,559 TRACE [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (DefaultStressor-6) Responses: [sender=edg-perf11-61837, received=true, suspected=false] > [sender=edg-perf12-7305, received=true, suspected=false] > {code} > 4. Transaction commit is issued > {code} > 10:24:48,562 TRACE [org.infinispan.transaction.TransactionCoordinator] (DefaultStressor-6) Committing transaction GlobalTransaction:<edg-perf10-20667>:38910:local > {code} > 5. Other participating nodes (edg-perf11 & edg-perf12) are suspected... > {code} > 10:24:52,705 TRACE [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (DefaultStressor-6) Target node edg-perf11-61837 left during remote call, ignoring > 10:24:52,716 TRACE [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (DefaultStressor-6) Target node edg-perf12-7305 left during remote call, ignoring > {code} > ... as they received a new view (without edg-perf10) meanwhile. > {code} > 10:24:48,547 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-1,edg-perf12-7305) ISPN000093: Received new, MERGED cluster view: MergeView::[edg-perf12-7305|20] (3) [edg-perf12-7305, edg-perf11-61837, edg-perf13-25187], 2 subgroups: [edg-perf13-25187|8] (1) [edg-perf13-25187], [edg-perf13-25187|19] (1) [edg-perf13-25187] > {code} > Still, the transaction is commited on edg-perf10 & updated entry is stored locally > {code} > 10:24:52,894 TRACE [org.infinispan.statetransfer.CommitManager] (DefaultStressor-6) Trying to commit. Key=key_000000000000065B. Operation Flag=null, L1 invalidation=false > 10:24:52,896 TRACE [org.infinispan.statetransfer.CommitManager] (DefaultStressor-6) Committing key=key_000000000000065B. It is a L1 invalidation or a normal put and no tracking is enabled! > 10:24:52,908 TRACE [org.infinispan.container.DefaultDataContainer] (DefaultStressor-6) Creating new ICE for writing. Existing=ImmortalCacheEntry{key=key_000000000000065B, value=[6 #14: 296, 501, 1109, 1119, 1459, 1544, 1999, 2083, 2130, 2257, 2298, 2784, 2941, 3009, ]}, metadata=EmbeddedMetadata{version=null}, new value=[6 #15: 296, 501, 1109, 1119, 1459, 1544, 1999, 2083, 2130, 2257, 2298, 2784, 2941, 3009, 3147, ] > {code} > 6. Other nodes rollback the transaction > {code} > 10:24:50,376 DEBUG [org.infinispan.transaction.TransactionTable] (transport-thread-10) Rolling back transaction GlobalTransaction:<edg-perf10-20667>:38910:remote because originator edg-perf10-20667 left the cluster > {code} > 7. edg-perf10 receives a new view, containing nodes edg-perf[10,11,13]. Incoming state transfer overwrites the updated value > {code} > 10:25:09,614 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-2,edg-perf10-20667) ISPN000093: Received new, MERGED cluster view: MergeView::[edg-perf10-20667|22] (3) [edg-perf10-20667, edg-perf11-61837, edg-perf13-25187], 4 subgroups: [edg-perf10-20667|15] (2) [edg-perf10-20667, edg-perf11-61837], [edg-perf10-20667|19] (3) [edg-perf10-20667, edg-perf12-7305, edg-perf11-61837], [edg-perf10-20667|18] (1) [edg-perf10-20667], [edg-perf10-20667|21] (2) [edg-perf10-20667, edg-perf13-25187] > {code} > 8. get operation returns outdated value > {code} > 10:26:21,020 TRACE [org.infinispan.remoting.rpc.RpcManagerImpl] (DefaultStressor-6) Response(s) to ClusteredGetCommand{key=key_000000000000065B, flags=null} is {edg-perf12-7305=SuccessfulResponse{responseValue=ImmortalCacheValue {value=[6 #14: 296, 501, 1109, 1119, 1459, 1544, 1999, 2083, 2130, 2257, 2298, 2784, 2941, 3009, ]}} } > {code} > From client perspective, this behavior is not transparent. Provided the transaction ended up successfully, presence of the updated entry can be assumed. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-4323) ConditionalOperationsConcurrentWriteSkewTest fails randomly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4323?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4323: ----------------------------------------------- Tomas Sykora <tsykora(a)redhat.com> changed the Status of [bug 1101088|https://bugzilla.redhat.com/show_bug.cgi?id=1101088] from ON_QA to VERIFIED > ConditionalOperationsConcurrentWriteSkewTest fails randomly > ----------------------------------------------------------- > > Key: ISPN-4323 > URL: https://issues.jboss.org/browse/ISPN-4323 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.0.0.Alpha1, 7.0.0.Alpha2, 7.0.0.Alpha3, 7.0.0.Alpha4 > Environment: RHEL and Open JDK > Reporter: Vitalii Chepeliuk > Assignee: William Burns > Priority: Blocker > Labels: testsuite_stability > Fix For: 7.0.0.Beta2 > > Attachments: ConditionalOperationsConcurrentWriteSkewTest.log.zip, ConditionalOperationsConcurrentWriteSkewTest.tar.bz2 > > > Following tests fail with TImeout exception > org.infinispan.api.ConditionalOperationsConcurrentWriteSkewTest.testConditionalRemove > org.infinispan.api.ConditionalOperationsConcurrentWriteSkewTest.testReplace > org.infinispan.api.ConditionalOperationsConcurrentWriteSkewTest.testPutIfAbsent > {noformat} > java.lang.AssertionError: java.lang.RuntimeException: java.util.concurrent.TimeoutException > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertFalse(Assert.java:64) > at org.infinispan.api.ConditionalOperationsConcurrentTest.testOnCaches(ConditionalOperationsConcurrentTest.java:129) > at org.infinispan.api.ConditionalOperationsConcurrentWriteSkewTest.testConditionalRemove(ConditionalOperationsConcurrentWriteSkewTest.java:56) > 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} > Failing tests in Jenkins > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5271) Usage of filter composition in DistributedEntryRetriever.sendRequest prevents dependency injection to filter and converter

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5271?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5271: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Usage of filter composition in DistributedEntryRetriever.sendRequest prevents dependency injection to filter and converter > -------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-5271 > URL: https://issues.jboss.org/browse/ISPN-5271 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.2.0.Alpha1, 7.1.1.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5277) Add a functional test for remote events with filters and protobuf marshalling

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5277?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5277: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3294 > Add a functional test for remote events with filters and protobuf marshalling > ----------------------------------------------------------------------------- > > Key: ISPN-5277 > URL: https://issues.jboss.org/browse/ISPN-5277 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Affects Versions: 7.2.0.Alpha1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.Beta1 > > > This exact scenario is not covered by existing tests. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2015