January 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5039) Add failover tests simulating node crash/kill

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5039?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5039: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Add failover tests simulating node crash/kill > --------------------------------------------- > > Key: ISPN-5039 > URL: https://issues.jboss.org/browse/ISPN-5039 > Project: Infinispan > Issue Type: Task > Components: Distributed Execution and Map/Reduce > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Fix For: 7.1.0.Beta1 > > > Although we have some failover tests we do not explicitly test node crashing and failover. We should add tests simulating node crash for regular one site setup and topology aware nodes. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5126) DistributedExecutorService ignores unsuccessful responses

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5126?page=com.atlassian.jira.plugin.... ] Dan Berindei reassigned ISPN-5126: ---------------------------------- Assignee: Vladimir Blagojevic > DistributedExecutorService ignores unsuccessful responses > --------------------------------------------------------- > > Key: ISPN-5126 > URL: https://issues.jboss.org/browse/ISPN-5126 > Project: Infinispan > Issue Type: Bug > Components: Core, Distributed Execution and Map/Reduce > Affects Versions: 7.1.0.Alpha1, 7.0.3.Final > Reporter: Dan Berindei > Assignee: Vladimir Blagojevic > Priority: Critical > Labels: testsuite_stability > > I got a failure in {{DistributedExecutorFailureTest}} (master only) on my machine because the distributed executor ignores {{CacheNotFoundResponse}} responses: > {noformat} > 15:18:45,516 TRACE (transport-thread-NodeA-p30129-t4:) [CommandAwareRpcDispatcher] Response: CacheNotFoundResponse > 15:18:45,516 TRACE (transport-thread-NodeA-p30129-t4:) [RpcManagerImpl] Response(s) to DistributedExecuteCommand [cache=null, keys=[], callable=org.infinispan.distexec.DistributedExecutorFailoverTest$SleepingSimpleCallable@23a9b62a] is {NodeB-4305=CacheNotFoundResponse} > 15:18:45,517 ERROR (testng-DistributedExecutorFailoverTest:) [UnitTestTestNGListener] Test testBasicTargetRemoteDistributedCallable(org.infinispan.distexec.DistributedExecutorFailoverTest) failed. > java.lang.AssertionError: expected:<1> but was:<null> > 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.testng.AssertJUnit.assertEquals(AssertJUnit.java:88) > at org.infinispan.distexec.DistributedExecutorFailoverTest.testBasicTargetRemoteDistributedCallable(DistributedExecutorFailoverTest.java:74) > {noformat} > {{RemoteDistributedTaskPart.retrieveResult()}} ignores any response that's not a {{SuccessfulResponse}} and returns {{null}}. It should throw an exception instead, so that the failover policy can retry it on another node. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5126) DistributedExecutorService ignores unsuccessful responses

by Dan Berindei (JIRA)

Dan Berindei created ISPN-5126: ---------------------------------- Summary: DistributedExecutorService ignores unsuccessful responses Key: ISPN-5126 URL: https://issues.jboss.org/browse/ISPN-5126 Project: Infinispan Issue Type: Bug Components: Core, Distributed Execution and Map/Reduce Affects Versions: 7.0.3.Final, 7.1.0.Alpha1 Reporter: Dan Berindei Priority: Critical I got a failure in {{DistributedExecutorFailureTest}} (master only) on my machine because the distributed executor ignores {{CacheNotFoundResponse}} responses: {noformat} 15:18:45,516 TRACE (transport-thread-NodeA-p30129-t4:) [CommandAwareRpcDispatcher] Response: CacheNotFoundResponse 15:18:45,516 TRACE (transport-thread-NodeA-p30129-t4:) [RpcManagerImpl] Response(s) to DistributedExecuteCommand [cache=null, keys=[], callable=org.infinispan.distexec.DistributedExecutorFailoverTest$SleepingSimpleCallable@23a9b62a] is {NodeB-4305=CacheNotFoundResponse} 15:18:45,517 ERROR (testng-DistributedExecutorFailoverTest:) [UnitTestTestNGListener] Test testBasicTargetRemoteDistributedCallable(org.infinispan.distexec.DistributedExecutorFailoverTest) failed. java.lang.AssertionError: expected:<1> but was:<null> 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.testng.AssertJUnit.assertEquals(AssertJUnit.java:88) at org.infinispan.distexec.DistributedExecutorFailoverTest.testBasicTargetRemoteDistributedCallable(DistributedExecutorFailoverTest.java:74) {noformat} {{RemoteDistributedTaskPart.retrieveResult()}} ignores any response that's not a {{SuccessfulResponse}} and returns {{null}}. It should throw an exception instead, so that the failover policy can retry it on another node. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5126) DistributedExecutorService ignores unsuccessful responses

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5126?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5126: ------------------------------- Status: Open (was: New) > DistributedExecutorService ignores unsuccessful responses > --------------------------------------------------------- > > Key: ISPN-5126 > URL: https://issues.jboss.org/browse/ISPN-5126 > Project: Infinispan > Issue Type: Bug > Components: Core, Distributed Execution and Map/Reduce > Affects Versions: 7.1.0.Alpha1, 7.0.3.Final > Reporter: Dan Berindei > Priority: Critical > Labels: testsuite_stability > > I got a failure in {{DistributedExecutorFailureTest}} (master only) on my machine because the distributed executor ignores {{CacheNotFoundResponse}} responses: > {noformat} > 15:18:45,516 TRACE (transport-thread-NodeA-p30129-t4:) [CommandAwareRpcDispatcher] Response: CacheNotFoundResponse > 15:18:45,516 TRACE (transport-thread-NodeA-p30129-t4:) [RpcManagerImpl] Response(s) to DistributedExecuteCommand [cache=null, keys=[], callable=org.infinispan.distexec.DistributedExecutorFailoverTest$SleepingSimpleCallable@23a9b62a] is {NodeB-4305=CacheNotFoundResponse} > 15:18:45,517 ERROR (testng-DistributedExecutorFailoverTest:) [UnitTestTestNGListener] Test testBasicTargetRemoteDistributedCallable(org.infinispan.distexec.DistributedExecutorFailoverTest) failed. > java.lang.AssertionError: expected:<1> but was:<null> > 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.testng.AssertJUnit.assertEquals(AssertJUnit.java:88) > at org.infinispan.distexec.DistributedExecutorFailoverTest.testBasicTargetRemoteDistributedCallable(DistributedExecutorFailoverTest.java:74) > {noformat} > {{RemoteDistributedTaskPart.retrieveResult()}} ignores any response that's not a {{SuccessfulResponse}} and returns {{null}}. It should throw an exception instead, so that the failover policy can retry it on another node. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5103) Inefficient index updates cause high cost merges and increase overall latency

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-5103?page=com.atlassian.jira.plugin.... ] Sanne Grinovero edited comment on ISPN-5103 at 1/7/15 12:43 PM: ---------------------------------------------------------------- As a reminder of our IRC chat: it seems this would be safe as Infinispan Query handles the identifiers in a slightly different way than Hibernate Search / ORM : the {{org.infinispan.query.Transformer}} guarantees a unique relation between each encoded id and makes it possible to reconstruct from it not only the ID instance but also the {{Transformer}} implementation to be used for the transformation itself. A similar optimisation wouldn't be always safe in ORM world as the {{org.hibernate.search.bridge.TwoWayFieldBridge}} needs to be known, or we'd need to be sure that different {{FieldBridge}} implementations would encode values in some unique way. For example we'd have a problem when mapping Integer(5) and Long(5) using keyword encoding as they would both map to "5", which could be back-mapped to either the Integer or the Long version, hence deleting the other entry from the index as well. was (Author: sannegrinovero): As a reminder of our IRC chat: it seems this would be safe as Infinispan Query handles the identifiers in a slightly different way than Hibernate Search / ORM : the {{org.infinispan.query.Transformer}} guarantees a unique relation between each encoded id and makes it possible to reconstruct from it not only the ID instance but also the {{Transformer}} implementation to be used for the transformation itself. A similar optimisation wouldn't be always safe in ORM world as the {{org.hibernate.search.bridge.TwoWayFieldBridge}} needs to be known, or we'd need to be sure that different {{FieldBridge}} implementations would encode values in some unique way. For example we'd have a problem when mapping Integer(5) and Long(5) using keyword encoding as they would both map to "5". > Inefficient index updates cause high cost merges and increase overall latency > ----------------------------------------------------------------------------- > > Key: ISPN-5103 > URL: https://issues.jboss.org/browse/ISPN-5103 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 7.0.2.Final, 7.1.0.Alpha1 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > > Currently every change to the index is done Lucene-wise combining two operations: > * Delete by query, using a boolean query on the id plus the entity class > * Add > > Under high load, specially during merges those numerous deletes provoke very long delays causing high latency. > We should instead use a simple Lucene Update to add/change documents, since internally it translates to a Delete by term plus an Add operation, and delete by terms are extremely efficient in Lucene. > Some local tests showed average latency of updating the index using this strategy to drop 4 times, both for the SYNC and ASYNC backends > With relation to sharing the index between entities, which was the original motivation of the Delete by query plus add strategy, we have two scenarios: > * Same cache with multiple entity types: that's a non-issue, since obviously there's no id collision in this case > * Different caches with the same index: this scenario happens when different caches shares the same index, for ex: > {code} > @Indexed(indexName=common) > public class Country { ... } > @Indexed(indexName=common) > public class Currency { ... } > cm.getCache("currencies").put(1, new Currency(...)) > cm.getCache("countries").put(1, new Country(...)) > {code} > This would require a delete by query in order to persist both a Country and a Currency with id=1. > It would also require setting "default.exclusive_index_use", "false", with the associated cost of having to reopen the IndexWriter on every operation. > Given the performance gain of doing a simple Update is considerable, we should make the corner case supported by extra configuration or alternatively, generate a unique @ProvidedId, including the entity class or the cache name that work for all cases described above. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5125) EventType methods are not public

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5125?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5125: ----------------------------------------------- William Burns <wburns(a)redhat.com> changed the Status of [bug 1179867|https://bugzilla.redhat.com/show_bug.cgi?id=1179867] from NEW to POST > EventType methods are not public > -------------------------------- > > Key: ISPN-5125 > URL: https://issues.jboss.org/browse/ISPN-5125 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.0.3.Final > Reporter: William Burns > Assignee: William Burns > Fix For: 7.1.0.Beta1 > > > The org.infinispan.notifications.cachelistener.filter.EventType has some methods that are not marked as public (isRetry, isPreEvent, isRemove, isCreate, isModified). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5125) EventType methods are not public

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5125?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5125: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3191 > EventType methods are not public > -------------------------------- > > Key: ISPN-5125 > URL: https://issues.jboss.org/browse/ISPN-5125 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.0.3.Final > Reporter: William Burns > Assignee: William Burns > Fix For: 7.1.0.Beta1 > > > The org.infinispan.notifications.cachelistener.filter.EventType has some methods that are not marked as public (isRetry, isPreEvent, isRemove, isCreate, isModified). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5124) The package org.infinispan.notifications.cachelistener.filter should have a public javadoc

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5124?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5124: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/3190 > The package org.infinispan.notifications.cachelistener.filter should have a public javadoc > ------------------------------------------------------------------------------------------ > > Key: ISPN-5124 > URL: https://issues.jboss.org/browse/ISPN-5124 > Project: Infinispan > Issue Type: Task > Components: Documentation-Core > Affects Versions: 7.0.3.Final > Reporter: William Burns > Assignee: William Burns > Fix For: 7.1.0.Beta1 > > > We need to add a package-info.java file to the org.infinispan.notifications.cachelistener.filter package so the classes can be exposed as public. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5125) EventType methods are not public

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5125?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5125: -------------------------------- Status: Open (was: New) > EventType methods are not public > -------------------------------- > > Key: ISPN-5125 > URL: https://issues.jboss.org/browse/ISPN-5125 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.0.3.Final > Reporter: William Burns > Assignee: William Burns > Fix For: 7.1.0.Beta1 > > > The org.infinispan.notifications.cachelistener.filter.EventType has some methods that are not marked as public (isRetry, isPreEvent, isRemove, isCreate, isModified). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5125) EventType methods are not public

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5125?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-5125: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1179867 > EventType methods are not public > -------------------------------- > > Key: ISPN-5125 > URL: https://issues.jboss.org/browse/ISPN-5125 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.0.3.Final > Reporter: William Burns > Assignee: William Burns > Fix For: 7.1.0.Beta1 > > > The org.infinispan.notifications.cachelistener.filter.EventType has some methods that are not marked as public (isRetry, isPreEvent, isRemove, isCreate, isModified). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2015