April 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4127) CacheJmxRegistration.unregisterCacheMBean unregisters cache mbean of all caches

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4127?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4127: ----------------------------------------------- Radoslav Husar <rhusar(a)redhat.com> changed the Status of [bug 917010|https://bugzilla.redhat.com/show_bug.cgi?id=917010] from ASSIGNED to ON_QA > CacheJmxRegistration.unregisterCacheMBean unregisters cache mbean of all caches > ------------------------------------------------------------------------------- > > Key: ISPN-4127 > URL: https://issues.jboss.org/browse/ISPN-4127 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 5.2.7.Final > Reporter: Dominik Pospisil > Assignee: Dominik Pospisil > Fix For: 5.2.8.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-694) Create expiration notification for in-memory cache entries

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-694?page=com.atlassian.jira.plugin.s... ] William Burns commented on ISPN-694: ------------------------------------ [~dan.berindei] I agree, I was referring to the case when you do a get on one of the owner nodes it will only refresh that owner's max idle at that time since it doesn't go remote. In this case the other node could time out early. And then if another non owner does a get or even that other owner the get could return null when the value is present. > Create expiration notification for in-memory cache entries > ---------------------------------------------------------- > > Key: ISPN-694 > URL: https://issues.jboss.org/browse/ISPN-694 > Project: Infinispan > Issue Type: Feature Request > Components: Eviction > Environment: any > Reporter: Edouard Boily > Assignee: Galder Zamarreño > Attachments: 01.patch > > > Create a CacheEntryExpired notification and make EvictionManager send this notification when a cache entry is evicted because it is expired. > Also mage sure the cache entry value is sent over in the event. > CacheEntryEvicted notification should also send the entry value in the event. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4185) Fix JPA cache store section formatting

by Ion Savin (JIRA)

[ https://issues.jboss.org/browse/ISPN-4185?page=com.atlassian.jira.plugin.... ] Ion Savin updated ISPN-4185: ---------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2478 > Fix JPA cache store section formatting > -------------------------------------- > > Key: ISPN-4185 > URL: https://issues.jboss.org/browse/ISPN-4185 > Project: Infinispan > Issue Type: Bug > Components: Documentation-Core > Affects Versions: 7.0.0.Alpha2 > Reporter: Ion Savin > Assignee: Ion Savin > > The section identation is one level up and the chapter separation delimiter is missing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4185) Fix JPA cache store section formatting

by Ion Savin (JIRA)

Ion Savin created ISPN-4185: ------------------------------- Summary: Fix JPA cache store section formatting Key: ISPN-4185 URL: https://issues.jboss.org/browse/ISPN-4185 Project: Infinispan Issue Type: Bug Components: Documentation-Core Affects Versions: 7.0.0.Alpha2 Reporter: Ion Savin Assignee: Ion Savin The section identation is one level up and the chapter separation delimiter is missing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4096) The unstable profile for server testsuite is not working correctly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4096?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-4096: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1083900 > The unstable profile for server testsuite is not working correctly > ------------------------------------------------------------------ > > Key: ISPN-4096 > URL: https://issues.jboss.org/browse/ISPN-4096 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Reporter: Jakub Markos > Assignee: Jakub Markos > Labels: 630 > Fix For: 7.0.0.Alpha2 > > > There are several surefire executions defined in the testsuites pom.xml, each can use a different arquillian group (which is just a set of container configurations). There are 4 main executions: suite-client-local, suite-client-dist, suite-client-repl, suite-manual. The unstable profile is configured to run the tests marked with Unstable category, but it's only using the arquillian group from suite-manual, so if there is a unstable client test, it fails because it can't find the arquillian container definition. > Looking for a nice solution. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4134) Make Cache.evict() a cluster-wide operation

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4134?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-4134: ------------------------------------ I guess making {{Cache.evict()}} cluster-wide would be a natural evolution of what we've been doing so far. {{evict()}} now behaves more or less like a regular {{remove()}} that writes the entry to the cache instead of removing it (or just skips the cache store, if passivation is disabled). But the javadoc hasn't changed a lot since the beginning of the project, and it paints a completely different picture: {noformat} * This method is designed to evict an entry from memory to free up memory used by the application. This method uses * a 0 lock acquisition timeout so it does not block in attempting to acquire locks. It behaves as a no-op if the * lock on the entry cannot be acquired <i>immediately</i>. * <p/> * Important: this method should not be called from within a transaction scope. {noformat} > Make Cache.evict() a cluster-wide operation > ------------------------------------------- > > Key: ISPN-4134 > URL: https://issues.jboss.org/browse/ISPN-4134 > Project: Infinispan > Issue Type: Enhancement > Components: Eviction > Affects Versions: 6.0.2.Final > Reporter: Paul Ferraro > Assignee: Dan Berindei > > Personally, I have never fully understood why Cache.evict() is a local-only operation. > If a user wants to perform a cluster-wide evict, they need to implement their own RPC mechanism in order to perform the eviction on each node. Within WildFly, there are at least 2 use cases for such an operation. > Why not instead make Cache.evict() a cluster-wide operation? The existing (i.e. local-only) behavior can always achieved via: > AdvancedCache.withFlags(Flag.CACHE_MODE_LOCAL).evict(...) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4184) Expose Unsafe to Netty module so that it can use native buffers

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4184?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-4184: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2477 > Expose Unsafe to Netty module so that it can use native buffers > --------------------------------------------------------------- > > Key: ISPN-4184 > URL: https://issues.jboss.org/browse/ISPN-4184 > Project: Infinispan > Issue Type: Bug > Components: Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 7.0.0.Alpha3 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4184) Expose Unsafe to Netty module so that it can use native buffers

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-4184: ------------------------------------- Summary: Expose Unsafe to Netty module so that it can use native buffers Key: ISPN-4184 URL: https://issues.jboss.org/browse/ISPN-4184 Project: Infinispan Issue Type: Bug Components: Server Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 7.0.0.Alpha3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4132) Group-based eviction

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4132?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-4132: ------------------------------------ Eviction in Infinispan assumes that evicted entry can be easily restored, either by Infinispan loading them from a store or by the user application itself. With that assumption, it doesn't make sense to evict a bunch of keys all at once: just because session S has been accessed recently, it doesn't mean that attribute S.A has also been accessed recently and it's worth keeping it in memory. > Group-based eviction > -------------------- > > Key: ISPN-4132 > URL: https://issues.jboss.org/browse/ISPN-4132 > Project: Infinispan > Issue Type: Feature Request > Components: Eviction > Affects Versions: 6.0.2.Final > Reporter: Paul Ferraro > Assignee: Dan Berindei > > Currently, Infinispan only supports size-based eviction. We can configure a cache with a specific max-entries, so if the size exceeds this value infinispan will evict any surplus entries. > However, if the cache has grouping enabled, it is perhaps more useful to use group-based eviction. In this scenario, max-entries would be interpreted as "max-groups", and infinispan would evict entire groups of cache entries if the number of groups exceeds this value. > In WildFly, web sessions make use of grouping. A single web session will map to a single group of multiple cache entries, where the number of entries is not necessarily the same for a given session. In this case, evicting per cache entry does not make sense - all entries of a session should be evicted or not at all. Also, users can specify the max number of sessions they want to remain in memory. Until infinispan supports group-based eviction, translating this value to an appropriate max-entries is cumbersome and imprecise. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-694) Create expiration notification for in-memory cache entries

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-694?page=com.atlassian.jira.plugin.s... ] Dan Berindei commented on ISPN-694: ----------------------------------- [~william.burns] for now, remote gets are sent to all the owners, so unless all the get requests are coming from the primary owner, the other owners will see some activity on the key. But maxIdle with numOwners != 1 will become pointless once we introduce staggered gets (I still have the branch in my repo!) With lifespan there are consistency problems as well: the exact moment the entry is created depends on the node, so it will expire at different times on different nodes. But I guess nobody that cares about consistency uses lifespan and/or maxIdle (except maybe [~pferraro]). > Create expiration notification for in-memory cache entries > ---------------------------------------------------------- > > Key: ISPN-694 > URL: https://issues.jboss.org/browse/ISPN-694 > Project: Infinispan > Issue Type: Feature Request > Components: Eviction > Environment: any > Reporter: Edouard Boily > Assignee: Galder Zamarreño > Attachments: 01.patch > > > Create a CacheEntryExpired notification and make EvictionManager send this notification when a cache entry is evicted because it is expired. > Also mage sure the cache entry value is sent over in the event. > CacheEntryEvicted notification should also send the entry value in the event. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2014