May 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4817) Cluster Listener replication of listener to remote dist nodes needs privilege action

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4817?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-4817: ---------------------------------- Fix Version/s: 9.0.0.Alpha3 (was: 9.0.0.Alpha2) > Cluster Listener replication of listener to remote dist nodes needs privilege action > ------------------------------------------------------------------------------------ > > Key: ISPN-4817 > URL: https://issues.jboss.org/browse/ISPN-4817 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 7.0.0.CR1 > Reporter: William Burns > Priority: Critical > Fix For: 9.0.0.Alpha3 > > > The ClusterListenerReplicateCallable needs to add the listener in a privileged block so that it can work properly. > I was also thinking if we need to change all of our messages to send along the current Subject so it can be properly applied to remote invocations as well. In this case we wouldn't need to wrap the listener invocation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4735) Remove TODOs from the documentation

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4735?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-4735: ---------------------------------- Fix Version/s: 9.0.0.Alpha3 (was: 9.0.0.Alpha2) > Remove TODOs from the documentation > ----------------------------------- > > Key: ISPN-4735 > URL: https://issues.jboss.org/browse/ISPN-4735 > Project: Infinispan > Issue Type: Task > Components: Documentation-Core, Documentation-Query, Documentation-Servers > Reporter: Mircea Markus > Assignee: Tristan Tarrant > Fix For: 9.0.0.Alpha3 > > > ATM the documentation has 38 todos, some of them being empty chapter in User Guide - pretty annoying for a new user trying to get used to Infinispan. Let's fixe all of these before 7.0.0.CR1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4584) Stricter validation of cache configurations for distributed indexes

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4584?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-4584: ---------------------------------- Fix Version/s: 9.0.0.Alpha3 (was: 9.0.0.Alpha2) > Stricter validation of cache configurations for distributed indexes > ------------------------------------------------------------------- > > Key: ISPN-4584 > URL: https://issues.jboss.org/browse/ISPN-4584 > Project: Infinispan > Issue Type: Enhancement > Components: Lucene Directory > Reporter: Sanne Grinovero > Assignee: Gustavo Fernandes > Fix For: 9.0.0.Alpha3 > > > See also ISPN-4577 : it should not be allowed to configure a distributed metadata cache while the chunks cache is using local mode. > Ideally think of additional strict checks which we should apply.. suggestions? > Mitigated by ISPN-4340 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4286) Two concurrent putIfAbsent operations can both return null during rebalance

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4286?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-4286: ---------------------------------- Fix Version/s: 9.0.0.Alpha3 (was: 9.0.0.Alpha2) > Two concurrent putIfAbsent operations can both return null during rebalance > --------------------------------------------------------------------------- > > Key: ISPN-4286 > URL: https://issues.jboss.org/browse/ISPN-4286 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 6.0.2.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Fix For: 9.0.0.Alpha3 > > > If the cache topology changes while executing a putIfAbsent operation, the old primary owner will throw an OutdatedTopologyException, and the originator will retry on the new owner. > When retrying the PutKeyValueCommand on the new primary owner, we compare the current value with the command's new value. If they are equal, we assume that the initial command wrote the old value, and we return {{null}}. > However, the value might have been written by another putIfAbsent operation. So we could have two {{putIfAbsent(k, v)}} operations, both returning {{null}}. > {code} > A is the originator, B is the primary owner, k = null > A -> B: putIfAbsent(k, v1) > B dies before writing v, C is now primary owner > D -> C: putIfAbsent(k, v1) // another put operation from D, with the same value > C -> D: null // correct > A -> C: retry_putIfAbsent(k, v1) > C -> A: null // C assumes A is overwriting its own value, so it's also returning null > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4159) DefaultTwoWayKey2StringMapper encodes objects to strings in a manner that is incompatible with string handling of some databases

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4159?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-4159: ---------------------------------- Fix Version/s: 9.0.0.Alpha3 (was: 9.0.0.Alpha2) > DefaultTwoWayKey2StringMapper encodes objects to strings in a manner that is incompatible with string handling of some databases > -------------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-4159 > URL: https://issues.jboss.org/browse/ISPN-4159 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 6.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Alpha3 > > > DefaultTwoWayKey2StringMapper uses two neat tricks. > 1. it does not encode all supported types, it only encodes non-Strings. Strings are kept unmodified. > 2. it uses a special prefix (unicode char 0xfeff) to mark which strings were encoded and which are plain. > Unfortunately some databases, notably MySql, interpret the endianness mark (0xfeff, 0xfffe), convert to native byte order and then drop it. > This leaves us with no clue the string is not an actual String but an encoded representation of another type. This misinterpretation leads later to ClassCastExceptions in various places in core and user code. > Proposed fix: get rid of #1 and #2 optimisations. Encode all objects, including Strings and always use the ?n prefix (where n stands for the original type). Drop the 0xFEFF marker prefix. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5075) org.infinispan.IllegalLifecycleStateException in query tests

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5075?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5075: ---------------------------------- Fix Version/s: 9.0.0.Alpha3 (was: 9.0.0.Alpha2) > org.infinispan.IllegalLifecycleStateException in query tests > ------------------------------------------------------------ > > Key: ISPN-5075 > URL: https://issues.jboss.org/browse/ISPN-5075 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Query > Affects Versions: 7.1.0.Alpha1 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 9.0.0.Alpha3 > > > Many query tests log an error after running: > {code} > Exception in thread "Hibernate Search: async deletion of index segments-1" org.infinispan.IllegalLifecycleStateException: ISPN000323: Cache 'LuceneIndexesMetadata' is in 'TERMINATED' state and so it does not accept new invocations. Either restart it or recreate the cache container. > at org.infinispan.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:89) > at org.infinispan.interceptors.InvocationContextInterceptor.handleDefault(InvocationContextInterceptor.java:71) > at org.infinispan.commands.AbstractVisitor.visitGetKeyValueCommand(AbstractVisitor.java:77) > at org.infinispan.commands.read.GetKeyValueCommand.acceptVisitor(GetKeyValueCommand.java:44) > at org.infinispan.interceptors.InterceptorChain.invoke(InterceptorChain.java:333) > at org.infinispan.cache.impl.CacheImpl.get(CacheImpl.java:422) > at org.infinispan.cache.impl.DecoratedCache.get(DecoratedCache.java:427) > at org.infinispan.lucene.impl.FileListOperations.getFileList(FileListOperations.java:160) > at org.infinispan.lucene.impl.FileListOperations.deleteFileName(FileListOperations.java:129) > at org.infinispan.lucene.impl.DirectoryImplementor.deleteFile(DirectoryImplementor.java:64) > at org.infinispan.lucene.impl.DirectoryLuceneV4$DeleteTask.run(DirectoryLuceneV4.java:195) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > {code} > That error does not cause the tests to fail, and are due to the async deletes of segments recently implemented. Need to check if the executors are being flushed correctly when the cache manager stops -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5077) Custom remote events can be slightly inefficient

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5077?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5077: ---------------------------------- Fix Version/s: 9.0.0.Alpha3 (was: 9.0.0.Alpha2) > Custom remote events can be slightly inefficient > ------------------------------------------------ > > Key: ISPN-5077 > URL: https://issues.jboss.org/browse/ISPN-5077 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Affects Versions: 7.0.2.Final > Reporter: Galder Zamarreño > Fix For: 9.0.0.Alpha3 > > > Something we might want to improve for Hot Rod 3.0 protocol: > [16:40] <galderz> i've been thinking further about converters, and I think i've found a slight mismatch between what converter means for embedded listeners vs remote listeners > [16:40] <wburns> oh yeah? > [16:40] <galderz> for embedded listeners, it essentially transforms what you see as `value` > [16:41] <galderz> with the knowledge that key and metadata information will be shipped > [16:41] <galderz> the way i mapped converter to remote listeners is that whatever the converter returns, we ship that, as is, to the client > [16:41] <galderz> so, if a remote listener wants a custom event that includes key + value > [16:41] <galderz> it needs to develop a converter impl that returns bytes containing key + value > [16:41] <galderz> which is inefficient because you are passing around the key twice > [16:42] <galderz> once as part of the event itself, and again inside the converted value > [16:42] <galderz> inefficient from the POV of shipping stuff around from other nodes to where the cluster listener is located > [16:44] <wburns> yeah makes sense > [16:44] <galderz> not a major issue but not easy to fix without changing semantics or public protocol -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5083) Hot Rod decoder should use async Cache operations

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5083?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5083: ---------------------------------- Fix Version/s: 9.0.0.Alpha3 (was: 9.0.0.Alpha2) > Hot Rod decoder should use async Cache operations > ------------------------------------------------- > > Key: ISPN-5083 > URL: https://issues.jboss.org/browse/ISPN-5083 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Reporter: Galder Zamarreño > Assignee: Gustavo Fernandes > Fix For: 9.0.0.Alpha3 > > > Hot Rod decoder is currently tying up Netty threads as a result of calling up to Infinispan sync operations. Instead, Hot Rod decoder should call up async operations, convert the Notifying Futures to Scala Futures, and write up the reply when it's received. This should increase performance specially under heavy load. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5093) Granularity of remote event listener implementations doing the same job

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5093?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5093: ---------------------------------- Fix Version/s: 9.0.0.Alpha3 (was: 9.0.0.Alpha2) > Granularity of remote event listener implementations doing the same job > ----------------------------------------------------------------------- > > Key: ISPN-5093 > URL: https://issues.jboss.org/browse/ISPN-5093 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.0.0.Alpha3 > > > Currently, if N clients add the same listener to a cache that does the same job, e.g. keeping a near cache consistent, this results in N server-side cluster listeners created, each potentially installed in different nodes. If one of those nodes fails, all clients that had a listener registered to that node will have to find a different node for this listener. > The downsides of this approach is that there are as many cluster listeners installed as clients have added listeners (or have near cache enabled), which might not very efficient. If a node goes down, all clients that have cluster listeners there need to failover to some other node. > The advantage of this approach is simplicity of the approach to decide where to add the listener and where to failover to. > For this type of scenarios, an alternative set up might be worth exploring: > If all these client side listeners are interested in exactly the same events, and the client ID would be exposed via the RemoteCache API, a server side cluster listener multi-plexing between all these clients could be potentially built. In other words, instead of having N clients register N cluster listeners, the first client would register the cluster listener with a client listener ID, and if more registrations were added with the same client listener ID, the connections would be added to the existing cluster listener implementation. > The maximise the efficiency of this solution, all clients (even running in different JMVs), given the same client listener ID, should agree upon the node to add the listener in. For a distributed cache, hashing on the cache name would work. For replicated caches, since there's no hashing available, the first node of the view could be used. > Since the logic to be executed server-side varies between being the first node adding the client listener vs the others, synchronization would be added to make sure that the first invocation only creates the cluster listener, and the others simply add the channel to the listener. > Failover is a bit more tricky too, because if the node with the cluster listener goes down, all the clients have to failover, which again exposes a 1st vs the others type of logic. > Advantages of this approach is the reduction in number of cluster listeners and potentially efficiency coming from a single cluster listener implementation server side. > The disadvantages come from the server side logic to add/failover a cluster listener, which need to take into account if the listener is present or not. Other disadvantages come from needing the clients to use some specific routing for adding listeners for same node. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5058) Document example configurations using a CacheStore to persist the Lucene index

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5058?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5058: ---------------------------------- Fix Version/s: 9.0.0.Alpha3 (was: 9.0.0.Alpha2) > Document example configurations using a CacheStore to persist the Lucene index > ------------------------------------------------------------------------------ > > Key: ISPN-5058 > URL: https://issues.jboss.org/browse/ISPN-5058 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Query > Reporter: Sanne Grinovero > Assignee: Gustavo Fernandes > Fix For: 9.0.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 May 2016