December 2013 - infinispan-issues

[JBoss JIRA] (ISPN-3781) Memached protocol server should not start if expiration is configured

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3781?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3781: ------------------------------- Fix Version/s: (was: 6.0.1.Final) > Memached protocol server should not start if expiration is configured > --------------------------------------------------------------------- > > Key: ISPN-3781 > URL: https://issues.jboss.org/browse/ISPN-3781 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Affects Versions: 6.0.0.Final > Reporter: Tristan Tarrant > Assignee: Galder Zamarreño > Fix For: 7.0.0.Final, 7.0.0.Alpha1 > > -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3812) Java Hot Rod client should use version 1.3

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3812?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3812: ------------------------------- Fix Version/s: 7.0.0.Alpha1 (was: 6.0.1.Final) > Java Hot Rod client should use version 1.3 > ------------------------------------------ > > Key: ISPN-3812 > URL: https://issues.jboss.org/browse/ISPN-3812 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Affects Versions: 6.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.0.Alpha1 > > > The introduction of the query operation bumped version to 1.3 in server but the client still uses 1.2. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3843) Remove broadcast/unicast optimization in JGroupsTransport

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3843?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3843: ------------------------------- Fix Version/s: 7.0.0.Alpha1 (was: 6.0.1.Final) > Remove broadcast/unicast optimization in JGroupsTransport > --------------------------------------------------------- > > Key: ISPN-3843 > URL: https://issues.jboss.org/browse/ISPN-3843 > Project: Infinispan > Issue Type: Bug > Components: RPC > Affects Versions: 6.0.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 7.0.0.Alpha1 > > > The broadcast/unicast optimization in JGroupsTransport can break the message ordering for regular messages, because NAKACK[2] and UNICAST[2|3] have their own ordering. > We should test if this optimization really brings any performance benefits and eliminate it, at least for asynchronous commands. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3835) Index Update command is processed before the registry listener is triggered

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3835?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3835: ------------------------------- Fix Version/s: 7.0.0.Alpha1 (was: 6.0.1.Final) > Index Update command is processed before the registry listener is triggered > --------------------------------------------------------------------------- > > Key: ISPN-3835 > URL: https://issues.jboss.org/browse/ISPN-3835 > Project: Infinispan > Issue Type: Bug > Components: Querying > Affects Versions: 6.0.0.Final > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Critical > Fix For: 7.0.0.Alpha1 > > > When using the InfinispanIndexManager backend the master node might receive an index update command about an index which it hasn't defined yet. > Index definitions are triggered by the type registry, which in turn is driven by the ClusterRegistry and an event listener on the ClusterRegistry. It looks like slaves are sending update requests before the master has processed the configuration event. > This leads to index update commands to be lost (with a stacktrace logged) -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3834) New advanced indexing flag to skip deletion of previous entry

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3834?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3834: ------------------------------- Fix Version/s: 7.0.0.Alpha1 (was: 6.0.1.Final) > New advanced indexing flag to skip deletion of previous entry > ------------------------------------------------------------- > > Key: ISPN-3834 > URL: https://issues.jboss.org/browse/ISPN-3834 > Project: Infinispan > Issue Type: Enhancement > Components: Querying > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Labels: 620 > Fix For: 7.0.0.Alpha1 > > > I'm needing to add a org.infinispan.context.Flag.SKIP_INDEX_CLEANUP which does not issue an UPDATE index command but a simple ADD. > Just ADD is way more efficient, just we can't automatically detect it safely so I need a flag to allow for efficient data import. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3833) QueryInterceptor#updateKnownTypesIfNeeded invokes into the cluster registry too frequently

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3833?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3833: ------------------------------- Fix Version/s: 7.0.0.Alpha1 (was: 6.0.1.Final) > QueryInterceptor#updateKnownTypesIfNeeded invokes into the cluster registry too frequently > ------------------------------------------------------------------------------------------ > > Key: ISPN-3833 > URL: https://issues.jboss.org/browse/ISPN-3833 > Project: Infinispan > Issue Type: Enhancement > Components: Querying > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 7.0.0.Alpha1 > > > The QueryInterceptor should use a local cache to avoid unnecessary invocations, especially as the cluster registry is transactional this is a source of garbage generation. -- 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

11 years

1
0
0 / 0

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

by Dan Berindei (JIRA)

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

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3845) CACHE_MODE_LOCAL flag only works in primary owner for non-tx caches

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3845?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3845: ------------------------------- Fix Version/s: 7.0.0.Alpha1 (was: 6.0.1.Final) > CACHE_MODE_LOCAL flag only works in primary owner for non-tx caches > ------------------------------------------------------------------- > > Key: ISPN-3845 > URL: https://issues.jboss.org/browse/ISPN-3845 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.0.Final > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Labels: testsuite_stability > Fix For: 7.0.0.Alpha1 > > > the flag is not forcing the EntryWrappingInterceptor to wrap the entry. the result is the entry will not be stored in the cache. > It's causing the random failures in: > {noformat} > HotRodReplicationTest.testReplicatedPutWithTopologyChanges > HotRod11ReplicationTest.testReplicatedPutWithTopologyChanges > HotRod12ReplicationTest.testReplicatedPutWithTopologyChanges > {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

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3844) Cluster Registry cache does not need to provide return value for put and remove

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3844?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3844: ------------------------------- Fix Version/s: 7.0.0.Alpha1 (was: 6.0.1.Final) > Cluster Registry cache does not need to provide return value for put and remove > ------------------------------------------------------------------------------- > > Key: ISPN-3844 > URL: https://issues.jboss.org/browse/ISPN-3844 > Project: Infinispan > Issue Type: Enhancement > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Minor > Labels: 620 > Fix For: 7.0.0.Alpha1 > > > This internal registry needs to be efficient, and the return types of put and remove operations are redundant for our purposes: I'm removing them. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3841) L1NonTxInterceptor - Invalid format of log.tracef message

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3841?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3841: ------------------------------- Fix Version/s: 7.0.0.Alpha1 > L1NonTxInterceptor - Invalid format of log.tracef message > --------------------------------------------------------- > > Key: ISPN-3841 > URL: https://issues.jboss.org/browse/ISPN-3841 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.0.Final > Reporter: Mikolaj Gierulski > Assignee: Sanne Grinovero > Priority: Minor > Labels: 620 > Fix For: 6.0.1.Final, 7.0.0.Alpha1 > > > org.infinispan.interceptors.distribution.L1NonTxInterceptor.invalidateL1(InvocationContext, DataWriteCommand, boolean) invokes log.tracef with invalid message format - it contains '%', but should be '%s': > log.tracef("Not invalidating key '%' as local node(%s) is not owner", command.getKey(), rpcManager.getAddress()); -- 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

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2013