January 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3198) Allow multiple versions of entries to be stored

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3198?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-3198: ------------------------------------- Assignee: (was: Mircea Markus) > Allow multiple versions of entries to be stored > ----------------------------------------------- > > Key: ISPN-3198 > URL: https://issues.jboss.org/browse/ISPN-3198 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 5.3.0.Final > Reporter: Manik Surtani > Labels: leads, versioning > > Storing multiple versions of a given entry will pave the way for eventual consistency based on vector clocks as well as the ability for API-controlled versioning. > Will require that each entry is a structure that contains multiple actual entries ordered by version. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3198) Allow multiple versions of entries to be stored

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3198?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3198: ---------------------------------- Fix Version/s: (was: 7.1.0.CR1) > Allow multiple versions of entries to be stored > ----------------------------------------------- > > Key: ISPN-3198 > URL: https://issues.jboss.org/browse/ISPN-3198 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 5.3.0.Final > Reporter: Manik Surtani > Labels: leads, versioning > > Storing multiple versions of a given entry will pave the way for eventual consistency based on vector clocks as well as the ability for API-controlled versioning. > Will require that each entry is a structure that contains multiple actual entries ordered by version. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3199) API to manipulate multiple versions of an entry

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3199?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-3199: ------------------------------------- Assignee: (was: Mircea Markus) > API to manipulate multiple versions of an entry > ----------------------------------------------- > > Key: ISPN-3199 > URL: https://issues.jboss.org/browse/ISPN-3199 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 5.3.0.Final > Reporter: Manik Surtani > Labels: leads > > In addition to the existing API, the following will be needed to allow user applications to directly control versioning. E.g., > {code} > put(K key, EntryVersion version); > get(K key, EntryVersion version); > getLatest(K key, EntryVersion upperBound); > evict(K key, EntryVersion upTo); > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3199) API to manipulate multiple versions of an entry

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3199?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3199: ---------------------------------- Fix Version/s: (was: 7.1.0.CR1) > API to manipulate multiple versions of an entry > ----------------------------------------------- > > Key: ISPN-3199 > URL: https://issues.jboss.org/browse/ISPN-3199 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 5.3.0.Final > Reporter: Manik Surtani > Assignee: Mircea Markus > Labels: leads > > In addition to the existing API, the following will be needed to allow user applications to directly control versioning. E.g., > {code} > put(K key, EntryVersion version); > get(K key, EntryVersion version); > getLatest(K key, EntryVersion upperBound); > evict(K key, EntryVersion upTo); > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3223) HotRod 2.0 Client recieves stale toplogy view on instance leave

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3223?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3223: ---------------------------------- Fix Version/s: (was: 7.1.0.CR1) > HotRod 2.0 Client recieves stale toplogy view on instance leave > --------------------------------------------------------------- > > Key: ISPN-3223 > URL: https://issues.jboss.org/browse/ISPN-3223 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 5.2.4.Final, 5.3.0.CR1, 7.0.0.Beta1 > Reporter: Takayoshi Kimura > Assignee: Galder Zamarreño > Attachments: hr-protocol-13.log, hr-protocol-20.log > > > When killed a HotRod server node, HotRod Clinet sometimes recieves a stale toplogy view which includes the dead node and uses it as a latest view. In this case the client keeps trying to connect that node and keeps failing. > Looks like the AbstractEncoder1x.generateTopologyResponse() takes care of node join but doesn't handle node leave: > {noformat} > if (!serverEndpointsMap.keySet.containsAll(cacheMembers)) { > {noformat} > For example, serverEndpointsMap.keySet is [A, B, C] and the actual cacheMembers is [A, B]. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3244) TopologyAwareSyncConsistentHashFactory should limit the number of segments per node

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3244?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3244: ---------------------------------- Fix Version/s: (was: 7.1.0.CR1) > TopologyAwareSyncConsistentHashFactory should limit the number of segments per node > ----------------------------------------------------------------------------------- > > Key: ISPN-3244 > URL: https://issues.jboss.org/browse/ISPN-3244 > Project: Infinispan > Issue Type: Bug > Components: State Transfer > Affects Versions: 5.2.6.Final, 5.3.0.CR2 > Reporter: Dan Berindei > > Let's say we have a cluster with 5 nodes: A(r1), B(r2), C(r2), D(r3), E(r3) > TopologyAwareConsistentSyncHashFactory will spread the segments equally on each rack, meaning A will own 2x segments compared to the other nodes. > TopologyAwareConsistentHashFactory limits the maximum number per node, so that A owns just as many segments as the other nodes. With a slight limitation: the number of racks must be greater than numOwners, otherwise each rack must hold (at least) one copy of all the data. > TopologyAwareConsistentSyncHashFactory is a little random, so we can't distribute the data perfectly, but we can limit the number of segments on each node to something like 1.5x the average number of segments. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3337) Define an approach to allow the injection of Configuration and GlobalConfiguration beans for overriding

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3337?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3337: ---------------------------------- Fix Version/s: (was: 7.1.0.CR1) > Define an approach to allow the injection of Configuration and GlobalConfiguration beans for overriding > ------------------------------------------------------------------------------------------------------- > > Key: ISPN-3337 > URL: https://issues.jboss.org/browse/ISPN-3337 > Project: Infinispan > Issue Type: Feature Request > Components: Spring Integration > Reporter: Navin Surtani > Assignee: Gustavo Fernandes > > ISPN-3279 removed the ConfigurationOverrides and GlobalConfigurationOverrides classes in the Spring module. These classes contained older set() calls in order to override Cache configurations and given the way that programmatic Configuration currently works in Infinispan, that approach is not maintainable. > We hence need a clean way to provide (Global) Configuration beans as a newer, cleaner approach. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3336) Extended Statistics check list

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3336?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3336: ---------------------------------- Fix Version/s: (was: 7.1.0.CR1) > Extended Statistics check list > ------------------------------ > > Key: ISPN-3336 > URL: https://issues.jboss.org/browse/ISPN-3336 > Project: Infinispan > Issue Type: Task > Components: Core > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Labels: core > > * add documentation > * check for duplicate stats; > * check for not exposed statistics > * try to improve the code (reduce the number of access to the CHM) > * add tests to check if they are exported via JMX correctly > * failing test: OptimisticLockingTxClusterExtendedStatisticLogicTest.testWriteSkewOnNonOwner > * failing test: PessimisticLockingTxClusterExtendedStatisticLogicTest.testDeadlockOnNonOwnerWithRemoteTx -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3273) Dist L1 owners that aren't primary don't respect assumeOriginKeptEntryInL1

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3273?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3273: ---------------------------------- Fix Version/s: (was: 7.1.0.CR1) > Dist L1 owners that aren't primary don't respect assumeOriginKeptEntryInL1 > -------------------------------------------------------------------------- > > Key: ISPN-3273 > URL: https://issues.jboss.org/browse/ISPN-3273 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: William Burns > Assignee: William Burns > Attachments: DistSyncFuncTest.java > > > When a write operation occurs causing a L1 invalidation, there is a boolean to say assumeOriginKeptEntryInL1 which means the owner won't send an invalidation to the originating node that caused this update. This works fine for the primary owner, however any additional backups think the origin is the primary owner and such send invalidations to possibly the real origin. > -This affects both tx and non tx caches. Tx caches that are sync don't see the problem since locking prevents the invalidation, however it causes an unneeded network roundtrip which can cause delay.- > Actually this only affects non-tx caches, as tx caches send the prepare/commit directly to the owner(s) instead of having it relayed. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3448) Tests from org.infinispan.distribution.rehash package fail randomly

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3448?page=com.atlassian.jira.plugin.... ] Tristan Tarrant resolved ISPN-3448. ----------------------------------- Fix Version/s: 7.0.0.Final (was: 6.0.1.Final) (was: 7.1.0.CR1) Resolution: Done > Tests from org.infinispan.distribution.rehash package fail randomly > ------------------------------------------------------------------- > > Key: ISPN-3448 > URL: https://issues.jboss.org/browse/ISPN-3448 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 6.0.0.Alpha3, 6.0.0.CR1, 6.0.0.Final, 7.0.0.Alpha2, 7.0.0.Alpha3, 7.0.0.Alpha4 > Reporter: Jiří Holuša > Labels: testsuite_stability > Fix For: 7.0.0.Final > > Attachments: NonTxPutIfAbsentDuringLeaveStressTest.testNodeLeavingDuringPutIfAbsent.log.zip, NonTxStateTransferOverwritingValue2Test.log.zip, NonTxStateTransferOverwritingValue2Test.testBackupOwnerJoiningDuringPutOverwrite.log.zip, NonTxStateTransferOverwritingValue2Test.testBackupOwnerJoiningDuringRemove.log.zip, NonTxStateTransferOverwritingValue2Test.testBackupOwnerJoiningDuring{Remove, Replace}WithPreviousValue.log.zip > > > These tests are randomly failing on various platforms (RHEL, Solaris) with various JDKs. > org.infinispan.distribution.rehash.NonTxPutIfAbsentDuringLeaveStressTest.testNodeLeavingDuringPutIfAbsent > org.infinispan.distribution.rehash.NonTxJoinerBecomingBackupOwnerTest.testBackupOwnerJoiningDuringPutIfAbsent > org.infinispan.distribution.rehash.NonTxPutIfAbsentDuringJoinStressTest.testNodeJoiningDuringPutIfAbsent > org.infinispan.distribution.rehash.NonTxJoinerBecomingBackupOwnerTest.testBackupOwnerJoiningDuringPut > org.infinispan.distribution.rehash.NonTxPutIfAbsentDuringLeaveStressTest.testNodeLeavingDuringPutIfAbsent > org.infinispan.distribution.rehash.NonTxStateTransferOverwritingValue2Test.testBackupOwnerJoiningDuringRemove > org.infinispan.distribution.rehash.NonTxStateTransferOverwritingValue2Test.testBackupOwnerJoiningDuringPutOverwrite > org.infinispan.distribution.rehash.NonTxStateTransferOverwritingValue2Test.testBackupOwnerJoiningDuringRemoveWithPreviousValue > org.infinispan.distribution.rehash.NonTxStateTransferOverwritingValue2Test.testBackupOwnerJoiningDuringReplaceWithPreviousValue > org.infinispan.distribution.rehash.NonTxStateTransferOverwritingValue2Test.testBackupOwnerJoiningDuringReplace > New randomly failing test > org.infinispan.distribution.rehash.ConcurrentOverlappingLeaveTest.testNonTransactional > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 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 2015