March 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3831) UnmodifiableList and UnmodifiableCollection are missing optimal Externalizers

by Ion Savin (JIRA)

[ https://issues.jboss.org/browse/ISPN-3831?page=com.atlassian.jira.plugin.... ] Ion Savin updated ISPN-3831: ---------------------------- Fix Version/s: 7.0.0.Alpha3 (was: 7.0.0.Alpha2) > UnmodifiableList and UnmodifiableCollection are missing optimal Externalizers > ----------------------------------------------------------------------------- > > Key: ISPN-3831 > URL: https://issues.jboss.org/browse/ISPN-3831 > Project: Infinispan > Issue Type: Enhancement > Components: Marshalling > Reporter: Sanne Grinovero > Assignee: Mircea Markus > Labels: 620 > Fix For: 7.0.0.Alpha3 > > > These types are widely used in Infinispan and are using a slow path for Serialization: > - class java.util.Collections$UnmodifiableList > - class java.util.Collections$UnmodifiableCollection > This degenerates in slow UTF8 decoding and significant garbage being created. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3941) Add pre-release stable version check for maven dependencies

by Ion Savin (JIRA)

[ https://issues.jboss.org/browse/ISPN-3941?page=com.atlassian.jira.plugin.... ] Ion Savin updated ISPN-3941: ---------------------------- Fix Version/s: 7.0.0.Alpha3 (was: 7.0.0.Alpha2) > Add pre-release stable version check for maven dependencies > ----------------------------------------------------------- > > Key: ISPN-3941 > URL: https://issues.jboss.org/browse/ISPN-3941 > Project: Infinispan > Issue Type: Enhancement > Components: Build process > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.0.Alpha3 > > > We need to enhance our maven build to perform the following dependecy checks before doing a release: > 1. no SNAPSHOT dependencies are used > 2. all dependencies are Final if the current build is a Final > Rule #2 might not be implementable for some external dependencies (some organizations use weird version schemes), so we might want to do this check only for org.jboss, org.infinispan artifact groups. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3907) Define a Protobuf custom option for defining numeric IDs for types

by Ion Savin (JIRA)

[ https://issues.jboss.org/browse/ISPN-3907?page=com.atlassian.jira.plugin.... ] Ion Savin updated ISPN-3907: ---------------------------- Fix Version/s: 7.0.0.Alpha3 (was: 7.0.0.Alpha2) > Define a Protobuf custom option for defining numeric IDs for types > ------------------------------------------------------------------ > > Key: ISPN-3907 > URL: https://issues.jboss.org/browse/ISPN-3907 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying > Affects Versions: 6.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.0.Alpha3, 7.0.0.Final > > > Currently the wire format of all Protobuf encoded keys and values contains a header/envelope that has some metadata information, like the fully qualified type name (that is protobuf type name, not java) of the object encoded in the message. This information is needed so that the other end can decode the message. And we added it because the Protobuf spec assumes both ends are aware of the message type, which is not the case most of the time. > While this approach solves the problem nicely, it becomes very inefficient is the FQN is long, which is usually the case, as people tend to stick the domain name of their company + package app name into it. > Solution: provide alternative unique numeric IDs to all types. The IDs can be added to message type definitions in the protobuf schema and the user is in charge of guaranteeing their uniqueness while the system must check and enforce the uniqueness when a schema is registered ib the ProtobufMetadataManager. To do this we define a custom Protobuf Message type option that accepts a numeric value. If such a numeric ID was assigned to the type then when it is serialized in protobuf the system has to use this id in the header rather that the FQN string. > This option should not be mandatory. Existing apps should work without requiring source code changes or recompiling providing that the relevant jars are upgraded in both client and server to support the new header encoding. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3936) State transfer should not modify or iterate shared cache stores

by Ion Savin (JIRA)

[ https://issues.jboss.org/browse/ISPN-3936?page=com.atlassian.jira.plugin.... ] Ion Savin updated ISPN-3936: ---------------------------- Fix Version/s: 7.0.0.Alpha3 (was: 7.0.0.Alpha2) > State transfer should not modify or iterate shared cache stores > --------------------------------------------------------------- > > Key: ISPN-3936 > URL: https://issues.jboss.org/browse/ISPN-3936 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 6.0.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Fix For: 7.0.0.Alpha3, 7.0.0.Final > > > When installing a new topology, we invalidate the cache entries that are no longer mapped to the local node. We also iterate over the entries in the cache stores and delete the ones that are no longer local, but this should only happen if the cache store is not shared. > We had similar issues in the past, but this seems to be related to the new cache store API introduced in 6.0. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3891) Tune for batching without transactions

by Ion Savin (JIRA)

[ https://issues.jboss.org/browse/ISPN-3891?page=com.atlassian.jira.plugin.... ] Ion Savin updated ISPN-3891: ---------------------------- Fix Version/s: 7.0.0.Alpha3 (was: 7.0.0.Alpha2) > Tune for batching without transactions > -------------------------------------- > > Key: ISPN-3891 > URL: https://issues.jboss.org/browse/ISPN-3891 > Project: Infinispan > Issue Type: Enhancement > Components: Transactions > Reporter: Sanne Grinovero > Assignee: Mircea Markus > Fix For: 7.0.0.Alpha3, 7.0.0.Final > > > The usage of batching is a critically important feature, widely used to improve performance in many common scenarios, but while documentation makes it clear that it's built on transactions, it's unclear how these transactions should be configured. > Also, I would challenge the decision of building batching on top of transactions and see if there are opportunities for further optimization. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3906) Do not place ProtobufValueWrapper instances in the cache

by Ion Savin (JIRA)

[ https://issues.jboss.org/browse/ISPN-3906?page=com.atlassian.jira.plugin.... ] Ion Savin updated ISPN-3906: ---------------------------- Fix Version/s: 7.0.0.Alpha3 (was: 7.0.0.Alpha2) > Do not place ProtobufValueWrapper instances in the cache > -------------------------------------------------------- > > Key: ISPN-3906 > URL: https://issues.jboss.org/browse/ISPN-3906 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying > Affects Versions: 6.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.0.Alpha3, 7.0.0.Final > > > ProtobufValueWrapper is only needed in order to provide a classbridge so we can integrate with Hibernate Search. Still, we should not need to wrap the protobuf encoded byte array put in the cache with this class. It should only be created as a temporary wrapper just before we feed the data to Hibernate Search. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3984) CompatModeDistributedTwoNodesMapReduceTest.testInvokeMapReduceOnAllKeys random failures

by Ion Savin (JIRA)

[ https://issues.jboss.org/browse/ISPN-3984?page=com.atlassian.jira.plugin.... ] Ion Savin updated ISPN-3984: ---------------------------- Fix Version/s: 7.0.0.Alpha3 (was: 7.0.0.Alpha2) > CompatModeDistributedTwoNodesMapReduceTest.testInvokeMapReduceOnAllKeys random failures > --------------------------------------------------------------------------------------- > > Key: ISPN-3984 > URL: https://issues.jboss.org/browse/ISPN-3984 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 6.0.1.Final > Reporter: Dan Berindei > Assignee: Vladimir Blagojevic > Labels: testsuite_stability > Fix For: 7.0.0.Alpha3 > > Attachments: cmdtnmrt.log.gz > > > The random failures in CompatModeDistributedTwoNodesMapReduceTest.testInvokeMapReduceOnAllKeys seem to be caused by state transfer being disabled in the test's caches. > {noformat} > 12:11:51,674 ERROR (testng-CompatModeDistributedTwoNodesMapReduceTest:) [UnitTestTestNGListener] Test testInvokeMapReduceOnAllKeys(org.infinispan.distexec.mapreduce.CompatModeDistributedTwoNodesMapReduceTest) failed. > java.lang.AssertionError: key 'well' does not have count 1 but 2 > at org.junit.Assert.fail(Assert.java:93) > at org.junit.Assert.assertTrue(Assert.java:43) > at org.infinispan.distexec.mapreduce.BaseWordCountMapReduceTest.verifyResults(BaseWordCountMapReduceTest.java:224) > at org.infinispan.distexec.mapreduce.BaseWordCountMapReduceTest.verifyResults(BaseWordCountMapReduceTest.java:334) > at org.infinispan.distexec.mapreduce.BaseWordCountMapReduceTest.testInvokeMapReduceOnAllKeys(BaseWordCountMapReduceTest.java:162) > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3983) Remove some performance bottlenecks from ProtoStream

by Ion Savin (JIRA)

[ https://issues.jboss.org/browse/ISPN-3983?page=com.atlassian.jira.plugin.... ] Ion Savin updated ISPN-3983: ---------------------------- Fix Version/s: 7.0.0.Alpha3 (was: 7.0.0.Alpha2) > Remove some performance bottlenecks from ProtoStream > ---------------------------------------------------- > > Key: ISPN-3983 > URL: https://issues.jboss.org/browse/ISPN-3983 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Affects Versions: 6.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Labels: 6.3remotequeries, 630 > Fix For: 7.0.0.Alpha3, 7.0.0.Final > > > Profiling has shown that there are many HashMaps created in MessageContext to help field lookup by name. > Normally this is a static piece of information that should be computed only once when a marshaller is registered and then it should become immutable and be reused. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3962) Upgrade to Wildfly 8.0.0.CR1

by Ion Savin (JIRA)

[ https://issues.jboss.org/browse/ISPN-3962?page=com.atlassian.jira.plugin.... ] Ion Savin updated ISPN-3962: ---------------------------- Fix Version/s: 7.0.0.Alpha3 (was: 7.0.0.Alpha2) > Upgrade to Wildfly 8.0.0.CR1 > ---------------------------- > > Key: ISPN-3962 > URL: https://issues.jboss.org/browse/ISPN-3962 > Project: Infinispan > Issue Type: Component Upgrade > Components: Test Suite - Server > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.0.0.Alpha3, 7.0.0.Final > > > Upgrade to Wildfly 8.0.0.CR1 and verify whether issues in http://lists.jboss.org/pipermail/infinispan-dev/2014-February/014478.html are gone -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3966) Enable selective TRACE logging for Infinispan Server modules

by Ion Savin (JIRA)

[ https://issues.jboss.org/browse/ISPN-3966?page=com.atlassian.jira.plugin.... ] Ion Savin updated ISPN-3966: ---------------------------- Fix Version/s: 7.0.0.Alpha3 (was: 7.0.0.Alpha2) > Enable selective TRACE logging for Infinispan Server modules > ------------------------------------------------------------ > > Key: ISPN-3966 > URL: https://issues.jboss.org/browse/ISPN-3966 > Project: Infinispan > Issue Type: Bug > Components: Server, Test Suite - Server > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.0.0.Alpha3, 7.0.0.Final > > > When running unstable tests, we should be able to take the flag used to enable TRACE logging in Infinispan core tests and apply it to the Infinispan Server configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 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 2014