October 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3181) Retrieving entries via REST doesn't work

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-3181?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-3181: ------------------------------------ Fix Version/s: 7.0.0.Final (was: 7.0.0.CR2) > Retrieving entries via REST doesn't work > ---------------------------------------- > > Key: ISPN-3181 > URL: https://issues.jboss.org/browse/ISPN-3181 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 5.3.0.Final > Reporter: Jakub Markos > Assignee: Tristan Tarrant > Fix For: 7.0.0.Final > > Attachments: console_output.txt, server.log, standalone-dist.xml > > > Retrieving an entry stored via REST fails with 404 http response. > The test is located here: > https://code.engineering.redhat.com/gerrit/gitweb?p=jdg-functional-tests.... > {code:java} > String fullPathKey = fullPathKey(KEY_A); > post(fullPathKey, "data", "application/text"); > HttpResponse resp = get(fullPathKey, "data"); > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

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

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-3244?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-3244: ------------------------------------ Fix Version/s: 7.0.0.Final (was: 7.0.0.CR2) > 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.0.0.Final > > > 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)

11 years, 5 months

1
0
0 / 0

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

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-3273?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-3273: ------------------------------------ Fix Version/s: 7.0.0.Final (was: 7.0.0.CR2) > 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.0.0.Final > > 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)

11 years, 5 months

1
0
0 / 0

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

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-3336?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-3336: ------------------------------------ Fix Version/s: 7.0.0.Final (was: 7.0.0.CR2) > 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.0.0.Final > > > * 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)

11 years, 5 months

1
0
0 / 0

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

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-3337?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-3337: ------------------------------------ Fix Version/s: 7.0.0.Final (was: 7.0.0.CR2) > 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.0.0.Final > > > 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)

11 years, 5 months

1
0
0 / 0

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

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-3351?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-3351: ------------------------------------ Fix Version/s: (was: 7.0.0.CR2) > 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.0.0.Final > > > https://community.jboss.org/wiki/ControlledClusterShutdownWithDataRestore... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

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

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-3344?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-3344: ------------------------------------ Fix Version/s: 7.0.0.Final (was: 7.0.0.CR2) > 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.0.0.Final > > > 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)

11 years, 5 months

1
0
0 / 0

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

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-3448?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-3448: ------------------------------------ Fix Version/s: 7.0.0.Final (was: 7.0.0.CR2) > 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.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.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3450) Jon plugin - failing RebuildIndex operation on [MassIndexer] component

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-3450?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-3450: ------------------------------------ Fix Version/s: 7.0.0.Final (was: 7.0.0.CR2) > Jon plugin - failing RebuildIndex operation on [MassIndexer] component > ---------------------------------------------------------------------- > > Key: ISPN-3450 > URL: https://issues.jboss.org/browse/ISPN-3450 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Reporter: Tomas Sykora > Assignee: Adrian Nistor > Fix For: 7.0.0.Final > > > RebuildIndex operation on [MassIndexer] component is failing while issuing in JON with this error: > java.lang.NullPointerException > at org.infinispan.rhq.CacheComponent.invokeOperation(CacheComponent.java:157) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:634) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) > I reused configuration from ISPN test suite + I was able to issue this operation successfully via jconsole tool. That's why I suspect that problems are somewhere in JON-ISPN interaction or plugin. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3585) The CDI module dependency on core and hotrod client should be optional

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-3585?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-3585: ------------------------------------ Fix Version/s: 7.0.0.Final (was: 7.0.0.CR2) > The CDI module dependency on core and hotrod client should be optional > ---------------------------------------------------------------------- > > Key: ISPN-3585 > URL: https://issues.jboss.org/browse/ISPN-3585 > Project: Infinispan > Issue Type: Bug > Components: CDI Integration > Affects Versions: 6.0.0.Beta2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Critical > Labels: dm > Fix For: 7.0.0.Final > > > The CDI module Extension has a hard dependency on both core and remote. We need to refactor the code so that the two dependencies are optional and features are enabled only when found in classpath -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 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 October 2014