February 2018 - infinispan-issues

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

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5570?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5570: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > 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.3.0.Final > > > 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.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6041) Remote Listeners: Client event reader thread reports EOF as error

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6041?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6041: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > Remote Listeners: Client event reader thread reports EOF as error > ----------------------------------------------------------------- > > Key: ISPN-6041 > URL: https://issues.jboss.org/browse/ISPN-6041 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 8.1.0.Final > Reporter: Dan Berindei > Priority: Minor > Fix For: 9.3.0.Final > > > {noformat} > 14:02:14,904 ERROR (Client-Listener-87aa07aee56d43e1) [ClientListenerNotifier] ISPN004043: Unrecoverable error reading event from server /127.0.0.1:15530, exiting event reader thread > org.infinispan.client.hotrod.exceptions.TransportException: End of stream reached! > at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport.readByte(TcpTransport.java:198) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readMagic(Codec20.java:305) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readEvent(Codec20.java:147) > at org.infinispan.client.hotrod.event.ClientListenerNotifier$EventDispatcher.run(ClientListenerNotifier.java:252) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > 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) > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6036) Support custom KeyPartitioners in the HotRod server and client

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6036?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6036: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > Support custom KeyPartitioners in the HotRod server and client > -------------------------------------------------------------- > > Key: ISPN-6036 > URL: https://issues.jboss.org/browse/ISPN-6036 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.3.0.Final > > > ISPN-5465 introduced the {{KeyPartitioner}} interface to allow custom mapping of keys to hash segments, but only in embedded mode. > The HotRod protocol doesn't necessarily need changes, the server and client just need to use the same {{KeyPartitioner}}. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6015) Query DSL should support groupBy for multi-valued properties

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6015?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6015: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > Query DSL should support groupBy for multi-valued properties > ------------------------------------------------------------ > > Key: ISPN-6015 > URL: https://issues.jboss.org/browse/ISPN-6015 > Project: Infinispan > Issue Type: Feature Request > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.3.0.Final > > > If a groupBy property is multivalued the entity will belong to multiple groups, one for each distinct value. > Current implementation in 8.0.x and 8.1.x does not allow this and instead of providing invalid results grouping by multivalued property was disallowed (see ISPN-6008). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6011) ClassCastException in CDI generated keys for JCache

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6011?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6011: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > ClassCastException in CDI generated keys for JCache > --------------------------------------------------- > > Key: ISPN-6011 > URL: https://issues.jboss.org/browse/ISPN-6011 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.1.0.CR1, 8.0.2.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.3.0.Final > > > When using JCache-annotations the DefaultCacheKeyGenerator exclusively looks at parameter values to form the cache key. Therefore it will be very likely that collissions occur (resulting in difficult to find ClassCastExceptions). The provided patch uses the method- and class names as additionally values to make the cache key more unique. > Might also add that I am aware that by spec this should not be an issue when no cachename is given (as it should generate a cache using the class-name), but when a cache name is given collissions may occur. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6006) Alias caches

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6006?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6006: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > Alias caches > ------------ > > Key: ISPN-6006 > URL: https://issues.jboss.org/browse/ISPN-6006 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Labels: dv, jdg7 > Fix For: 9.3.0.Final > > > Implement alias caches: > https://github.com/infinispan/infinispan/wiki/Alias-Caches -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5990) Upgrade javassist dependency in protostream to ensure java 8 compatibility

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5990?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5990: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > Upgrade javassist dependency in protostream to ensure java 8 compatibility > -------------------------------------------------------------------------- > > Key: ISPN-5990 > URL: https://issues.jboss.org/browse/ISPN-5990 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.0.0.Final, 8.1.0.Alpha1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.0.3.Final, 9.3.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5987) Create concurrent topology switch under failover unit test

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5987?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5987: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > Create concurrent topology switch under failover unit test > ---------------------------------------------------------- > > Key: ISPN-5987 > URL: https://issues.jboss.org/browse/ISPN-5987 > Project: Infinispan > Issue Type: Task > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.3.0.Final > > > Create a unit test for ISPN-5879. > Matej built a very interesting one [here|https://raw.githubusercontent.com/mcimbora/infinispan/da971738e326a7...] but needs some further work. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5976) Server ops which don't manipulate the model should be runtime only

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5976?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5976: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > Server ops which don't manipulate the model should be runtime only > ------------------------------------------------------------------ > > Key: ISPN-5976 > URL: https://issues.jboss.org/browse/ISPN-5976 > Project: Infinispan > Issue Type: Feature Request > Components: Server > Affects Versions: 8.1.0.Beta1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.3.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6162) Drop Query.getResultSize() method

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6162?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6162: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > Drop Query.getResultSize() method > --------------------------------- > > Key: ISPN-6162 > URL: https://issues.jboss.org/browse/ISPN-6162 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying, Remote Querying > Reporter: Tristan Tarrant > Assignee: Adrian Nistor > Fix For: 9.3.0.Final > > > Do we keep org.infinispan.query.dsl.Query.getResultSize? Does it return int or long? Return -1 if actual figure unknown/hard to compute? Result size might be non-trivial for non-indexed or hybrid case and will require full scan even for queries with limit. Deprecate it now, remove in ispn 9. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2018