January 2015 - infinispan-issues - Jboss List Archives

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

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3351?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3351: ---------------------------------- Fix Version/s: 7.1.0.CR1 (was: 7.1.0.Beta1) > 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.CR1 > > > https://community.jboss.org/wiki/ControlledClusterShutdownWithDataRestore... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

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

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3344?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3344: ---------------------------------- Fix Version/s: 7.1.0.CR1 (was: 7.1.0.Beta1) > 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.CR1 > > > 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.11#6341)

11 years, 3 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 updated ISPN-3448: ---------------------------------- Fix Version/s: 7.1.0.CR1 (was: 7.1.0.Beta1) > 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.CR1 > > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3664) Improve write command processing

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3664?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3664: ---------------------------------- Fix Version/s: 7.1.0.CR1 (was: 7.1.0.Beta1) > Improve write command processing > -------------------------------- > > Key: ISPN-3664 > URL: https://issues.jboss.org/browse/ISPN-3664 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 6.0.0.CR1 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 7.1.0.CR1 > > > Major refactorization of the write command with the following goals: > -> Base WriteCommand: all the write command has the same workflow through the interceptor chain > -> Create a concrete WriteCommand for each operation (put, remove, replace, replaceIfEquals, removeIfEquals, putIfAbsent) > -> Extend the interceptor chain to process each one of the command and add a new "visitWriteCommand", that is invoked by the default visitX methods. > -> (minor) change the GetKeyValueCommand to ReadCommand to make name "compatible" with WriteCommand. > Note that most of the interceptor only needs to implement the visitWriteCommand because all the write command has the same execution flow. The basic flow of the write commands are: (non-tx) lock, fetch value (cachestore/remote), check condition and apply change. for tx mode, lock (if pessimistic), fetch value (cache loader, remote, etc), apply change and add it to the transaction (if successful) > Also, another advantage is the simplification of the EntryFactory because if we think a little about it, independent of the write command we need to wrap the entry anyway. > Suggested implementation > {code:java} > class abstract WriteCommand > Object key, Object newValue > boolen match(Object currentValue) //true by default > boolean needsRemoteGetBeforeWrite() //true by default > object perform() //common implementation like: if (match(entry.getValue()) then entry.setValue(newValue); entry.setChanged(true); entry.setRemoved(newValue == null)} > {code} > * Concrete implementations* > {code:java} > {PutCommand|RemoveCommand} extends WriteCommand > ovewrite needsRemoteGetBeforeWrite() {return !flags.contains(IGNORE_RETURN_VALUE)} > ReplaceIfPresentCommand extends WriteCommand > ovewrite match(Object currentValue) {return currentValue != null} > PutIfAbsentCommand extends WriteCommand > ovewrite match(Object currentValue) {return currentValue == null} > {code} > * Special base class for operation with expected value to compare* > {code:java} > class abstract AdvancedWriteCommand extends WriteCommand > Object expectedValue > match(Object currentValue) {return currentValue.equals(expectedValue)} > {RemoveIfEquals|ReplaceIfEquals} extends AdvancedWriteCommand //no different implementation needed. > {code} > ps: I'm going to open the discussion in the dev mailing list... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3667) Existing cacher stores should be generic types

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3667?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3667: ---------------------------------- Fix Version/s: 7.1.0.CR1 (was: 7.1.0.Beta1) > Existing cacher stores should be generic types > ---------------------------------------------- > > Key: ISPN-3667 > URL: https://issues.jboss.org/browse/ISPN-3667 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 6.0.0.CR1 > Reporter: Mircea Markus > Assignee: Mircea Markus > Labels: dm > Fix For: 7.1.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3650) Test of org.infinispan.persistence.rest fail randomly on all environments

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3650?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3650: ---------------------------------- Fix Version/s: 7.1.0.CR1 (was: 7.1.0.Beta1) > Test of org.infinispan.persistence.rest fail randomly on all environments > ------------------------------------------------------------------------- > > Key: ISPN-3650 > URL: https://issues.jboss.org/browse/ISPN-3650 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores, Test Suite - Core > Affects Versions: 6.0.0.CR1, 6.0.0.Final > Environment: Windows && Solaris && RHEL > Reporter: Anna Manukyan > Assignee: Galder Zamarreño > Labels: testsuite_stability > Fix For: 7.1.0.CR1 > > Attachments: rest-trace-infinispan.log.zip, traces_rhel.zip > > > The tests of the package org.infinispan.persistence.rest fail periodically on Windows and Solaris and RHEL machines. > * Tests wich fail most likely > >>> org.infinispan.persistence.rest.RestStoreParallelIterationTest.testCancelingTaskMultipleProcessors > >>> org.infinispan.persistence.rest.RestStoreParallelIterationTest.testSequentialIteration > >>> org.infinispan.persistence.rest.RestStoreParallelIterationTest.testParallelIteration > >>> org.infinispan.persistence.rest.RestCacheStoreFunctionalTest.testRestoreTransactionalAtomicMap > >>> org.infinispan.persistence.rest.RestStoreParallelIterationTest.clearContent > You can find the log attached. > * Jenkins job for RHEL could be found here > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... > * Jenkins job for Windows > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3624) Rewrite documentation on load testing Infinispan Servers

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3624?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3624: ---------------------------------- Fix Version/s: 7.1.0.CR1 (was: 7.1.0.Beta1) > Rewrite documentation on load testing Infinispan Servers > -------------------------------------------------------- > > Key: ISPN-3624 > URL: https://issues.jboss.org/browse/ISPN-3624 > Project: Infinispan > Issue Type: Task > Components: Documentation-Core > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.1.0.CR1 > > > The current documentation in http://infinispan.org/docs/6.0.x/user_guide/user_guide.html#sid-68355066 is outdated. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

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

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3621?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3621: ---------------------------------- Fix Version/s: 7.1.0.CR1 (was: 7.1.0.Beta1) > 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.CR1 > > > 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.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3769) Disallow async marshalling when the replication queue is enabled

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3769?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3769: ---------------------------------- Fix Version/s: 7.1.0.CR1 (was: 7.1.0.Beta1) > Disallow async marshalling when the replication queue is enabled > ---------------------------------------------------------------- > > Key: ISPN-3769 > URL: https://issues.jboss.org/browse/ISPN-3769 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 6.0.0.Final > Reporter: Dan Berindei > Assignee: Mircea Markus > Fix For: 7.1.0.CR1 > > > The rationale is similar to ISPN-2939, the async marshalling option can cause inconsistencies because it can reorder commands. > But the case is stronger when the replication queue is in use, because the {{RpcManager.invokeRemotely()}} call already happens on a the replication queue's background thread. The user thread is already free to do its thing, so there isn't any reason to do the RPC on yet another background thread. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3743) Silence "IllegalStateException: Default cache is in 'STOPPING' state" exceptions

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3743?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3743: ---------------------------------- Fix Version/s: 7.1.0.CR1 (was: 7.1.0.Beta1) > Silence "IllegalStateException: Default cache is in 'STOPPING' state" exceptions > -------------------------------------------------------------------------------- > > Key: ISPN-3743 > URL: https://issues.jboss.org/browse/ISPN-3743 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 6.0.0.Final > Reporter: Dan Berindei > Labels: testsuite_stability > Fix For: 7.1.0.CR1 > > > When a cache in STOPPING state receives a command, the exception is propagated all the way to the caller: > {noformat} > 09:33:02,005 ERROR (testng-NonTxPutIfAbsentDuringLeaveStressTest:) [UnitTestTestNGListener] Test testNodeLeavingDuringPutIfAbsent(org.infinispan.distribution.rehash.NonTxPutIfAbsentDuringLeaveStressTest) failed. > java.util.concurrent.ExecutionException: org.infinispan.remoting.RemoteException: ISPN000217: Received exception from NodeC-25987, see cause for remote stack trace > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > Caused by: org.infinispan.remoting.RemoteException: ISPN000217: Received exception from NodeC-25987, see cause for remote stack trace > at org.infinispan.remoting.transport.AbstractTransport.checkResponse(AbstractTransport.java:41) > Caused by: org.infinispan.remoting.RemoteException: ISPN000217: Received exception from NodeD-57301, see cause for remote stack trace > at org.infinispan.remoting.transport.AbstractTransport.checkResponse(AbstractTransport.java:41) > Caused by: java.lang.IllegalStateException: Default cache is in 'STOPPING' state and this is an invocation not belonging to an on-going transaction, so it does not accept new invocations. Either restart it or recreate the cache container. > at org.infinispan.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:93) > {noformat} > This causes random failures in NonTxPutIfAbsentDuringLeaveStressTest.testNodeLeavingDuringPutIfAbsent. > The originator should either ignore the IllegalStateException or wait for a new cache topology and retry the operation, just like it should for SuspectExceptions (ISPN-2577). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 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