February 2016 - infinispan-issues

[JBoss JIRA] (ISPN-6140) Avoid refresh after starting or stopping a node

by Pedro Zapata (JIRA)

Pedro Zapata created ISPN-6140: ---------------------------------- Summary: Avoid refresh after starting or stopping a node Key: ISPN-6140 URL: https://issues.jboss.org/browse/ISPN-6140 Project: Infinispan Issue Type: Bug Components: Console Reporter: Pedro Zapata Priority: Minor Node status should be automatically changed without relaying on a manual refresh. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6139) Delete a node from cluster

by Pedro Zapata (JIRA)

Pedro Zapata created ISPN-6139: ---------------------------------- Summary: Delete a node from cluster Key: ISPN-6139 URL: https://issues.jboss.org/browse/ISPN-6139 Project: Infinispan Issue Type: Enhancement Components: Console Reporter: Pedro Zapata Nodes can be added but they can't be deleted from the console. Only stopped nodes should be able to be deleted. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6051) ClusterExpirationManager missing locking

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-6051?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-6051: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3978 > ClusterExpirationManager missing locking > ---------------------------------------- > > Key: ISPN-6051 > URL: https://issues.jboss.org/browse/ISPN-6051 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.1.0.Final > Reporter: Dan Berindei > Assignee: William Burns > Fix For: 8.2.0.CR1 > > > Because {{ClusterExpirationManager.handleLifespanExpired()}} doesn't lock the entry and the value is actually read in the async thread, the created {{RemoveExpiredCommand}} sometimes uses a newer value written by another thread. > Could be fixed by using {{DataContainer.compute()}} to check expiration and create the {{RemoveExpirationCommand}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5995) ParseUtils.unexpectedElement/unxpectedAttribute called but the exception is not thrown

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5995?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5995: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3977 > ParseUtils.unexpectedElement/unxpectedAttribute called but the exception is not thrown > -------------------------------------------------------------------------------------- > > Key: ISPN-5995 > URL: https://issues.jboss.org/browse/ISPN-5995 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.1.0.CR1, 8.0.2.Final > Reporter: Adrian Nistor > Fix For: 8.2.0.CR1, 8.0.3.Final, 8.1.2.Final > > > There are a number of invocations of org.infinispan.configuration.parsing.ParseUtils where the returned XMLStreamException is not thrown although it should. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5995) ParseUtils.unexpectedElement/unxpectedAttribute called but the exception is not thrown

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5995?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5995: -------------------------------- Fix Version/s: 8.1.2.Final > ParseUtils.unexpectedElement/unxpectedAttribute called but the exception is not thrown > -------------------------------------------------------------------------------------- > > Key: ISPN-5995 > URL: https://issues.jboss.org/browse/ISPN-5995 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.1.0.CR1, 8.0.2.Final > Reporter: Adrian Nistor > Fix For: 8.2.0.CR1, 8.0.3.Final, 8.1.2.Final > > > There are a number of invocations of org.infinispan.configuration.parsing.ParseUtils where the returned XMLStreamException is not thrown although it should. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5995) ParseUtils.unexpectedElement/unxpectedAttribute called but the exception is not thrown

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5995?page=com.atlassian.jira.plugin.... ] Adrian Nistor reassigned ISPN-5995: ----------------------------------- Assignee: Adrian Nistor > ParseUtils.unexpectedElement/unxpectedAttribute called but the exception is not thrown > -------------------------------------------------------------------------------------- > > Key: ISPN-5995 > URL: https://issues.jboss.org/browse/ISPN-5995 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.1.0.CR1, 8.0.2.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.2.0.CR1, 8.0.3.Final, 8.1.2.Final > > > There are a number of invocations of org.infinispan.configuration.parsing.ParseUtils where the returned XMLStreamException is not thrown although it should. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5809) View of cluster events

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-5809?page=com.atlassian.jira.plugin.... ] Pedro Zapata reassigned ISPN-5809: ---------------------------------- Assignee: Pedro Zapata (was: Vladimir Blagojevic) > View of cluster events > ---------------------- > > Key: ISPN-5809 > URL: https://issues.jboss.org/browse/ISPN-5809 > Project: Infinispan > Issue Type: Sub-task > Components: Console > Reporter: Pedro Zapata > Assignee: Pedro Zapata > > As an Adminstrator, I want to view all cluster-split and cluster-merge events in the last 7 days. Each event should indicate the following information: time-stamp of event, Merge/Split, the cluster View before Merge/Split, the cluster View after Merge/Split. > Cluster events will be visualized as a summary in the cache containers page > https://rawgit.com/infinispan/infinispan-console-mockup/master/cache-cont... > and in the cluster list page > https://rawgit.com/infinispan/infinispan-console-mockup/master/clusters.html > A detailed ‘Grid events’ page will be added: > https://rawgit.com/infinispan/infinispan-console-mockup/master/events.html > Type of logs: > * Task execution (as requested by users) > * Node join/leave > * Split/Merge > * Rebalancing start / stop > * Mass indexer > * Server start/shutdown > * Site up / down > * Cache related events > Log properties: > * Timestamp > * Title > * Description > Logs will be of severity INFO and ERROR. > Logs will be stored in a persistent, eviction, 7 days expiration cache. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6137) ScriptMetadataTest.testBrokenParameters fails since the logging range changes

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6137?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6137: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Integrated. Thanks! > ScriptMetadataTest.testBrokenParameters fails since the logging range changes > ----------------------------------------------------------------------------- > > Key: ISPN-6137 > URL: https://issues.jboss.org/browse/ISPN-6137 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 8.2.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.2.0.CR1 > > > The ISPN-6123 fix changed the logging ids for the scripting module, breaking `ScriptMetadataTest.testBrokenParameters`: > {noformat} > The exception was thrown with the wrong message: expected "^ISPN021011.*" but got "ISPN026011: Script parameters must be declared using the array notation, e.g. [a,b,c]" > at org.testng.internal.Invoker.handleInvocationResults(Invoker.java:1481) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:754) > 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) > Caused by: java.lang.IllegalArgumentException: ISPN026011: Script parameters must be declared using the array notation, e.g. [a,b,c] > at org.infinispan.scripting.impl.ScriptMetadataParser.unarray(ScriptMetadataParser.java:99) > at org.infinispan.scripting.impl.ScriptMetadataParser.parse(ScriptMetadataParser.java:56) > at org.infinispan.scripting.ScriptMetadataTest.testBrokenParameters(ScriptMetadataTest.java:63) > 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:497) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) > ... 14 more > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5012) ClusterRegistry as a service cache provider

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5012?page=com.atlassian.jira.plugin.... ] Adrian Nistor resolved ISPN-5012. --------------------------------- Fix Version/s: (was: 8.2.0.CR1) Resolution: Duplicate Issue > ClusterRegistry as a service cache provider > ------------------------------------------- > > Key: ISPN-5012 > URL: https://issues.jboss.org/browse/ISPN-5012 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > > The ClusterRegistry is currently a volatile, replicated cache with a composite key and it does not serve the original purpose for which it was built. It should be refactored to be a service cache factory with a builder API based on desired features and a NamingStrategy so that we can have "well-known" caches as well as temporary caches. It should also be possible to use the cache dependency mechanism to "chain" service cache lifecycles to other caches. > Here's an example API (not a real example): > RegistryBuilder builder = registry.getBuilder(); > builder.persistent().clustered().dependsOn(Cache<?,?> cache).namingStrategy(new StaticCacheNamingStrategy("___protobuf_metadata")) > This registry would be able to provide caches to the following use cases: > - protobuf schemas > - hotrod topology > - security acl > - map/reduce work caches > - index caches > - etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6138) Remove type parameter form QueryBuilder and QueryFactory

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6138?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6138: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/3975 > Remove type parameter form QueryBuilder and QueryFactory > -------------------------------------------------------- > > Key: ISPN-6138 > URL: https://issues.jboss.org/browse/ISPN-6138 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > > That parameter has become meaningless after several refactorings. It will always be ```Query```, never a subtype of it, so it can be removed. > This will not be backward compatible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2016