January 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6639) Implement multi-tenancy for Memcached

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6639?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6639: ----------------------------------- Fix Version/s: 9.0.0.Beta3 (was: 9.0.0.Beta2) > Implement multi-tenancy for Memcached > ------------------------------------- > > Key: ISPN-6639 > URL: https://issues.jboss.org/browse/ISPN-6639 > Project: Infinispan > Issue Type: Sub-task > Components: Server > Reporter: Sebastian Łaskawiec > Priority: Optional > Fix For: 9.0.0.Beta3 > > > Currently this implementation is out of scope. Please vote for it if you'd like it to be implemented. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

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

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6688?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6688: ----------------------------------- Fix Version/s: 9.0.0.Beta3 (was: 9.0.0.Beta2) > 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.Beta3, 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6766) hot rod client: RemoteCache.removeClient method does not remove the listener from the list after server restart

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6766?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6766: ----------------------------------- Fix Version/s: 9.0.0.Beta3 (was: 9.0.0.Beta2) > hot rod client: RemoteCache.removeClient method does not remove the listener from the list after server restart > --------------------------------------------------------------------------------------------------------------- > > Key: ISPN-6766 > URL: https://issues.jboss.org/browse/ISPN-6766 > Project: Infinispan > Issue Type: Bug > Components: Listeners, Remote Protocols > Affects Versions: 8.2.1.Final > Reporter: Eli Z > Priority: Minor > Fix For: 9.0.0.Beta3 > > > After registering a client listener in the client and then restarting the infinispan server --> The original listener object can not be removed from the client listener list by using the method RemoteCache.removeClient(Object listener) --> after calling this method and then get all listeners, i still see the old listener in the list. > By doing a little debug, it seems that in class RemoveClientListenerOperation.execute when trying to remove from the server and a failure status is returned (probably due to the fact the the server after the restart does not know this listener id) the listener is not removed from the list eventually. the line this.listenerNotifier.removeClientListener(listenerId); is not executed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6724) Modules scripting and infinispan directory provider use the same logging id range

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6724?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6724: ----------------------------------- Fix Version/s: 9.0.0.Beta3 (was: 9.0.0.Beta2) > Modules scripting and infinispan directory provider use the same logging id range > --------------------------------------------------------------------------------- > > Key: ISPN-6724 > URL: https://issues.jboss.org/browse/ISPN-6724 > Project: Infinispan > Issue Type: Bug > Reporter: Adrian Nistor > Fix For: 9.0.0.Beta3, 9.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6819) SharedStoreInvalidationDuringRehashTest.testRehashWith[out]Preload random failures

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6819?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6819: ----------------------------------- Fix Version/s: 9.0.0.Beta3 (was: 9.0.0.Beta2) > SharedStoreInvalidationDuringRehashTest.testRehashWith[out]Preload random failures > ---------------------------------------------------------------------------------- > > Key: ISPN-6819 > URL: https://issues.jboss.org/browse/ISPN-6819 > Project: Infinispan > Issue Type: Bug > Components: Core, Test Suite - Core > Affects Versions: 9.0.0.Alpha2, 8.2.4.Final > Reporter: Dan Berindei > Priority: Critical > Labels: testsuite_stability > Fix For: 9.0.0.Beta3 > > > {noformat} > java.lang.AssertionError: expected:<0> but was:<3> > 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.distribution.rehash.SharedStoreInvalidationDuringRehashTest.checkContentAndInvalidations(SharedStoreInvalidationDuringRehashTest.java:213) > at org.infinispan.distribution.rehash.SharedStoreInvalidationDuringRehashTest.doTest(SharedStoreInvalidationDuringRehashTest.java:135) > at org.infinispan.distribution.rehash.SharedStoreInvalidationDuringRehashTest.testRehashWithoutPreload(SharedStoreInvalidationDuringRehashTest.java:122) > {noformat} > http://ci.infinispan.org/project.html?tab=testDetails&testNameId=-7068250... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

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

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6798?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6798: ----------------------------------- Fix Version/s: 9.0.0.Beta3 (was: 9.0.0.Beta2) > 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.Beta3 > > > 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, 2 months

1
0
0 / 0

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

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6827?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6827: ----------------------------------- Fix Version/s: 9.0.0.Beta3 (was: 9.0.0.Beta2) > 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.Beta3 > > 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, 2 months

1
0
0 / 0

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

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6933?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6933: ----------------------------------- Fix Version/s: 9.0.0.Beta3 (was: 9.0.0.Beta2) > 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.Beta3 > > > 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, 2 months

1
0
0 / 0

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

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6942?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6942: ----------------------------------- Fix Version/s: 9.0.0.Beta3 (was: 9.0.0.Beta2) > 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.Beta3 > > > Listener.observation was added earlier, however it wasn't properly documented. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

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

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6956?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6956: ----------------------------------- Fix Version/s: 9.0.0.Beta3 (was: 9.0.0.Beta2) > 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.Beta3, 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, 2 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 January 2017