November 2014 - infinispan-issues

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

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3244?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3244: ----------------------------------- Fix Version/s: 7.1.0.Alpha1 (was: 7.0.0.Final) > 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 > Fix For: 7.1.0.Alpha1 > > > 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.1#6329)

10 years, 2 months

1
0
0 / 0

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

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3336?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3336: ----------------------------------- Fix Version/s: 7.1.0.Alpha1 (was: 7.0.0.Final) > 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 > Priority: Critical > Labels: core > Fix For: 7.1.0.Alpha1 > > > * 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.1#6329)

10 years, 2 months

1
0
0 / 0

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

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3273?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3273: ----------------------------------- Fix Version/s: 7.1.0.Alpha1 (was: 7.0.0.Final) > 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 > Fix For: 7.1.0.Alpha1 > > 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.1#6329)

10 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 Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3337?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3337: ----------------------------------- Fix Version/s: 7.1.0.Alpha1 (was: 7.0.0.Final) > 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 > Fix For: 7.1.0.Alpha1 > > > 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.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3344) Create a release script for ProtoStream library

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3344?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3344: ----------------------------------- Fix Version/s: 7.1.0.Alpha1 (was: 7.0.0.Final) > Create a release script for ProtoStream library > ----------------------------------------------- > > Key: ISPN-3344 > URL: https://issues.jboss.org/browse/ISPN-3344 > Project: Infinispan > Issue Type: Task > Components: Build process > Affects Versions: 6.0.0.Alpha1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.1.0.Alpha1 > > > Need to add license information and a short README to the project. Also update the 'Cutting Infinispan Releases' document with relevant details for Protostream. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3351) Controlled cluster shutdown with data restore from persistent storage

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3351?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3351: ----------------------------------- Fix Version/s: 7.1.0.Alpha1 (was: 7.0.0.Final) > Controlled cluster shutdown with data restore from persistent storage > --------------------------------------------------------------------- > > Key: ISPN-3351 > URL: https://issues.jboss.org/browse/ISPN-3351 > Project: Infinispan > Issue Type: Feature Request > Components: Core, Loaders and Stores > Reporter: Mircea Markus > Labels: roadmap > Fix For: 7.1.0.Alpha1 > > > https://community.jboss.org/wiki/ControlledClusterShutdownWithDataRestore... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3614) Add remote query quick start/demo

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3614?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3614: ----------------------------------- Fix Version/s: 7.1.0.Alpha1 (was: 7.0.0.Final) > Add remote query quick start/demo > --------------------------------- > > Key: ISPN-3614 > URL: https://issues.jboss.org/browse/ISPN-3614 > Project: Infinispan > Issue Type: Task > Components: Remote Querying > Reporter: Mircea Markus > Assignee: Adrian Nistor > Fix For: 7.1.0.Alpha1 > > > Should describe how the users: > - download the servers > - configure it (indexing ...) > - with sample domain model, how to write the marshallers, define the indexes using the RHQ plugin > - some code that connects to the server, adds and queries the data (mvn module?) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

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

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3448?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3448: ----------------------------------- Fix Version/s: 7.1.0.Alpha1 (was: 7.0.0.Final) > 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: 6.0.1.Final, 7.1.0.Alpha1 > > 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.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3621) Most CacheStore configuration examples in the documentation are wrong (outdated)

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3621?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3621: ----------------------------------- Fix Version/s: 7.1.0.Alpha1 (was: 7.0.0.Final) > Most CacheStore configuration examples in the documentation are wrong (outdated) > -------------------------------------------------------------------------------- > > Key: ISPN-3621 > URL: https://issues.jboss.org/browse/ISPN-3621 > Project: Infinispan > Issue Type: Bug > Components: Documentation-Core > Affects Versions: 6.0.0.CR1 > Reporter: Sanne Grinovero > Assignee: Mircea Markus > Fix For: 7.1.0.Alpha1 > > > I've been trying half a dozen configuration snippets from the documentation, I couldn't get any CacheStore to work. All I get from the configuration parser is an unhelpfull stack trace: > {quote} > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[50,63] > Message: Unexpected element '{urn:infinispan:config:6.0}loaders' encountered > at org.infinispan.configuration.parsing.ParseUtils.unexpectedElement(ParseUtils.java:35) > at org.infinispan.configuration.parsing.Parser60.parseCache(Parser60.java:178) > at org.infinispan.configuration.parsing.Parser60.parseNamedCache(Parser60.java:109) > at org.infinispan.configuration.parsing.Parser60.readElement(Parser60.java:76) > at org.infinispan.configuration.parsing.ParserRegistry.parseElement(ParserRegistry.java:130) > at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:112) > at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:99) > at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:86) > ... 47 more > {quote} > One might think that something (what?) is wrong at [row,col]:[50,63] but I'm copy pasting the documentation. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3622) Configuration schema is not published at documented URL

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3622?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3622: ----------------------------------- Fix Version/s: 7.1.0.Alpha1 (was: 7.0.0.Final) > Configuration schema is not published at documented URL > ------------------------------------------------------- > > Key: ISPN-3622 > URL: https://issues.jboss.org/browse/ISPN-3622 > Project: Infinispan > Issue Type: Bug > Components: Configuration, Documentation-Core > Affects Versions: 6.0.0.CR1 > Reporter: Sanne Grinovero > Assignee: Adrian Nistor > Priority: Critical > Fix For: 7.1.0.Alpha1 > > > Some examples refer to URL http://www.infinispan.org/schemas/infinispan-config-6.0.xsd to find the XSD, but it's not there. > This combined with the missing documentation makes it quite a guesswork on how to configure it. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2014