March 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5042) Remote gets caused by writes could be replicated only to the primary owner

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5042?page=com.atlassian.jira.plugin.... ] Dan Berindei resolved ISPN-5042. -------------------------------- Resolution: Done It's no longer relevant, with staggered gets (ISPN-825) we already ask the primary owner first, and only ask the backups if the primary is too slow. > Remote gets caused by writes could be replicated only to the primary owner > -------------------------------------------------------------------------- > > Key: ISPN-5042 > URL: https://issues.jboss.org/browse/ISPN-5042 > Project: Infinispan > Issue Type: Enhancement > Components: Core, State Transfer > Affects Versions: 7.1.0.Alpha1 > Reporter: Dan Berindei > Assignee: Sebastian Łaskawiec > Priority: Minor > Labels: 7.0 > Fix For: 8.2.0.Final > > > For write operations that need the previous value, a write CH-only owner that doesn't have a key locally will attempt to retrieve the key from the read CH-owners. > Sending the remote get command to all the previous owners will create extra load on the cluster during state transfer, so it should be more efficient to send the remote get only to the primary owner. Even though the latency of some write operations will be higher, the average latency should be better. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6334) Handle definitions of indexable classes in server config

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6334?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6334: -------------------------------- Description: Server's xml config already accepts them but they are not actually used. This is a continuation of ISPN-6178. Test for server are also missing ATM. (was: Server's xml config already accepts them but they are not actually used. This is a continuation of ISPN-6178.) > Handle definitions of indexable classes in server config > --------------------------------------------------------- > > Key: ISPN-6334 > URL: https://issues.jboss.org/browse/ISPN-6334 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Final > > > Server's xml config already accepts them but they are not actually used. This is a continuation of ISPN-6178. Test for server are also missing ATM. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6334) Handle definitions of indexable classes in server config

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6334?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6334: -------------------------------- Description: Server's xml config already accepts them but they are not actually used. This is a continuation of ISPN-6178. Tests for server are also missing ATM. (was: Server's xml config already accepts them but they are not actually used. This is a continuation of ISPN-6178. Test for server are also missing ATM.) > Handle definitions of indexable classes in server config > --------------------------------------------------------- > > Key: ISPN-6334 > URL: https://issues.jboss.org/browse/ISPN-6334 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Final > > > Server's xml config already accepts them but they are not actually used. This is a continuation of ISPN-6178. Tests for server are also missing ATM. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6305) Deadlock during cache start

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6305?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes resolved ISPN-6305. ------------------------------------- Resolution: Duplicate Issue > Deadlock during cache start > --------------------------- > > Key: ISPN-6305 > URL: https://issues.jboss.org/browse/ISPN-6305 > Project: Infinispan > Issue Type: Bug > Components: Core, Remote Querying > Affects Versions: 8.2.0.CR1 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Attachments: deadlock > > > I have a test where 3 servers are started concurrently. Some times it deadlocks (stack trace atached) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6305) Deadlock during cache start

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6305?page=com.atlassian.jira.plugin.... ] Work on ISPN-6305 started by Gustavo Fernandes. ----------------------------------------------- > Deadlock during cache start > --------------------------- > > Key: ISPN-6305 > URL: https://issues.jboss.org/browse/ISPN-6305 > Project: Infinispan > Issue Type: Bug > Components: Core, Remote Querying > Affects Versions: 8.2.0.CR1 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Attachments: deadlock > > > I have a test where 3 servers are started concurrently. Some times it deadlocks (stack trace atached) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6305) Deadlock during cache start

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6305?page=com.atlassian.jira.plugin.... ] Work on ISPN-6305 stopped by Gustavo Fernandes. ----------------------------------------------- > Deadlock during cache start > --------------------------- > > Key: ISPN-6305 > URL: https://issues.jboss.org/browse/ISPN-6305 > Project: Infinispan > Issue Type: Bug > Components: Core, Remote Querying > Affects Versions: 8.2.0.CR1 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Attachments: deadlock > > > I have a test where 3 servers are started concurrently. Some times it deadlocks (stack trace atached) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6305) Deadlock during cache start

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6305?page=com.atlassian.jira.plugin.... ] Adrian Nistor commented on ISPN-6305: ------------------------------------- [~gustavonalle] I have a hunch this was fixed by ISPN-6323 and ISPN-6178. > Deadlock during cache start > --------------------------- > > Key: ISPN-6305 > URL: https://issues.jboss.org/browse/ISPN-6305 > Project: Infinispan > Issue Type: Bug > Components: Core, Remote Querying > Affects Versions: 8.2.0.CR1 > Reporter: Gustavo Fernandes > Attachments: deadlock > > > I have a test where 3 servers are started concurrently. Some times it deadlocks (stack trace atached) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6324) Remove clustercacheloader example from server

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-6324?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-6324: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Remove clustercacheloader example from server > --------------------------------------------- > > Key: ISPN-6324 > URL: https://issues.jboss.org/browse/ISPN-6324 > Project: Infinispan > Issue Type: Task > Components: Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.2.0.Final > > > The ccl example is not really useful for server. Let's remove it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6336) NonIndexedClusteredDummyInMemoryStoreQueryDslConditionsTest random failures

by Gustavo Fernandes (JIRA)

Gustavo Fernandes created ISPN-6336: --------------------------------------- Summary: NonIndexedClusteredDummyInMemoryStoreQueryDslConditionsTest random failures Key: ISPN-6336 URL: https://issues.jboss.org/browse/ISPN-6336 Project: Infinispan Issue Type: Bug Reporter: Gustavo Fernandes Picked this failure when running the query testsuite in loop. It's somehow hard to reproduce. The presence of the Byteman test runner in the stacktrace looks suspicious, since it is not supposed to run this test. {code} Tests run: 2907, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 51.21 sec <<< FAILURE! - in TestSuite testSampleDomainQuery16(org.infinispan.query.dsl.embedded.NonIndexedClusteredDummyInMemoryStoreQueryDslConditionsTest) Time elapsed: 0.01 sec <<< FAILURE! java.lang.AssertionError: expected:<50> but was:<0> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:743) at org.junit.Assert.assertEquals(Assert.java:118) at org.junit.Assert.assertEquals(Assert.java:555) at org.junit.Assert.assertEquals(Assert.java:542) at org.infinispan.query.dsl.embedded.QueryDslConditionsTest.testSampleDomainQuery16(QueryDslConditionsTest.java:1366) 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.MethodInvocationHelper$1.runTestMethod(MethodInvocationHelper.java:200) at org.jboss.byteman.contrib.bmunit.BMNGAbstractRunner.run(BMNGAbstractRunner.java:58) at sun.reflect.GeneratedMethodAccessor72.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.testng.internal.MethodInvocationHelper.invokeHookable(MethodInvocationHelper.java:212) at org.testng.internal.Invoker.invokeMethod(Invoker.java:707) 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) {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6287) Make blueprint optional in OSGi manifests

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6287?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-6287: -------------------------------------- Fix Version/s: (was: 8.2.0.Final) (was: 8.1.2.Final) > Make blueprint optional in OSGi manifests > ----------------------------------------- > > Key: ISPN-6287 > URL: https://issues.jboss.org/browse/ISPN-6287 > Project: Infinispan > Issue Type: Enhancement > Components: Integration > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Minor > > In a pure Equinox environment we have no Blueprint bundle and importing it cases failures. The easiest solution is to make it optional. > Bundles to cover: > * infinispan-core > * infinispan-remote > * infinispan-embedded -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 March 2016