February 2014 - infinispan-issues

[JBoss JIRA] (ISPN-4021) Allow each Map/Reduce task to use a different cache configuration

by Dan Berindei (JIRA)

Dan Berindei created ISPN-4021: ---------------------------------- Summary: Allow each Map/Reduce task to use a different cache configuration Key: ISPN-4021 URL: https://issues.jboss.org/browse/ISPN-4021 Project: Infinispan Issue Type: Feature Request Components: Core, Distributed Execution and Map/Reduce Affects Versions: 6.0.1.Final Reporter: Dan Berindei Assignee: Vladimir Blagojevic Fix For: 7.0.0.Final Some Map/Reduce tasks may need a cache store and eviction, some may not. Each task should be able to use its own cache configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3915) Upgrade to Netty 4.x

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3915?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3915: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2385 > Upgrade to Netty 4.x > -------------------- > > Key: ISPN-3915 > URL: https://issues.jboss.org/browse/ISPN-3915 > Project: Infinispan > Issue Type: Component Upgrade > Components: Server > Reporter: Galder Zamarreño > Assignee: Norman Maurer > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > Upgrade to latest Netty 4.x version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3915) Upgrade to Netty 4.x

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3915?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3915: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Upgrade to Netty 4.x > -------------------- > > Key: ISPN-3915 > URL: https://issues.jboss.org/browse/ISPN-3915 > Project: Infinispan > Issue Type: Component Upgrade > Components: Server > Reporter: Galder Zamarreño > Assignee: Norman Maurer > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > Upgrade to latest Netty 4.x version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-4010) Allow configuring the LevelDB cache store through JON

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-4010?page=com.atlassian.jira.plugin.... ] Work on ISPN-4010 started by William Burns. > Allow configuring the LevelDB cache store through JON > ----------------------------------------------------- > > Key: ISPN-4010 > URL: https://issues.jboss.org/browse/ISPN-4010 > Project: Infinispan > Issue Type: Feature Request > Reporter: Mircea Markus > Assignee: William Burns > Labels: 630 > > Although a JON console can create a cache, the JON can not set a levelDB store configuration. Our customer wants to set a levelDB store setting using the JON when creating the cache. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-4018) Write skew should not be check if conditional operations does not change the value

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-4018?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-4018: ------------------------------ Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/2391 > Write skew should not be check if conditional operations does not change the value > ---------------------------------------------------------------------------------- > > Key: ISPN-4018 > URL: https://issues.jboss.org/browse/ISPN-4018 > Project: Infinispan > Issue Type: Bug > Components: Core, Transactions > Affects Versions: 6.0.1.Final > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > Currently, if a conditional operation does no perform the update, we still perform the check. however, the write never happened. It simple makes no sense. > However, if a write succeeds after, the write skew check must be performed for the key. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2780) org.infinispan.lucene.cacheloader.IndexCacheLoaderTest.readExistingIndexTest fails randomly on all environments

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-2780?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on ISPN-2780: --------------------------------------- We recently resolved a similar issue. Is this still happening? > org.infinispan.lucene.cacheloader.IndexCacheLoaderTest.readExistingIndexTest fails randomly on all environments > --------------------------------------------------------------------------------------------------------------- > > Key: ISPN-2780 > URL: https://issues.jboss.org/browse/ISPN-2780 > Project: Infinispan > Issue Type: Bug > Components: Lucene Directory > Affects Versions: 5.2.0.CR3 > Reporter: Anna Manukyan > Assignee: Sanne Grinovero > Priority: Critical > Labels: retest, stable_embedded_query, testsuite_stability > > The test org.infinispan.lucene.cacheloader.IndexCacheLoaderTest.readExistingIndexTest fails almost always on all environments. The error message is: > {code} > Error Message > String '0' should exist but was not found in index > Stacktrace > java.lang.AssertionError: String '0' should exist but was not found in index > at org.infinispan.lucene.cacheloader.IndexCacheLoaderTest.verifyOnDirectory(IndexCacheLoaderTest.java:131) > at org.infinispan.lucene.cacheloader.IndexCacheLoaderTest.verifyIndex(IndexCacheLoaderTest.java:83) > at org.infinispan.lucene.cacheloader.IndexCacheLoaderTest.readExistingIndexTest(IndexCacheLoaderTest.java:71) > 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.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:715) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237) > 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:334) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:37) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368) > at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64) > 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) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2905) StateTransferLockImpl.waitForTransactionData should be able to time-out

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2905?page=com.atlassian.jira.plugin.... ] Dan Berindei resolved ISPN-2905. -------------------------------- Fix Version/s: 6.0.0.Final Resolution: Done > StateTransferLockImpl.waitForTransactionData should be able to time-out > ----------------------------------------------------------------------- > > Key: ISPN-2905 > URL: https://issues.jboss.org/browse/ISPN-2905 > Project: Infinispan > Issue Type: Feature Request > Components: Test Suite - Core > Affects Versions: 5.2.4.Final > Reporter: Radim Vansa > Assignee: Dan Berindei > Fix For: 6.0.0.Final > > > During a topology change a lot of threads can get stuck in {{StateTransferLockImpl.waitForTransactionData}} indefinitely, due to ISPN-2808 fill up the OOB threadpool and block the topology change. > These operations should timeout after a period. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-4020) Write a test for map/reduce with passivation enabled

by Dan Berindei (JIRA)

Dan Berindei created ISPN-4020: ---------------------------------- Summary: Write a test for map/reduce with passivation enabled Key: ISPN-4020 URL: https://issues.jboss.org/browse/ISPN-4020 Project: Infinispan Issue Type: Task Components: Distributed Execution and Map/Reduce, Test Suite - Core Reporter: Dan Berindei Assignee: Vladimir Blagojevic Fix For: 7.0.0.Final If an entry is activated (i.e. removed from the store) during the mapping phase, between the iteration of the data container and the iteration of the cache store, it may be possible for that entry to be skipped. We need to write a test to confirm if this is the case. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-4019) Write a test with a node joining/leaving during a map/reduce task

by Dan Berindei (JIRA)

Dan Berindei created ISPN-4019: ---------------------------------- Summary: Write a test with a node joining/leaving during a map/reduce task Key: ISPN-4019 URL: https://issues.jboss.org/browse/ISPN-4019 Project: Infinispan Issue Type: Task Components: Distributed Execution and Map/Reduce, Test Suite - Core Reporter: Dan Berindei Assignee: Vladimir Blagojevic Fix For: 7.0.0.Final We should have a test to confirm that the M/R results do not change if a node joins/leaves during each of the map/combine/distributed reduce phases. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-4018) Write skew should not be check if conditional operations does not change the value

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-4018?page=com.atlassian.jira.plugin.... ] Work on ISPN-4018 started by Pedro Ruivo. > Write skew should not be check if conditional operations does not change the value > ---------------------------------------------------------------------------------- > > Key: ISPN-4018 > URL: https://issues.jboss.org/browse/ISPN-4018 > Project: Infinispan > Issue Type: Bug > Components: Core, Transactions > Affects Versions: 6.0.1.Final > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > Currently, if a conditional operation does no perform the update, we still perform the check. however, the write never happened. It simple makes no sense. > However, if a write succeeds after, the write skew check must be performed for the key. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2014