March 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5476) Cross-site tests should run in parallel

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5476?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5476: ------------------------------------ Fix Version/s: 8.2.0.Final (was: 8.2.0.CR1) > Cross-site tests should run in parallel > --------------------------------------- > > Key: ISPN-5476 > URL: https://issues.jboss.org/browse/ISPN-5476 > Project: Infinispan > Issue Type: Task > Components: Core, Cross-Site Replication, Test Suite - Core > Affects Versions: 7.2.1.Final > Reporter: Dan Berindei > Fix For: 8.2.0.Final > > > Currently the cross-site tests have to run in a single thread, and that means they're much slower than the regular core tests. > It also means they need to run with a separate Maven profile, and that (combined with their duration) makes it very unlikely for devs to run the xsite tests on their machines. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5475) Narayana should be configured to use a volatile store by default

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5475?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5475: ------------------------------------ Fix Version/s: 8.2.0.Final (was: 8.2.0.CR1) > Narayana should be configured to use a volatile store by default > ---------------------------------------------------------------- > > Key: ISPN-5475 > URL: https://issues.jboss.org/browse/ISPN-5475 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Core > Affects Versions: 7.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.2.0.Final > > > The {{jbossts-properties.xml}} configuration file in the core module configures a file store by default, and tests have to call {{TestCacheManagerFactory.markAsTransactional()}} (or one of the methods that calls it) to configure a volatile store instead. > Furthermore, the {{jbossts-properties.xml}} file is explicitly filtered out of the core tests jar, so other modules can't use it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5470) Remote-executor threads should not block to acquire locks

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5470?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5470: ------------------------------------ Fix Version/s: 8.2.0.Final (was: 8.2.0.CR1) > Remote-executor threads should not block to acquire locks > --------------------------------------------------------- > > Key: ISPN-5470 > URL: https://issues.jboss.org/browse/ISPN-5470 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 7.2.1.Final > Reporter: Dan Berindei > Fix For: 8.2.0.Final > > > Currently, enabling the queue on the remote-executor thread pool can cause deadlocks, because a CommitCommand/1PCPrepareCommand could end up in the queue while a remote-executor thread is busy waiting to acquire the same lock that this commit would release. > If trying to acquire a lock would free the thread until the key has been acquired, we could enable the queue on the remote-executor/OOB thread pools, and we would need a lot less threads for the same load. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5469) Remote-executor threads should not block during RPCs

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5469?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5469: ------------------------------------ Fix Version/s: 8.2.0.Final (was: 8.2.0.CR1) > Remote-executor threads should not block during RPCs > ---------------------------------------------------- > > Key: ISPN-5469 > URL: https://issues.jboss.org/browse/ISPN-5469 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 7.2.1.Final > Reporter: Dan Berindei > Fix For: 8.2.0.Final > > > This is particularly important in non-transactional caches, where the primary owner has to forward a command to the backup owners. The remote-executor thread on the primary should not be blocked while waiting for the backup responses, and instead process other commands. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5468) Change the interceptors to move the new sequential interfaces

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5468?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5468: ------------------------------------ Fix Version/s: 8.2.0.Final (was: 8.2.0.CR1) > Change the interceptors to move the new sequential interfaces > ------------------------------------------------------------- > > Key: ISPN-5468 > URL: https://issues.jboss.org/browse/ISPN-5468 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 7.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.2.0.Final > > > The first step is to move all interceptors to the new sequential interfaces, without actually allowing the command execution to be suspended and resumed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5557) Core threading redesign

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5557?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5557: ------------------------------------ Fix Version/s: 8.2.0.Final (was: 8.2.0.CR1) > Core threading redesign > ----------------------- > > Key: ISPN-5557 > URL: https://issues.jboss.org/browse/ISPN-5557 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 7.2.2.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Fix For: 8.2.0.Final > > > Infinispan needs a lot of threads, because everything is synchronous: locking, remote command invocations, cache writers. This causes various issues, from general context switching overhead to the thread pools getting full and causing deadlocks. > We should redesign the core so that most blocking happens on the application threads, and the number of internal threads is kept to a minimum. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5533) M/R DeltaAwareList can add duplicate values because of topology changes

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5533?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5533: ------------------------------------ Fix Version/s: 8.2.0.Final (was: 8.2.0.CR1) > M/R DeltaAwareList can add duplicate values because of topology changes > ----------------------------------------------------------------------- > > Key: ISPN-5533 > URL: https://issues.jboss.org/browse/ISPN-5533 > Project: Infinispan > Issue Type: Bug > Components: Core, Distributed Execution and Map/Reduce > Affects Versions: 7.2.2.Final, 8.0.0.Alpha1 > Reporter: Dan Berindei > Fix For: 8.2.0.Final > > > By default, the intermediate cache is non-transactional, so a topology change will cause write commands to be retried. Because a {{PutKeyValueCommand(K, DeltaAwareList)}} command is not idempotent, a retried command will append extra intermediate values to the list. > The M/R framework tries to guard against this by waiting for all the nodes to initialize the intermediate cache before starting the reduce phase, but it cannot guard against nodes joining or leaving during the reduce phase. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5530) AtomicObjectFactoryTest.distributedCacheTest random failures

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5530?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5530: ------------------------------------ Fix Version/s: 8.2.0.Final (was: 8.2.0.CR1) > AtomicObjectFactoryTest.distributedCacheTest random failures > ------------------------------------------------------------ > > Key: ISPN-5530 > URL: https://issues.jboss.org/browse/ISPN-5530 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 7.2.2.Final, 8.0.0.Alpha1 > Reporter: Dan Berindei > Assignee: Tristan Tarrant > Priority: Blocker > Labels: testsuite_stability > Fix For: 8.2.0.Final > > > {noformat} > java.lang.AssertionError: obtained = 999; espected = 1000 expected:<1000> but was:<999> > 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.infinispan.atomic.AtomicObjectFactoryTest.distributedCacheTest(AtomicObjectFactoryTest.java:114) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:348) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:38) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:382) > at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5521) Upgrade to Hibernate ORM 5.0.1.Final

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5521?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5521: ------------------------------------ Fix Version/s: 8.2.0.Final (was: 8.2.0.CR1) > Upgrade to Hibernate ORM 5.0.1.Final > ------------------------------------ > > Key: ISPN-5521 > URL: https://issues.jboss.org/browse/ISPN-5521 > Project: Infinispan > Issue Type: Component Upgrade > Components: Loaders and Stores > Reporter: Sanne Grinovero > Assignee: Tristan Tarrant > Fix For: 8.2.0.Final > > > I'm opening this to make sure we keep Infinispan aligned with the other platforms, now moving to Hibernate 5. > This affects at least the JPA CacheStore, I'm not sure if other components. > Among many improvements, noticeable for Infinispan there is better OSGi support. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5515) Purge store if there is another node already running

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5515?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5515: ------------------------------------ Fix Version/s: 8.2.0.Final (was: 8.2.0.CR1) > Purge store if there is another node already running > ---------------------------------------------------- > > Key: ISPN-5515 > URL: https://issues.jboss.org/browse/ISPN-5515 > Project: Infinispan > Issue Type: Enhancement > Components: Core, Loaders and Stores > Affects Versions: 7.2.2.Final, 8.0.0.Alpha1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.2.0.Final > > > Preloading happens before communicating with other nodes that might already have the cache running. When joining the existing members, the cache then waits to receive the first CH in which it is a member, and then deletes only the entries in the segments that it doesn't own in that CH. > The intention of this was to remove as little as possible from the existing data, e.g. if the first node to start up is not the one that was stopped last. But the preloaded entries are not replicated to the other nodes, so this can lead to inconsistencies. > It would be better to delay preloading until we know we are the first node to start up, but failing that we could clear the data container and the store before receiving the initial state. > Note that this will only allow preloading data from one node. Restoring data from more nodes is harder to do, and we will implement it as part of graceful restart. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2016