January 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (IPROTO-130) Inefficent ProtobufUtil.fromWrappedByteArray(ImmutableSerializationContext ctx, byte[] bytes)

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/IPROTO-130?page=com.atlassian.jira.plugi... ] Nistor Adrian updated IPROTO-130: --------------------------------- Fix Version/s: 4.2.6.Final 4.3.3.Final > Inefficent ProtobufUtil.fromWrappedByteArray(ImmutableSerializationContext ctx, byte[] bytes) > ---------------------------------------------------------------------------------------------- > > Key: IPROTO-130 > URL: https://issues.redhat.com/browse/IPROTO-130 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 4.2.5.Final, 4.3.2.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.2.6.Final, 4.3.3.Final > > > The implementation uses a ByteArrayInputStream that wraps the byte[], and then creates a CodedInputStream around it and this copies the input data to its own buffer. This should have been made more efficiently by building a CodedInputStream directly around the byte[] (which internally uses CodedInputStream.ArrayDecoder and doesn't need a buffer copy). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11229) Handle async-xsite in parallel

by Pedro Ruivo (Jira)

Pedro Ruivo created ISPN-11229: ---------------------------------- Summary: Handle async-xsite in parallel Key: ISPN-11229 URL: https://issues.redhat.com/browse/ISPN-11229 Project: Infinispan Issue Type: Enhancement Components: Cross-Site Replication Affects Versions: 10.0.0.CR2 Reporter: Pedro Ruivo Assignee: Pedro Ruivo Fix For: 9.1.8.Final, 10.0.0.Final Asynchronous cross-site replication relies on the ordering of the write operation to ensure data consistency. This ordering is provided by JGroups; it only delivers the next request after the first one is completed. This order contains updates for multiple caches and keys. What is proposed here is to handle different keys/cache updates in parallel. It should improve the response time, however, there is no free lunch. The following is expected: * An increase of CPU utilization: it may spawn new threads to handle different keys update in parallel * An increase in memory: it chains the updates (queue) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10657) Handle async-xsite in parallel

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-10657?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-10657: ------------------------------- Fix Version/s: 9.1.8.Final > Handle async-xsite in parallel > ------------------------------ > > Key: ISPN-10657 > URL: https://issues.redhat.com/browse/ISPN-10657 > Project: Infinispan > Issue Type: Enhancement > Components: Cross-Site Replication > Affects Versions: 10.0.0.CR2 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 9.1.8.Final, 10.0.0.Final > > > Asynchronous cross-site replication relies on the ordering of the write operation to ensure data consistency. This ordering is provided by JGroups; it only delivers the next request after the first one is completed. > This order contains updates for multiple caches and keys. What is proposed here is to handle different keys/cache updates in parallel. > It should improve the response time, however, there is no free lunch. The following is expected: > * An increase of CPU utilization: it may spawn new threads to handle different keys update in parallel > * An increase in memory: it chains the updates (queue) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10657) Handle async-xsite in parallel

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-10657?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-10657: ------------------------------- Status: Pull Request Sent (was: Reopened) > Handle async-xsite in parallel > ------------------------------ > > Key: ISPN-10657 > URL: https://issues.redhat.com/browse/ISPN-10657 > Project: Infinispan > Issue Type: Enhancement > Components: Cross-Site Replication > Affects Versions: 10.0.0.CR2 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 9.1.8.Final, 10.0.0.Final > > > Asynchronous cross-site replication relies on the ordering of the write operation to ensure data consistency. This ordering is provided by JGroups; it only delivers the next request after the first one is completed. > This order contains updates for multiple caches and keys. What is proposed here is to handle different keys/cache updates in parallel. > It should improve the response time, however, there is no free lunch. The following is expected: > * An increase of CPU utilization: it may spawn new threads to handle different keys update in parallel > * An increase in memory: it chains the updates (queue) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10657) Handle async-xsite in parallel

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-10657?page=com.atlassian.jira.plugi... ] Pedro Ruivo reopened ISPN-10657: -------------------------------- > Handle async-xsite in parallel > ------------------------------ > > Key: ISPN-10657 > URL: https://issues.redhat.com/browse/ISPN-10657 > Project: Infinispan > Issue Type: Enhancement > Components: Cross-Site Replication > Affects Versions: 10.0.0.CR2 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 10.0.0.Final > > > Asynchronous cross-site replication relies on the ordering of the write operation to ensure data consistency. This ordering is provided by JGroups; it only delivers the next request after the first one is completed. > This order contains updates for multiple caches and keys. What is proposed here is to handle different keys/cache updates in parallel. > It should improve the response time, however, there is no free lunch. The following is expected: > * An increase of CPU utilization: it may spawn new threads to handle different keys update in parallel > * An increase in memory: it chains the updates (queue) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10657) Handle async-xsite in parallel

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-10657?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-10657: ------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/7379, https://github.com/infinispan/infinispan/pull/7790 (was: https://github.com/infinispan/infinispan/pull/7379) > Handle async-xsite in parallel > ------------------------------ > > Key: ISPN-10657 > URL: https://issues.redhat.com/browse/ISPN-10657 > Project: Infinispan > Issue Type: Enhancement > Components: Cross-Site Replication > Affects Versions: 10.0.0.CR2 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 10.0.0.Final > > > Asynchronous cross-site replication relies on the ordering of the write operation to ensure data consistency. This ordering is provided by JGroups; it only delivers the next request after the first one is completed. > This order contains updates for multiple caches and keys. What is proposed here is to handle different keys/cache updates in parallel. > It should improve the response time, however, there is no free lunch. The following is expected: > * An increase of CPU utilization: it may spawn new threads to handle different keys update in parallel > * An increase in memory: it chains the updates (queue) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9077) NullPointerException when trying to recover cache

by Johno Crawford (Jira)

[ https://issues.redhat.com/browse/ISPN-9077?page=com.atlassian.jira.plugin... ] Johno Crawford closed ISPN-9077. -------------------------------- Thanks! > NullPointerException when trying to recover cache > ------------------------------------------------- > > Key: ISPN-9077 > URL: https://issues.redhat.com/browse/ISPN-9077 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.2.0.Final > Reporter: Johno Crawford > Priority: Major > Fix For: 9.2.2.Final, 9.3.0.Final > > > {code:java} > 2018-04-13 08:34:35,065 ERROR [transport-thread-x-service-2-p4-t20] (org.infinispan.topology.ClusterCacheStatus) ISPN000228: Failed to recover cache xx state after the current node became the coordinator > java.lang.NullPointerException: null > at org.infinispan.partitionhandling.impl.PreferAvailabilityStrategy.lambda$static$0(PreferAvailabilityStrategy.java:33) ~[infinispan-core-9.2.0.Final.jar:9.2.0.Final] > at java.util.TimSort.countRunAndMakeAscending(TimSort.java:360) ~[?:1.8.0_144] > at java.util.TimSort.sort(TimSort.java:220) ~[?:1.8.0_144] > at java.util.Arrays.sort(Arrays.java:1512) ~[?:1.8.0_144] > at java.util.stream.SortedOps$SizedRefSortingSink.end(SortedOps.java:348) ~[?:1.8.0_144] > at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482) ~[?:1.8.0_144] > at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) ~[?:1.8.0_144] > at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708) ~[?:1.8.0_144] > at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) ~[?:1.8.0_144] > at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499) ~[?:1.8.0_144] > at org.infinispan.partitionhandling.impl.PreferAvailabilityStrategy.onPartitionMerge(PreferAvailabilityStrategy.java:120) ~[infinispan-core-9.2.0.Final.jar:9.2.0.Final] > at org.infinispan.topology.ClusterCacheStatus.doMergePartitions(ClusterCacheStatus.java:597) ~[infinispan-core-9.2.0.Final.jar:9.2.0.Final] > at org.infinispan.topology.ClusterTopologyManagerImpl.lambda$recoverClusterStatus$6(ClusterTopologyManagerImpl.java:519) ~[infinispan-core-9.2.0.Final.jar:9.2.0.Final] > at org.infinispan.executors.LimitedExecutor.runTasks(LimitedExecutor.java:144) [infinispan-core-9.2.0.Final.jar:9.2.0.Final] > at org.infinispan.executors.LimitedExecutor.access$100(LimitedExecutor.java:33) [infinispan-core-9.2.0.Final.jar:9.2.0.Final] > at org.infinispan.executors.LimitedExecutor$Runner.run(LimitedExecutor.java:174) [infinispan-core-9.2.0.Final.jar:9.2.0.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_144] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_144] > at java.lang.Thread.run(Thread.java:748) [?:1.8.0_144] > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7744) ServerEventLoggerTest.testLocalServerEventLogging fails intermittently

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-7744?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-7744: ----------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > ServerEventLoggerTest.testLocalServerEventLogging fails intermittently > ---------------------------------------------------------------------- > > Key: ISPN-7744 > URL: https://issues.redhat.com/browse/ISPN-7744 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Affects Versions: 9.0.0.Final > Reporter: Tristan Tarrant > Assignee: Dan Berindei > Priority: Major > Fix For: 10.1.2.Final, 11.0.0.Alpha1 > > > I got org.infinispan.server.eventlogger.ServerEventLoggerTest.testLocalServerEventLogging fail on Windows with following stacktrace: > {code} > java.lang.AssertionError: expected:<2> but was:<1> > 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:245) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:252) > at org.infinispan.server.eventlogger.ServerEventLoggerTest$1.call(ServerEventLoggerTest.java:60) > at org.infinispan.test.TestingUtil.withCacheManager(TestingUtil.java:1296) > at org.infinispan.server.eventlogger.ServerEventLoggerTest.testLocalServerEventLogging(ServerEventLoggerTest.java:43) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7744) ServerEventLoggerTest.testLocalServerEventLogging fails intermittently

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-7744?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-7744: ----------------------------- Fix Version/s: (was: 10.1.2.Final) > ServerEventLoggerTest.testLocalServerEventLogging fails intermittently > ---------------------------------------------------------------------- > > Key: ISPN-7744 > URL: https://issues.redhat.com/browse/ISPN-7744 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Affects Versions: 9.0.0.Final > Reporter: Tristan Tarrant > Assignee: Dan Berindei > Priority: Major > Fix For: 11.0.0.Alpha1 > > > I got org.infinispan.server.eventlogger.ServerEventLoggerTest.testLocalServerEventLogging fail on Windows with following stacktrace: > {code} > java.lang.AssertionError: expected:<2> but was:<1> > 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:245) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:252) > at org.infinispan.server.eventlogger.ServerEventLoggerTest$1.call(ServerEventLoggerTest.java:60) > at org.infinispan.test.TestingUtil.withCacheManager(TestingUtil.java:1296) > at org.infinispan.server.eventlogger.ServerEventLoggerTest.testLocalServerEventLogging(ServerEventLoggerTest.java:43) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-129) ProtobufUtil.fromWrappedByteArray should not create a ByteArrayInputStream

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/IPROTO-129?page=com.atlassian.jira.plugi... ] Dan Berindei updated IPROTO-129: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/protostream/pull/89 > ProtobufUtil.fromWrappedByteArray should not create a ByteArrayInputStream > -------------------------------------------------------------------------- > > Key: IPROTO-129 > URL: https://issues.redhat.com/browse/IPROTO-129 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 4.3.2.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > > {{ProtobufUtil.fromWrappedByteArray}} wraps the {{bytep[]}} in a {{ByteArrayInputStream}} and uses that as an input for {{CodedInputStream}}. But that is inefficient, because {{CodedInputStream.StreamDecoder}} needs to allocate a buffer and copy from the stream into the buffer before processing. > Instead we can pass the {{byte[]}} directly to {{CodedInputStream}} and use {{CodedInputStream.ArrayDecoder}}, which doesn't need a buffer. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2020