December 2016 - infinispan-issues

[JBoss JIRA] (ISPN-6956) AffinityPartitioner enabled as default partitioner

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6956?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6956: ---------------------------------- Fix Version/s: 9.0.0.Beta2 (was: 9.0.0.Beta1) > AffinityPartitioner enabled as default partitioner > -------------------------------------------------- > > Key: ISPN-6956 > URL: https://issues.jboss.org/browse/ISPN-6956 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 9.0.0.Beta2, 9.0.0.Final > > > Having the {{org.infinispan.distribution.ch.impl.AffinityPartitioner}} as default enabled {{KeyPartitioner}} will allow people to use the functionality offered by {{org.infinispan.distribution.ch.AffinityTaggedKey}} out of the box, without needing to enable it explicitly in configuration. > {{AffinityTaggedKey}} is used by Query but not only. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6971) Use JChannel directly instead of going through MessageDispatcher

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6971?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6971: ---------------------------------- Fix Version/s: 9.0.0.Beta2 (was: 9.0.0.Beta1) > Use JChannel directly instead of going through MessageDispatcher > ---------------------------------------------------------------- > > Key: ISPN-6971 > URL: https://issues.jboss.org/browse/ISPN-6971 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 9.0.0.Alpha4 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 9.0.0.Beta2 > > > JGroups changed its serialization in 4.0, and even when using MessageDispatcher we still have to provide a JGroups-style marshaller for deserializing RPC responses. If we used JChannel directly, we could avoid this, and we'd have more control over how we process responses. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6798) Examples of JDBC CacheStore configuration should remind about the shared attribute

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6798?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6798: ---------------------------------- Fix Version/s: 9.0.0.Beta2 (was: 9.0.0.Beta1) > Examples of JDBC CacheStore configuration should remind about the shared attribute > ---------------------------------------------------------------------------------- > > Key: ISPN-6798 > URL: https://issues.jboss.org/browse/ISPN-6798 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Documentation-Core > Reporter: Sanne Grinovero > Priority: Minor > Fix For: 9.0.0.Beta2 > > > The "shared" configuration attribute is defaulting to _false_ even for database-based CacheStore instances as the attribute is defined in the parent of all {{CacheStore}} types. > The attribute isn't very visible either, as it's not explicitly listed among the available attributes (because it's inherited), and I think this is quite confusing as - while a non-shared configuration could be a choice - there's a strong assumption and expectation that these will point to a shared relational database. > I'd suggest to: > - add a highlighted reminder about this > - set the attribute explicitly in all example configurations > See also: > - http://stackoverflow.com/questions/37949448/duplicate-record-errors-in-hi... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6965) Throw UnsupportedOperation exceptions in RemoteCache for unimplemented methods of ConcurrentMap

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6965?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6965: ---------------------------------- Fix Version/s: 9.0.0.Beta2 (was: 9.0.0.Beta1) > Throw UnsupportedOperation exceptions in RemoteCache for unimplemented methods of ConcurrentMap > ----------------------------------------------------------------------------------------------- > > Key: ISPN-6965 > URL: https://issues.jboss.org/browse/ISPN-6965 > Project: Infinispan > Issue Type: Task > Components: Remote Protocols > Reporter: Sanne Grinovero > Fix For: 9.0.0.Beta2 > > > The {{RemoteCache}} class inherits several methods from {{ConcurrentMap}} which are not overriden and won't work as expected, or are not safe for concurrent usage. > These should at least throw an exception, and ideally be documented as not-implemented in the javadocs. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6803) Precompute a bitset for each flag

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6803?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6803: ---------------------------------- Fix Version/s: 9.0.0.Beta2 (was: 9.0.0.Beta1) > Precompute a bitset for each flag > --------------------------------- > > Key: ISPN-6803 > URL: https://issues.jboss.org/browse/ISPN-6803 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 9.0.0.Alpha2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.Beta2 > > > Commands now use keep track of flags as "bitsets" that are actually {{long}}. > However, flag checks still refer to the {{Flag}} instances themselves, and because the ordinal is not a static field, it cannot be optimized away by HotSpot. We can avoid that by precomputing a bitset for each flag, and making it {{static final}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6802) Micro-optimizations for read operations

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6802?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6802: ---------------------------------- Fix Version/s: 9.0.0.Beta2 (was: 9.0.0.Beta1) > Micro-optimizations for read operations > --------------------------------------- > > Key: ISPN-6802 > URL: https://issues.jboss.org/browse/ISPN-6802 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 9.0.0.Alpha2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.Beta2 > > > * L1 entries are written to the data container by L1TxInterceptor/L1NonTxInterceptor directly, so there is no reason to commit the context entries in EntryWrappingInterceptor or to clear the locks in the locking interceptors. > * ClearCommands can no longer be wrapped in PrepareCommands, so we can stop the state transfer in {{EntryWrappingInterceptor.visitClearCommand()}} instead of checking the type for each command. > * In transactional caches, a read operation without an explicit transaction triggers two queries for the current transaction to the transaction manager, which usually means 2 thread-local lookups. > * IsMarshallerInterceptor shouldn't do anything unless there is an asynchronous store > * Transactional remote get commands use NonTxInvocationInterceptor instead of SingleKeyNonTxInterceptor. > * Configuration attributes should be cached, as reading them requires accessing multiple instances + a cast in Attribute.get() -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6827) ReplTotalOrderVersionedStateTransferTest.testStateTransfer random failures

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6827?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6827: ---------------------------------- Fix Version/s: 9.0.0.Beta2 (was: 9.0.0.Beta1) > ReplTotalOrderVersionedStateTransferTest.testStateTransfer random failures > --------------------------------------------------------------------------- > > Key: ISPN-6827 > URL: https://issues.jboss.org/browse/ISPN-6827 > Project: Infinispan > Issue Type: Bug > Components: Core, Test Suite - Core > Affects Versions: 9.0.0.Alpha2 > Reporter: Dan Berindei > Priority: Critical > Labels: testsuite_stability > Fix For: 9.0.0.Beta2 > > Attachments: ReplTotalOrderVersionedStateTransferTest_pr_rvansa_ISPN-5989_20160314.log.zip > > > {noformat} > java.lang.RuntimeException: Timed out waiting for rebalancing to complete on node ReplTotalOrderVersionedStateTransferTest-NodeB-17608, expected member list is [ReplTotalOrderVersionedStateTransferTest-NodeB-17608, ReplTotalOrderVersionedStateTransferTest-NodeC-39826], current member list is [ReplTotalOrderVersionedStateTransferTest-NodeA-54647, ReplTotalOrderVersionedStateTransferTest-NodeB-17608, ReplTotalOrderVersionedStateTransferTest-NodeC-39826]! > at org.infinispan.test.TestingUtil.waitForRehashToComplete(TestingUtil.java:267) > at org.infinispan.test.TestingUtil.waitForRehashToComplete(TestingUtil.java:277) > at org.infinispan.container.versioning.VersionedReplStateTransferTest.testStateTransfer(VersionedReplStateTransferTest.java:74) > {noformat} > http://ci.infinispan.org/project.html?tab=testDetails&testNameId=-7264982... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6942) Listener.observation is not documented

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6942?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6942: ---------------------------------- Fix Version/s: 9.0.0.Beta2 (was: 9.0.0.Beta1) > Listener.observation is not documented > -------------------------------------- > > Key: ISPN-6942 > URL: https://issues.jboss.org/browse/ISPN-6942 > Project: Infinispan > Issue Type: Task > Components: Listeners > Reporter: William Burns > Assignee: William Burns > Fix For: 9.0.0.Beta2 > > > Listener.observation was added earlier, however it wasn't properly documented. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6688) PreferAvailabilityStrategy: Improve selection of segment owners after merge

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6688?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6688: ---------------------------------- Fix Version/s: 9.0.0.Beta2 (was: 9.0.0.Beta1) > PreferAvailabilityStrategy: Improve selection of segment owners after merge > --------------------------------------------------------------------------- > > Key: ISPN-6688 > URL: https://issues.jboss.org/browse/ISPN-6688 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.2.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.Beta2, 9.0.0.Final > > > {{PreferAvailabilityStrategy}} picks a winning CH after merge, but that CH is very likely to be the wrong one. We should improve our odds at preserving cache data by mixing CHs, and keeping from each node's response only the information about the segments it owns itself. > The downside is that {{PreferAvailabilityStrategy}} becomes tightly coupled with {{DefaultConsistentHash}}/{{ReplicatedConsistentHash}}, and users that want to add custom {{ConsistentHash}} implementations will have to re-implement {{PreferAvailabilityStrategy}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6933) Rename the jdk8backported package as its name is confusing

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6933?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6933: ---------------------------------- Fix Version/s: 9.0.0.Beta2 (was: 9.0.0.Beta1) > Rename the jdk8backported package as its name is confusing > ---------------------------------------------------------- > > Key: ISPN-6933 > URL: https://issues.jboss.org/browse/ISPN-6933 > Project: Infinispan > Issue Type: Task > Components: Core > Reporter: Sanne Grinovero > Assignee: Tristan Tarrant > Fix For: 9.0.0.Beta2 > > > As discussed on the mailing list on this thread, the package name of {{org.infinispan.commons.util.concurrent.jdk8backported.EquivalentConcurrentHashMapV8}} (and others in the same package) is confusing as people keep wondering if we should get rid of it, if it's supposed to work on JDK7, etc.. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2016