November 2014 - infinispan-issues

[JBoss JIRA] (ISPN-3103) StateRequestCommand requests serialization of type for which no Externalizer exists

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3103?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3103: -------------------------------- Priority: Major (was: Critical) > StateRequestCommand requests serialization of type for which no Externalizer exists > ----------------------------------------------------------------------------------- > > Key: ISPN-3103 > URL: https://issues.jboss.org/browse/ISPN-3103 > Project: Infinispan > Issue Type: Enhancement > Components: State Transfer > Reporter: Sanne Grinovero > Assignee: Adrian Nistor > Attachments: ISPN-3103_cow_externalized.patch > > > RPC org.infinispan.statetransfer.StateRequestCommand sends a parameter defined as type Set (field segments) which is implemented by a java.util.concurrent.CopyOnWriteArraySet. > This implementation is Serializable but seems to be quite slow as we don't have a custom Externalizer for it. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4950) Expiration settings not applied to entries stored via CLI

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-4950?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-4950: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Expiration settings not applied to entries stored via CLI > --------------------------------------------------------- > > Key: ISPN-4950 > URL: https://issues.jboss.org/browse/ISPN-4950 > Project: Infinispan > Issue Type: Bug > Components: CLI, Remote Protocols, Server > Affects Versions: 7.0.0.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.0.1.Final > > > Data stored via CLI does not seem to get container expiration settings applied. E.g. > For a server side configuration like this: > {code} > <local-cache name="shay" start="EAGER"> > <expiration lifespan="1000" max-idle="1000"/> > </local-cache> > {code} > Storing it and retrieving it always returns the entry, no matter how long it's waited: > {code} > [disconnected /] connect > [standalone@localhost:9990 /] cd subsystem=infinispan/cache-container=local > [standalone@localhost:9990 cache-container=local] cache shay > [standalone@localhost:9990 local-cache=shay] put a a1 > [standalone@localhost:9990 local-cache=shay] get a > a1 > ... > [standalone@localhost:9990 local-cache=shay] get a > a1 > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4986) Error in CDI User Guide

by Bruno Palaoro (JIRA)

[ https://issues.jboss.org/browse/ISPN-4986?page=com.atlassian.jira.plugin.... ] Bruno Palaoro updated ISPN-4986: -------------------------------- Description: In the user guide, the classes of the cdi interceptors are wrong. Instead of org.infinispan.cdi.interceptor, as it was in previous versions, it should be org.infinispan.jcache.annotation. I've noticed this in the 6.x and 7.x versions of the user guide. http://infinispan.org/docs/6.0.x/user_guide/user_guide.html#_use_jcache_c... was: In the user guide, the classes of the cdi interceptors are worng. Instead of org.infinispan.cdi.interceptor as it was in previous versions, it should be org.infinispan.jcache.annotation. I've noticed this in the 6.x and 7.x versions of the user guide. http://infinispan.org/docs/6.0.x/user_guide/user_guide.html#_use_jcache_c... > Error in CDI User Guide > ----------------------- > > Key: ISPN-4986 > URL: https://issues.jboss.org/browse/ISPN-4986 > Project: Infinispan > Issue Type: Bug > Components: CDI Integration > Affects Versions: 6.0.2.Final, 7.0.0.Final > Reporter: Bruno Palaoro > Priority: Minor > > In the user guide, the classes of the cdi interceptors are wrong. > Instead of org.infinispan.cdi.interceptor, as it was in previous versions, it should be org.infinispan.jcache.annotation. I've noticed this in the 6.x and 7.x versions of the user guide. > http://infinispan.org/docs/6.0.x/user_guide/user_guide.html#_use_jcache_c... -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4986) Error in CDI User Guide

by Bruno Palaoro (JIRA)

[ https://issues.jboss.org/browse/ISPN-4986?page=com.atlassian.jira.plugin.... ] Bruno Palaoro updated ISPN-4986: -------------------------------- Issue Type: Enhancement (was: Bug) > Error in CDI User Guide > ----------------------- > > Key: ISPN-4986 > URL: https://issues.jboss.org/browse/ISPN-4986 > Project: Infinispan > Issue Type: Enhancement > Components: CDI Integration > Affects Versions: 6.0.2.Final, 7.0.0.Final > Reporter: Bruno Palaoro > Priority: Minor > > In the user guide, the classes of the cdi interceptors are worng. > Instead of org.infinispan.cdi.interceptor as it was in previous versions, it should be org.infinispan.jcache.annotation. I've noticed this in the 6.x and 7.x versions of the user guide. > http://infinispan.org/docs/6.0.x/user_guide/user_guide.html#_use_jcache_c... -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4986) Error in CDI User Guide

by Bruno Palaoro (JIRA)

[ https://issues.jboss.org/browse/ISPN-4986?page=com.atlassian.jira.plugin.... ] Bruno Palaoro updated ISPN-4986: -------------------------------- Issue Type: Bug (was: Enhancement) > Error in CDI User Guide > ----------------------- > > Key: ISPN-4986 > URL: https://issues.jboss.org/browse/ISPN-4986 > Project: Infinispan > Issue Type: Bug > Components: CDI Integration > Affects Versions: 6.0.2.Final, 7.0.0.Final > Reporter: Bruno Palaoro > Priority: Minor > > In the user guide, the classes of the cdi interceptors are worng. > Instead of org.infinispan.cdi.interceptor as it was in previous versions, it should be org.infinispan.jcache.annotation. I've noticed this in the 6.x and 7.x versions of the user guide. > http://infinispan.org/docs/6.0.x/user_guide/user_guide.html#_use_jcache_c... -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4986) Error in CDI User Guide

by Bruno Palaoro (JIRA)

Bruno Palaoro created ISPN-4986: ----------------------------------- Summary: Error in CDI User Guide Key: ISPN-4986 URL: https://issues.jboss.org/browse/ISPN-4986 Project: Infinispan Issue Type: Bug Components: CDI Integration Affects Versions: 7.0.0.Final, 6.0.2.Final Reporter: Bruno Palaoro Priority: Minor In the user guide, the classes of the cdi interceptors are worng. Instead of org.infinispan.cdi.interceptor as it was in previous versions, it should be org.infinispan.jcache.annotation. I've noticed this in the 6.x and 7.x versions of the user guide. http://infinispan.org/docs/6.0.x/user_guide/user_guide.html#_use_jcache_c... -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4979) CacheStatusResponse map uses too much memory

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-4979?page=com.atlassian.jira.plugin.... ] Work on ISPN-4979 started by William Burns. ------------------------------------------- > CacheStatusResponse map uses too much memory > -------------------------------------------- > > Key: ISPN-4979 > URL: https://issues.jboss.org/browse/ISPN-4979 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 7.0.0.Final > Reporter: Dan Berindei > Assignee: William Burns > Priority: Critical > Fix For: 7.1.0.Final > > > When the cluster is large and there are a log of caches, the {{CacheStatusResponse}} map on the new coordinator can get quite large. One of the problems that seems to be that the addresses in {{DefaultConsistentHash}} are duplicated on serialization, so the deserialized version occupies more memory. > We need to investigate why the objects are not "shared" by the River marshaller, and maybe work around the problem by de-duplicating the addresses in the externalizer. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4979) CacheStatusResponse map uses too much memory

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-4979?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on ISPN-4979: --------------------------------------- I think you would benefit of ISPN-2133 as well to implement this. Would need to be combined with the AddressCollection we discussed years ago, which threads all Addresses as singletons and manages immutable shallow copies. > CacheStatusResponse map uses too much memory > -------------------------------------------- > > Key: ISPN-4979 > URL: https://issues.jboss.org/browse/ISPN-4979 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 7.0.0.Final > Reporter: Dan Berindei > Assignee: William Burns > Priority: Critical > Fix For: 7.1.0.Final > > > When the cluster is large and there are a log of caches, the {{CacheStatusResponse}} map on the new coordinator can get quite large. One of the problems that seems to be that the addresses in {{DefaultConsistentHash}} are duplicated on serialization, so the deserialized version occupies more memory. > We need to investigate why the objects are not "shared" by the River marshaller, and maybe work around the problem by de-duplicating the addresses in the externalizer. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4979) CacheStatusResponse map uses too much memory

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4979?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4979: ------------------------------- Status: Open (was: New) > CacheStatusResponse map uses too much memory > -------------------------------------------- > > Key: ISPN-4979 > URL: https://issues.jboss.org/browse/ISPN-4979 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 7.0.0.Final > Reporter: Dan Berindei > Assignee: William Burns > Priority: Critical > Fix For: 7.1.0.Final > > > When the cluster is large and there are a log of caches, the {{CacheStatusResponse}} map on the new coordinator can get quite large. One of the problems that seems to be that the addresses in {{DefaultConsistentHash}} are duplicated on serialization, so the deserialized version occupies more memory. > We need to investigate why the objects are not "shared" by the River marshaller, and maybe work around the problem by de-duplicating the addresses in the externalizer. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4444) After state transfer, a node is able to read keys it no longer owns from its data container

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-4444?page=com.atlassian.jira.plugin.... ] Work on ISPN-4444 started by Pedro Ruivo. ----------------------------------------- > After state transfer, a node is able to read keys it no longer owns from its data container > ------------------------------------------------------------------------------------------- > > Key: ISPN-4444 > URL: https://issues.jboss.org/browse/ISPN-4444 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 7.0.0.Alpha4 > Reporter: Dan Berindei > Assignee: Pedro Ruivo > Priority: Critical > Fix For: 7.1.0.Alpha1 > > > When state transfer ends and each node receives a CH_UPDATE command from the coordinator, it first installs the new topology and then it starts invalidating entries it no longer owns. > However, there are two cases when the node can still read its stale values: > 1. If L1 is enabled, it will look in the local DataContainer first, regardless of the key's location. > 2. If L1 is disabled, but the key was removed on the new owners, the node will still look up the key in the local DataContainer after receiving a null response. > The problem can be reproduced with {{TxReadAfterLosingOwnershipTest}} and its subclasses, by replacing the {{operation.update(cache(1));}} line with {{operation.update(cache(0));}} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 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 November 2014