February 2014 - infinispan-issues

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

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3907?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3907: ------------------------------- Fix Version/s: 7.0.0.Alpha2 (was: 7.0.0.Alpha1) > 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.Final, 7.0.0.Alpha2 > > > 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 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3866) Parser60.parseStore() ignores store configurations if they are not a SingleFileStore or a ClusterLoader

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3866?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3866: ------------------------------- Fix Version/s: 7.0.0.Alpha2 (was: 7.0.0.Alpha1) > Parser60.parseStore() ignores store configurations if they are not a SingleFileStore or a ClusterLoader > ------------------------------------------------------------------------------------------------------- > > Key: ISPN-3866 > URL: https://issues.jboss.org/browse/ISPN-3866 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Affects Versions: 6.0.1.Final > Reporter: Guillermo GARCIA OCHOA > Assignee: Tristan Tarrant > Priority: Critical > Fix For: 7.0.0.Alpha2 > > > The {{Parser60.parseStore()}} methods ignores all store definition that is not a {{SingleFileStore}} or a {{ClusterLoader}} > {code:java} > private void parseStore(final XMLExtendedStreamReader reader, final ConfigurationBuilderHolder holder) throws XMLStreamException { > ConfigurationBuilder builder = holder.getCurrentConfigurationBuilder(); > CacheLoader store = null; > Boolean fetchPersistentState = null; > Boolean ignoreModifications = null; > Boolean purgeOnStartup = null; > Boolean preload = null; > Boolean shared = null; > // Here it reads the attributes that the AbstractStoreConfiguration defines > for (int i = 0; i < reader.getAttributeCount(); i++) { > ParseUtils.requireNoNamespaceAttribute(reader, i); > String value = replaceProperties(reader.getAttributeValue(i)); > Attribute attribute = Attribute.forName(reader.getAttributeLocalName(i)); > ... > } > // Then it will use the read attributes (and parse the childrens tags) > // if and only if the configure store is a SingleFileStore or ClusterLoader > if (store != null) { > if (store instanceof SingleFileStore) { > ... > parseStoreChildren(reader, sfs); > } else if (store instanceof ClusterLoader) { > ... > parseLoaderChildren(reader, cscb); > } > } > } > {code} > This means that there is no way to set a configuration to my custom cache store with the default parser {{Parser60}}. > If there is another way to what I'm asking for, please let me know because in the documentation only refers to the {{SingleFileStore}} implementation. -- 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 month

1
0
0 / 0

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

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3984?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3984: ------------------------------- Fix Version/s: 7.0.0.Alpha2 (was: 7.0.0.Alpha1) > 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.Alpha2 > > 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 month

1
0
0 / 0

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

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3983?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3983: ------------------------------- Fix Version/s: 7.0.0.Alpha2 (was: 7.0.0.Alpha1) > 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.Final, 7.0.0.Alpha2 > > > 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 month

1
0
0 / 0

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

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3941?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3941: ------------------------------- Fix Version/s: 7.0.0.Alpha2 (was: 7.0.0.Alpha1) > 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.Alpha2 > > > 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 month

1
0
0 / 0

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

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3962?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3962: ------------------------------- Fix Version/s: 7.0.0.Alpha2 (was: 7.0.0.Alpha1) > 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.Final, 7.0.0.Alpha2 > > > 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 month

1
0
0 / 0

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

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3966?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3966: ------------------------------- Fix Version/s: 7.0.0.Alpha2 (was: 7.0.0.Alpha1) > 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.Final, 7.0.0.Alpha2 > > > 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 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3942) HotRod client keep trying recover a connection to a cluster member after shutdown

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3942?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3942: ------------------------------- Fix Version/s: 7.0.0.Alpha2 (was: 7.0.0.Alpha1) > HotRod client keep trying recover a connection to a cluster member after shutdown > --------------------------------------------------------------------------------- > > Key: ISPN-3942 > URL: https://issues.jboss.org/browse/ISPN-3942 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 6.0.1.Final, 7.0.0.Alpha1 > Environment: Infinispan server with HotRod client in server-client mode and replicated caches. > Reporter: Wolf-Dieter Fink > Assignee: Pedro Ruivo > Priority: Critical > Labels: clustered, hotrod, hotrod-java-client > Fix For: 7.0.0.Final, 7.0.0.Alpha2 > > Attachments: hotrod-client.log > > > If a HotRod client is connected to a server cluster and one of the servers do a correct shutdown, the client keep try to reconnect the server after the cluster view has changed. > There is only a replicated cache configured. > From the server-logfile the new cluster view is established > 16:00:22,290 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-3,shared=udp) ISPN000094: Received new cluster view: [node1/clustered|2] (1) [node1/clustered] > There is no failure from the application perspective, but there there is always a retry if the RoundRobin return the unavailable server. > This might end in a performance or failure issue if there is a larger cluster and a part going out of work for some reason. -- 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 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3994) IntegrationTest.testAsyncAddRemove fails randomly

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3994?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3994: ------------------------------- Fix Version/s: 7.0.0.Alpha2 (was: 7.0.0.Alpha1) > IntegrationTest.testAsyncAddRemove fails randomly > ------------------------------------------------- > > Key: ISPN-3994 > URL: https://issues.jboss.org/browse/ISPN-3994 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 6.0.1.Final > Reporter: Pedro Ruivo > Assignee: Mircea Markus > Labels: testsuite_stability > Fix For: 7.0.0.Final, 7.0.0.Alpha2 > > > org.infinispan.rest.IntegrationTest.testAsyncAddRemove > http://ci.infinispan.org/viewLog.html?buildId=6518&tab=buildResultsDiv&bu... -- 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 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3991) DistSyncTx1PCL1FuncTest.testBackupOwnerInvalidatesL1WhenPrimaryIsUnaware fails randomly

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3991?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3991: ------------------------------- Fix Version/s: 7.0.0.Alpha2 (was: 7.0.0.Alpha1) > DistSyncTx1PCL1FuncTest.testBackupOwnerInvalidatesL1WhenPrimaryIsUnaware fails randomly > --------------------------------------------------------------------------------------- > > Key: ISPN-3991 > URL: https://issues.jboss.org/browse/ISPN-3991 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 6.0.1.Final > Reporter: Pedro Ruivo > Assignee: Dan Berindei > Labels: testsuite_stability > Fix For: 7.0.0.Final, 7.0.0.Alpha2 > > > org.infinispan.distribution.DistSyncTx1PCL1FuncTest.testBackupOwnerInvalidatesL1WhenPrimaryIsUnaware > http://ci.infinispan.org/viewLog.html?buildId=5960&tab=buildResultsDiv&bu... -- 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 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2014