February 2017 - infinispan-issues

[JBoss JIRA] (ISPN-5575) Shared write-behind store can read stale entries on joiner

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-5575?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-5575: ------------------------------ Fix Version/s: 9.0.0.CR3 (was: 9.0.0.CR2) > Shared write-behind store can read stale entries on joiner > ---------------------------------------------------------- > > Key: ISPN-5575 > URL: https://issues.jboss.org/browse/ISPN-5575 > Project: Infinispan > Issue Type: Bug > Components: Core, Loaders and Stores > Affects Versions: 8.0.0.Alpha2, 7.2.3.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.CR3 > > > The AsyncCacheWriter modification queue is not sent with state transfer when the store is shared. A joiner can then read from the shared store a stale version of entries that have updates in the modification queue but are no longer in memory (because they were either removed explicitly, or evicted). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5574) Define high-level cache capabilities

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-5574?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-5574: ------------------------------ Fix Version/s: 9.0.0.CR3 (was: 9.0.0.CR2) > Define high-level cache capabilities > ------------------------------------ > > Key: ISPN-5574 > URL: https://issues.jboss.org/browse/ISPN-5574 > Project: Infinispan > Issue Type: Feature Request > Components: Configuration, Core > Affects Versions: 7.2.3.Final > Reporter: Dan Berindei > Priority: Minor > Fix For: 9.0.0.CR3 > > > Infinispan's configuration is very flexible, and it's sometimes hard to figure out how different settings affect things like cache consistency. > For example, the lucene-directory module uses the fairly complicated {{Configurations.noDataLossOnJoiner()}} method to validate that a cache is safe for storing lucene indexes. > Another example is users who would like to use a store for backup, but they don't want read from the store for M/R tasks or when get(k) doesn't find the key in memory. > One idea would be to define a set of "capabilities" like "state-transfer-complete" or "all-data-in-memory". The user could then add those capabilities in the cache definition, and the cache won't start if the configuration violates those capabilities. The capabilities would also be used internally, to improve the error message when a feature requires a particular combination of settings. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5572) Exposed JMX MBeans should be separate components

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-5572?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-5572: ------------------------------ Fix Version/s: 9.0.0.CR3 (was: 9.0.0.CR2) > Exposed JMX MBeans should be separate components > ------------------------------------------------ > > Key: ISPN-5572 > URL: https://issues.jboss.org/browse/ISPN-5572 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 8.0.0.Alpha2, 7.2.3.Final > Reporter: Dan Berindei > Fix For: 9.0.0.CR3 > > > We currently expose internal components as JMX MBeans, and that makes our JMX "API" very unstructured. The exposed MBeans should be separate components, and the only concern in their interfaces should be ease of use. > One example of JMX getting in the way of refactoring is {{CacheMgmtInterceptor}}. The interceptor chain is dynamic, so it should be possible to insert the interceptor only when statistics are enabled. But because the {{statisticsEnabled}} attribute is on the interceptor itself, that becomes a lot trickier, and we had to introduce a separate configuration attribute that disables statistics permanently (ISPN-5542). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5570) Cross-site: retry backup commands

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-5570?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-5570: ------------------------------ Fix Version/s: 9.0.0.CR3 (was: 9.0.0.CR2) > Cross-site: retry backup commands > --------------------------------- > > Key: ISPN-5570 > URL: https://issues.jboss.org/browse/ISPN-5570 > Project: Infinispan > Issue Type: Bug > Components: Core, Cross-Site Replication > Affects Versions: 7.2.3.Final > Reporter: Dan Berindei > Fix For: 9.0.0.CR3 > > > There are 3 phases in a backup RPC: > 1. Sender -> Local site master: caused by the site master is shutting down or crashing, or by a network split. > 2. Local site master -> Remote site master: > 2.1. Local site master is no longer a site master, e.g. because it's shutting down or because it's no longer coordinator after a merge. > 2.2. Remote site master is not longer a site master. > 2.3. Link between local site and remote site is down. > 3. Remote site master -> Backup targets > Replication failures in phase 3 are handled by retrying (except for TimeoutExceptions), because {{BaseBackupReceiver}} uses regular cache methods to perform the updates. > But replication failures in phases 1 and 2 are not handled in any way, except for causing the remote site to be taken offline after a certain number of replication failures (if backup is synchronous). We should instead retry backup RPCs when we get a {{SuspectException}} or {{UnreachableException}}, and perhaps even when we get no response (2.2?), and only stop when the timeout expires or when the backup is taken offline. > Async backup probably needs retrying as well, and perhaps even a more sophisticated approach like I-RAC (ISPN-2634). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

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

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-5557?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-5557: ------------------------------ Fix Version/s: 9.0.0.CR3 (was: 9.0.0.CR2) > 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: 9.0.0.CR3 > > > 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 (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

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

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-5530?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-5530: ------------------------------ Fix Version/s: 9.0.0.CR3 (was: 9.0.0.CR2) > 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: 9.0.0.CR3 > > > {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 (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5709) Support for running Infinispan as an Application in YARN

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-5709?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-5709: ------------------------------ Fix Version/s: 9.0.0.CR3 (was: 9.0.0.CR2) > Support for running Infinispan as an Application in YARN > -------------------------------------------------------- > > Key: ISPN-5709 > URL: https://issues.jboss.org/browse/ISPN-5709 > Project: Infinispan > Issue Type: Feature Request > Components: Hadoop Integration > Reporter: Gustavo Fernandes > Fix For: 9.0.0.CR3 > > > Hadoop 2.x allows custom "applications" to be managed by the resource scheduler framework. As an example, Apache Spark, Apache Tez, HBase and others can be bootstrapped and managed on top of Yarn. > Running on top of Yarn offers the following capabilities: > * Creating on demand (or long running) clusters with a simple command line, possibly targeting different versions and/or number of nodes > * Increase/Decrease the number of nodes as required > * Fine grained control of memory/CPU/disk/network utilized > * Submit arbitrary jobs targeting the application -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5704) Enhancements for Functional Map API

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-5704?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-5704: ------------------------------ Fix Version/s: 9.0.0.CR3 (was: 9.0.0.CR2) > Enhancements for Functional Map API > ----------------------------------- > > Key: ISPN-5704 > URL: https://issues.jboss.org/browse/ISPN-5704 > Project: Infinispan > Issue Type: Enhancement > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.0.0.CR3 > > > List of enhancements that didn't make it into 8.0: > * Transaction support. > * Verify locks are acquired for all operations (once tx is in place, locks can be checked easily) > * Complete persistence support (remove many returning previous, put many returning previous, remove many) > * Replication of per-invocation parameters. > * Port mode *Becoming*Test to functional APIs, and expand on testing other functional APIs. > * Test interoperability with cache, e.g. cache put with lifespan can be retrieved via functional map with lifespan, and viceversa > * Test compatibility mode > * Add more listener events: activation, passivation and expiration. > * Use check isLocal instead of `e == null` in command impls > * Fix branch skip issue (see previous PR: https://github.com/infinispan/infinispan/pull/3571) > * Add externalizers for primitive versions of Optional. > * ValueMatcherMode indexes in MarshallableFunctionExternalizers should be based on {{ordinal()}} calls to annotation. Also, could the core's enumeration use the annotations defined in commons? > * Add AdvancedExternalizer version for functions that takes value matcher > * Complete support for MetaCreated and MetaLastUsed (which should be separated into MetaLastModified and MetaLastAccessed) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5671) Implement missing RemoteCache read operations using near cache

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-5671?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-5671: ------------------------------ Fix Version/s: 9.0.0.CR3 (was: 9.0.0.CR2) > Implement missing RemoteCache read operations using near cache > -------------------------------------------------------------- > > Key: ISPN-5671 > URL: https://issues.jboss.org/browse/ISPN-5671 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.0.0.CR3 > > > For example: getAll, getWithMetadata, containsKey, getBulk, getAsync, values, retrieveEntries, and entrySet. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5665) Query should not rely on the results of return values of write commands

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-5665?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-5665: ------------------------------ Fix Version/s: 9.0.0.CR3 (was: 9.0.0.CR2) > Query should not rely on the results of return values of write commands > ----------------------------------------------------------------------- > > Key: ISPN-5665 > URL: https://issues.jboss.org/browse/ISPN-5665 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 8.0.0.Beta2 > Reporter: Dan Berindei > Assignee: Gustavo Fernandes > Fix For: 9.0.0.CR3 > > > The query interceptor relies on the return value of the write commands to know the previous value of the modified entries. This is not correct, because some write commands do not return the previous value, e.g. {{remove(key, value)}}, {{replace(key, oldValue, newValue)}}, and {{putAll(map)}}. > The query interceptor should instead look up the previous values in the invocation context, and also force the loading of old values in the invocation context if the command doesn't do it explicitly (e.g. {{putAll(map)}}, or {{put(k, v)}} with the {{IGNORE_RETURN_VALUES}} flag). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 2017